Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0 )cin@b@0ortsanativegasgenericadvertisment@b@00allowedtheconcatenationoftheseparat@@0coincide@entity@inserttheworddownlinkbeforemodeaandotherplacesint@eneedtomentionthatipphswillinsteadbestandardsbased@cremovethetableentryscrambleron/off@thetx/rxtransitiongapisagapbetweenthedownlinkburst@cbaudrateispoorlanguageifbaudissymbolratethenbaud@defines@itonlywastesbandwidthifweneedtoaddafielditcanbe@&naturalthefigurecontainedinthissectionisfigure79@AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijkQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJ>@ Cj%7.hal e-iJ.hj -Ek. l`l -mFxrogermarkspQmarksprogermarksBRmarksBrogermarksTmarksrogermarks@Umarks@roger marksmarksroger marks( i marks!(!roger  marks"0#q#marks$"0$ marks( i marks!(!roger  marks"0#q#marks$"0$DTDT €Editor's NotesEditor's Questions and Concerns€AEditor's Action Items€A€A€A Starting Line #€A Section€A  Fig/Table# BA1BAj  !"#$%&'()*+,-./0234567j^_ `2a4bc d ijkmn.p+v"wx#y'{)€%€0€€€€1€€66leiOwang' *  wang * leiP wang wang ' leiQ wang VYwang VleiRwangwang YleiSwang wang leiTwang@nh&`wanghleiUwangnp0AWW0374-02W07-0375-01W1WWWYW WAWW10WWW105WW W$WW106WW W#WW109W11WWWWWWWWWWWWWWWMWWWW110W110-127W116W118W12*W136W15AW19WW2W W'WAWW20W202WWWWWWW454WWWW471W472W48W497WW8WWWW5RW5.3$W5.3changedtomihfserviceoverview$V588W596W6W6.2.1W6.2.3W6.5.6.16W6.5.6.2.26W6.5.6.2.2needsanintroduction6V76W<WWW3W8<WHWW8.2.2W8.6WaWWWWWWWWWa-1WableWaboutW2Waccess3WWactionszWWK 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 OCOMSP^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  ABCDdEF^G_H`IJaKbLcMgNiOmPjQkRvSwTxUyVW{XpYnZ p\n] ׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫׫'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\{]^_`abcdebA`abcas@;be@+different@ifatleastonequeryisrequiredthereshouldbesomeminim@aereisnoreferencespleasechangeclausetexttothere@may@ miheventsubscribeandunsubscribearelistedpartofservi@mipshop@pleaseclarifywhichprotocolmessageismandatoryandwhich@Treferencetoethertypeismissing@?referencetowrongmessage@referenced@sinceavailableresourcesareonapercandidatelinkbasis@Psome@tablek-2doesnotprovideaverycomprehensivemappingbetw@thepurposeandusefulnessofmihnethocandidatequerycom@transport@japply@choose@:correctfigure26toshowmihprotocolheaderhasfixedleng@e@indicatethatthereversedirectionsareallowed@Dmay@optional@Vremovealldefinitionandmentioningofmihnethocandidate@similar@@o@;u@QAAExport Full RecordsEOFMPR$@` ABCDEFGHdIJ^K_L`MaNbOcPgQiRmSjTkUvVwWxXyYZ{[p\n]^QCAAbout CommentaryEDQEAExport Vote & CommentsE6NALL OFMPRV D@]W@gFD@ @D@  ] W@ g F E@D@]W@gFFD@F$@`V0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsical, Bindinghh' Cw# ,v # 0x #  2y # s 2 @BBA0 0^_`ab c dijkmvwxy€€€             XXXX$XXXX2 X  X  X X& X'X(X)XXXXXXXX!X 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 PMb@B@2@I@ @Ad@t@@@@7@6=@p@@@f@ @ @P;< disapprove @ @P; @P;toclarifydocument@d@B@2A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,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€ (EStephens, Adrian PF DisapproveGProducer^ Technical_143`47a8.2.1cA"When the MIH transport is reliable, the acknowledgement mechanism may not be used". In my experience, different readers understand different things by "may not". Some read is as "shall not", others as "need not". This is a potential interoperability issue.d1g4303referenced in clause 8.5, it should be included hered140n rd(2) Save Data to Filee(3) Submit Ballot Filef9Proceed with the following steps by clicking the buttons:€gAFile name must follow format: BallotNumber_Lastname_Firstname.USR (Extension is .USR) File format choice must be: FileMakerPro or FileMakerPro Runtime@AR  33  V  33r  R€tAWORKING GROUP BALLOT: Send email to: using the subject line: Make sure to: Attach file created in (2) Send manually if this button does not work.@Az    33%  &  33M  h  33z€uA €vA wShow All Comments€A@IEEE SPONSOR BALLOT: Upload using IEEE Balloting Center web form@@A*    33* not work.@work.@   337  R  33fPI3Import Full RecordsExport Full Records Enter commentExport Vote & Comments Email file Startup script Delete Empty RecordsDelete Abstain CommentsDelete All Records Show VotesShow All Records in OrderSort by Comment #Sort by Page/LineSort by Comment OriginatorSort by RecommenderShow Editor's Problems Assign Editors#Mark Found Records%Unmark Found Records'Find Marked Records)Import Ballot Comments+Export Comments-Import Comments/ Export Clause Editor's Proposals1 Import Clause Editor's Proposals3Export Group Resolutions5Import Group Resolutions7Export Editor's Input9Import Editor's Input:Import Global Data< Help WebLink>WirelessMAN WebLink@Export IEEE XMLCOpen Reply Comment FileEAbout Commentary<AKEG  7   :UVWQNF89=>>9=>gP:@K79@<E Q@ Q*E@uD QFGB{K@(MNxS@W@ZC[E\G]I^K_M`OaQbScUeW  A} !LISTAqVDEFEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEfterW=WcWWWallWalleviatebWallocationbWalphaWalsoWWWalternativeWalternativesWalthoughWbWalwaysbWanWareadWasWWcWWatW(WOWattributesWbandWbandsdWbandwidth(WbaseWbeWWW(WbWcWWbelowbWcWWerL> `Z   [w \ ]  ^ w  $,.YesNo/,  , : AM PMew h 3  $,.YesNo/,  , : AM PMi   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PMm   ,  , : AM PMd   $ ANU#OV#V+X^5)SY{cTZbo|h[ +' \_l) ]D+b ^`l$)C_B+``al)a,maTbc -6cI dd De ]f)aTgvhYi< A_.^ -^; Pbj0=bi.  _l -d @/Tcj4A6XZB% K%[%K% %\%0E>]^% 7%e%D€B G€ AEmail ToB G€ A Email SubjectB G€ AEmail ccB G€A BallotNumberB G€A DocNumberB G€ACommentary VersionB G€A ExportDateB AbG€A Comment DateB G€ACommentary Version NotesB G€ACommentary Version DateB G€AMarkB G€A XML OutputB  B  " 0000000 87654321 "& & &""&""& ""&b&"" F€A Comment Type€ASuggested Remedy€ A Starting Page Number€ACommentXCreate CommentZDocument[Create another Comment\Create/Submit Ballot]In WG Ballot, "Binding" comnents are those which form the basis of a "Disapprove" vote. IEEE Balloting Center processes all Technical comments identically.€^AeShow All Comments€hAiSection€jAk Fig/Table#€lAmStarting Line # B?A6 6^_`abc€` a b cdX)*+,-.X()*+,-.X,-.XXolutionARecommendation byCRecommendation:EReason for RecommendationHEditor's QuestionsKEditor's Action ItemsN Group's Notes @B=Abajkogabor@chaplinclintf@clint@Ocypherdavid@eastwoodeastwoodlesterf@1erik@g@henderson@hong@&julkavibhor@kadathur@|levy@marian@:meylemansVmeylemansmarc@*@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 sBls# #  al#I clI#[  bl[#^ Bmv^#b  @ivb# sj{# Dkv# 8w#i,Cjvi# 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# #  #K dK# ## ## ## # ^#H  _lH#s  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€ $$$$$%%% % %  %  &  & & &&'''''((((()=52;/<16333 <3 3 4  4  =65 549$9"9 :&867;,788:);+-*,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 GL5605iA 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 GH DisapprovePP802-21-D03-00KenichiTaniuchiktaniuchi@tari.toshiba.com+44 1223 7634574 24580intel.com Classification FileOther2Other3Other3€mAComment 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 DataIsj@0@@F@g@xcBscAy@qcAcAcAccAcAF.cACa@c|@@jO@/@FpAvBm@ w@vq@vAj@vw@vA@j@cAvA@jA+H\@@@-@ @w@jZvA@xcAAj@cAg@QJ@Gv@@jA@EEREEdREEREEREEREEREEREEdREEwy10&W'WWWW105WWWW W$WW106WWWWW W#WW11WMW114WW141WW2'W20W210W227,W260WW WWW277W299W326WW331W339WWUW344W"WWW347W!WWW35W351W WWW363W378W397WDWW406yW407xWyW417lW420W427W429[W\W444W471W488'WW497WW8WWWWW532WW556WW563WW576W588W59W615WWWW618W621W624W88WasW Wby'WWcmtWWWWWWW&W'W8WWWWWWWWWWW WW#W$WMWWWWW/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/20hEAjayFRajkumaranamendmentWbitsWbyWdividedWitWlinkWmediumWnadaWnadaprovidedtheamendmentlinkthroughoutthenumberofbiVnumberWofWoverWprovidedWreceivedWsuccessfullyWtheWthemWthroughoutWtimeWtoWtookWtransmitWageisfoundtocarrythVinWisWlinkWlooseWmagicWmakeWmayWmessageWWmessage-idWmihWWmostWnewWnewlyWnodeWWnormativeWnumberWofWWonWpropertiesWprotocolWWrequirementWretransmissionWretransmittedWsameWWshallWsourceWspecWspecialWtheWWthesourcemihnodemayatmostmaketworetransmissionatteVthisWWtoWWtransaction-idWWtwoWwhat'sWwhyWwithWWDMember adrian.p.stephens@intel.com ProducerNo1111o113ther33er3333qvjexists-WWexpandZW\WexpandtheblocktoproperlyincludethelinkandmihprimitZV\VnticationisreferencedinthisparagraVexplicitWWWexplicitlyvWexposed@Wextend-Wextending4WextentWexternal'WfW%WfakWlWmWfailedeWfailureeWWfar7WfastWfdd3Wfdd/tdd;WfeatureWfeatures,W/WfewWfieldW=WWAWfigWfigureWWWWW*WHWWWWQWfigure-7WfirstWWWW&WbWWWWWfirstintroducesomethinglikeapicssomewhereintheannex&VfixWWWW WWWfixthefontthisisthereisseveralotherplacesindraftVfixthemodellingsothatthestandarddoesn'tplayfastandVfixthepdfand/orthetextsothepagenumberscorrespondVfixthetext V cannexes%W/WanotherWW W WWvWWWWWWWanswerWanyWWWWWWWWW WWW/W5WwWWWWWWWW*WMWWWWWWWWWW WWanythingWWanywhereWWapWWWWWWWWapartWWapiWappear!W[W/WWappearanceWappears=WFWbWnWoWWWW WWWWWWapplicableWWJWWWapplicationWW(W<Wapplication'sWappliedWPWWappliesW0WWWWWWWWWWWtWWappropriatelyWWWapproximatelyWapsWarbitraryW'WarchitecturallyWarchitectureWWWWWWWWWW_390سسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسس|9cd‚@wÃ1@ÃB@ÃS@Ãd@Ãr@Ãvj21-07-0317-00-0000-s@5.1.7@8-octet@8.3.4targetdecisionandhandoverexecution@802.11u@|802.16@802.21needstoclearlystateworkingassumptionsregarding@aaone-octetselectorfieldfollowedbyavariablelengthval@nacknowledgement@ addacross-referenceforprimitivesdefinedinclause7ind@additthere@addthefollowingsentenceorsomethingsimilartotheparag@ionintherawo@available@Mbeen@nbot@capable@&case@changedescriptiontoabitmapnwherenmustbeamultiple@changen2nhocompletetomnhocomplete@changerequestisreceivedtorequestmessageisreceived@0changethetexttoclearlyspecifyhowthedestainationofe@dchangetothelinkdetectedeventisgeneratedonthemnwhe@fytypesonthelocalmihf@fEHenderson, Gregory SF DisapproveGProducer^ Editorial_134`39a 7.4.27.2.2c^Sytax of primitives in text doesn't not match syntax in adjoining description table line 39-65d642g4960jDelete spaces in table syntaxpUthis is a convention used throughout. spaces are used in table for better readabilityvUthis is a convention used throughout. spaces are used in table for better readabilitywDisagree{e) editor disagrees 2007/12/1909/16/2007 23:51:48 EDTYes E Kim, EunahKim, EunahveGProducer^ Editorial_134`39a 7.4.27.2.2c^Sytax of primitives in text doesn't not match syntax in adjoining description table line 39-65d642g4960jDelete spaces in table syntaxpUthis is a convention used throughout. spaces are used in table for better readabilityvUthis is a convention used throughout. spaces are used in table for better readabilitywDisagree{e) editor disagrees 2007/12/0709/16/2007 23:51:48 EDTMarkedYes E Kim, Eunah2d642`7^_ !0⣃⤃⦃ %㏃⠃p;⟃ἃὃAB‚!:‚$7‚%?@‚&ể‚*ẃ‚1‚3‚4Ꮓ‚7‚:>‚A‚B6‚Cᎃṃ'()‚Dῃ$+‚E ‚F*‚G‚I‚J᷃ḃ‚Rᴃᵃ‚S‚T‚Ud‚V‚X ‚YVW‚c᱃ᲃ᳃=‚g#‚h"c‚s‚xᯃ ‚y‚ᭃb‚᫃ `a‚᪃‚ᩃ_‚^‚]‚݃ރ߃‚f‚ᧃ‚‚‚\‚‚eÃ![Ã!0QÃ!@PRhÃ!`Ã!Ã!Ã!giÃ"jÃ" OmoÃ"0lÃ"@knpÃ"PqsÃ"`rÃ"ឃᢃ Ã"tÃ#uvÃ# ᝃᤃwxy{|}Ã#0ᣃz~Ã#@⁃Ã#P᥃Ã#`Ã#CÃ#E℃⅃Ↄ€BCdDE FGHIJK^L_MaN`OcP QRjST UwVWmXY{Z[n\x]k^b_`iabpcdyefvghijklmgnomgno,2„,stephensadrianp+ disapprove„- disapprove.3„.stephensadrianp- disapprove„/ disapprove0-&„0stephensadrianp/ disapprove„1 disapprove2:„2stephensadrianp1 disapprove„3 disapprove4%„4stephensadrianp3 disapprove„5 disapprove68X„6stephensadrianp5 disapprove dDTwcd 0 @ P ` p‚!‚"‚#‚$‚%‚&‚'‚(‚)‚*‚1‚2‚3‚4‚5‚6‚7‚8‚9‚:‚A‚B‚C‚D‚E‚F‚G‚H‚I‚J‚Q‚R‚S‚T‚U‚V‚W‚X‚Y‚Z‚a‚b‚c‚d‚e‚f‚g‚h‚i‚j‚q‚r‚s‚t‚u‚v‚w‚x‚y‚z‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>d1pWWW W W W W WWWJWKWLWMWNWpieter-paulW W!W"W#W$WpiotrWWqiaobingWWWWWWWWWWWWWWWWWrWrajkumar[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWrajkumarajay[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVVVVVVVVVVVVVVVVVVrichWWWWWWWW vneedsWWWWWWW W W@WWWWnetWWWWtWuW W WWWWnetwokWnetworkWWWWWWWWW/WkWWWW WW W}WWWWWWWWWnetworksWW WWW WWWWneverWnewWWuWW)WAWnolistofiesprovidedVnodeiWW W Wnon-posWnon-zeroWnormativeWWWWnotWWWWWWWWW/W0W2W5WAWuWwWWWWWW&W(W8WAWWWWWWWWWWWW WnoteWnothing5WWnullsWnumberWWWAW W WnumberedWobjectivesWobtainWobtainedWobtainsWofWWWW,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5BfHÃ"p@Ã3@@ÃD@ÃT@ÃeP@!rudolfmarian@AzNd @rinvias@fsreemanthulasrinvias@zsreemanthulasrinvias@reemanthulasrinvias@€€ €4€=X€?chaplinclintf€EW€] disapprove€q€}X€natarajankadathurs@€ disapprove€Y€ disapprove€rudolfmarian@€famolaridavid@€hrudolfmarian@rudolfmarian@#rudolfmarian@=federperetz@Ah]@n$rajkumarajay@57rajkumarajay@6 disapprove‚ meylemansmarc@‚‚(@‚+‚G‚X‚e disapprove‚nQ‚julkavibhor@‚ disapprove‚soodkapil@‚ disapproveƒ<` ሃቃᢃᬃẃῃ"#$%.69=S⠃⫃ƒƃʃՃ-./Qgijk㗃㾃㿃ƒăᒃᾃڃ:ዃ؃ރ Zw₃⢃⾃ Gu‚!ፃἃY➃‚"ᎃ‚#Nv⏃⦃‚$P℃⇃⼃‚%σ1⣃˃̃‚&᷃݃W‚'ᡃ*⌃‚(⑃╃‚*2k‚1@⎃Ⓝ‚2ᔃ΃z‚3ៃ᠃>tↃ‚5ᆃኃʃ‚6┃‚7‚8ᣃᭃ4BU‚9r‚:‚AḃQ‚Bᧃ !]‚Cᰃ+Cx‚DDR✃⤃‚E‚F᥃){‚Gᑃ7‚HᏃ҃|~‚Iᗃ/‚JጃX‚Qᩃ?Is‚Rᤃᯃ̃V⚃‚S-‚T}‚Uᝃᮃṃ(A‚V‚Wᨃ׃Fapprove⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⺃ǃȃɃʃ˃̃̓΃σ܀܁܂܃܄܅܆܇܈܉܊܋܌܍܎܏ܐܑܒܓܔܕܖܗܘܙܚܛܜܝܞܟܠܡܢܣܤܥܦܧܨܩܪܫܬܭܮܯܱܴܷܸܹܻܼܾܰܲܳܵܶܺܽܿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟu=@w Superceded 0 @ P ` p‚!‚"‚#‚$‚%‚&‚'‚(‚)‚*‚1‚2‚3‚4‚5‚6‚7‚8‚9‚:‚A‚B‚C‚D‚E‚F‚G‚H‚I‚J‚Q‚R‚S‚T‚U‚V‚W‚X‚Y‚Z‚a‚b‚c‚d‚e‚f‚g‚h‚i‚j‚q‚r‚s‚t‚u‚v‚w‚x‚y‚z‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚‚Ã!Ã! Ã!0Ã!@Ã!PÃ!`Ã!pÃ!Ã!Ã!Ã"Ã" Ã"0Ã"@Ã"PÃ"`4Ã23Ã32Ã3 1Ã300Qdj0/W^WWWWW0-24W1WWWWW%W7W=WTWXWWWWQWWW W1simplewritenormativeatthebeginingofthesectionV1-hsdpa/W1.1W1.2W10WhWWW100mNW106gW11WW11-12W11u,W12*WWWW13WQWW14WW14-15W145-146W149W15W16(WW178hW18W180W19WW19-47W2WWWWWW%W2W5W=WXWWWW1WQWkWWWW2-3'W2-hsupa/W20W21-07-0226-00-0000-mBW21-07-0312-00-0000-eW21-07-0312-00-0000-edocV21-07-0315-00-0000-dW21-07-0316-00-0000-mW/3gpp2W3gpp2WW:W3rd:W4WW4-55W42W43W47-48,W49W5<W5.1.1WW&W(W7W& jwagreeᇃሃቃፃᎃᏃᔃᕃᗃᙃᝃៃᡃᣃᤃ᥃ᦃṃểἃɃσу҃Ӄ׃؃ڃ܃݃ރ߃  !"#,-<>?@ABCDEFHKLMNPQRSUVXZ`bdehjprsz{|~⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⍃⎃⏃␃⒃Ⓝ┃╃▃◃☃⩃⪃⭃⯃ⳃⶃ⸃⹃⻃⼃⾃ǃȃ׃ۃ܃݃߃ !"#%.012379:;<=>?BCDFGHIJKLNOPQRSTUVWXYZ[\]^_`abbofqWoutqWoutofscope/unresolvableqVprincipleᆃዃᑃὃăƃЃԃՃփGe^editorialጃWʃ˃σЃ҃Ӄԃ؃كڃ݃ރ߃$%()*+.39:;T⑃⒃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⥃⬃ⱃⴃⵃɃ̃уڃ -/0134S]abefghvz{|}~ㆃ㇃㐃㘃㝃㠃㡃ǃȃɃʃ˃̃̓΃σ؃ރ߃editorialwastechnicalVgeneralᆃᇃሃቃኃᚃᛃᜃᮃẃểὃᾃƒ!"#<⩃⪃⮃Ⰳⳃⶃⷃ⺃!"&'()*+,EFGHOPQR^cijklt㎃㏃㑃㔃㕃㖃㚃㜃㟃㢃㣃㦃㩃㪃ЃWؓWؔWؕWؖWؗWؘWؙWؚW؛W؜W؝W؞W؟WؠWءW^technical̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓̓academicу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWOWPWQWRWSWTWUWVWWWXWYWZWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWp8`a1!YWZWEW1.1WWWWW1.3%ă1.42ᾃ8⠃⢃2.10.2:W2.17W2.47W8W2.5WW2.6WW2.7WWWW2.8UWXWW2.9;W<WW3⟃3.1G3.143.15;3.163.18ἃ3.23.263.293.42F3.63.7H3.855.1.15.1.25.1.4➃5.1.55.1.775.1.8Ã5.2.15.2.3.55.3.1߃5.3.2.25.3.3.55.3.4݃ރ5.4.2ẃ5.4.35.5.15.5.25.5.3ۃ܃5.5.45.5.55.5.65.6.15.6.265.6.2.65.7.2ṃ'()✃كڃ̃6"#$6.2ⷃ6.2.1+6.2.26.2.5 *׃؃)6.3.1ⵃⶃ"㡃㢃bc0W0-255W0.00W1WWWWWWoWWWWWWWWWWWWWW1theserecommendationshouldbenormativefor802.21althouV1-4=W1.0W1.2W1.3WWW1.5W1.5.1W1.5.1sentencetoocomplicatedanduncleartheieee802.21sV10WWW10.1W10.6W100NW10000200wW10000302wW107qW10e-3W11WWWW4WWW5.2.1W5.4.3W6.0WW6.2.1W64W65535W7-45W7.0W7.3.10.1 W7.3.6W7.4.23W7.4.23.2W8WWWW8-26W8-octetW8.6.3.15W802WWW W802.1W802.11WWWWWWWWWWWWWWW802.16WWW W802.21WWWWWWW802.3WWC Individual IndividualIndex #-21-D3.01.55Index #.g.gupta@intel.com P802-21-D3.01.55Index #: 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 andcords" button in Create andd in Create anddreate and All Records" button in Create andreate and €yes〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㔃㕃㖃㗃㙃㛃㜃㞃㟃㢃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃ҃ӃԃՃփ׃؃كڃۃ܃݃ ; bc12@21-05-0359r2@3.40@38-52@5.1.2@O8-octet@8.6forextendibilityofmihthereisaneedtoallowdefini@"802.11-2007@"a@hasimilarmechanismmaybeavailableforieee802.16forthi@abbreviations@accomplished@Lacknowledgement@actual@!addressing@yalongnalready@=alsoi@amend@Ganoanalog@and$andparameterextractioncommandsmissinghyphen@andthismessageistransmittedovercontrolplaneusingl2@annex@ annexes@appliestoalltechnologyspecificreferencemodelsupto5.@are@aretherereallynonormativereferencesforthisstandard@_ard@QQcommands@commonly@)configurations@\contain@\crossing@.default@defines@definitionfornetworksecurityismissing@describing@+descriptions@@ ab@8.4.5@all@all@all@all@all@dwhatisitssy@address@]after@all@all@ll@ddress@]after@all@l@orieextensibility@additional@]after@all@]after@all@l@additional@]after@all@dditional@]after@all@of21-07-0xxx-00-0000-taddressdoc@all@ll@0-0000-taddressdoc@all@all@all@be1andchangeallsubsequentaidvaluesa@uldbe1andchangeallsubsequentaidvaluesa@mih@mobile@Qname@note@or1oustanding@Toutstandingp153l21-24@sparamters@opleasechangeasappropriate@proper@Mprovides@r1@rename@Zreplacecanbeeitherthelocalmihforaremotemihfwithi@require@rest@,network@Am`a4@86.3.2@7.3.5.2@c7.4.17.2.2@;8.2.1@8.4.1@Hb2.5@oleantoenumerate@changehorizontalpolygonformlmesapfromgraytowhite@changetrue/falsetoinitiatehandoverandaborthandover@corresponding@deletetext@forlinkconfigurethresholdschangen/aunder802.11to@ifnotthendifferentnameswillbenecessaryhandoverresult@ip-based@network@proper@split8octetsintotwo4octetfieldsoneforlowmhzando@still@triggering@under@up@c14@abitmapdoesnothaveavalueofn/a@boolean@corresponding@error@ifatypeisenumeratedthenitsvalueisnot0-255yesmost@ifthevaluesfromtable13areusedthenavalidrangeexis@indicates@linkdownreasoncodeisnotusedanywhere@markedmhz@network@a8.4.1 8.5.1.4 b0ثWثWثWثWثWثWثW0/1UWUW; jmifhWmifh-idWmightWWmihWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWW&W'W(W)W+W-W7W<W@WRW]WcWiWjWtWwWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWW W#W$W'W*W+WCWDWKWLWOWQWXWZW[W\WbWeWfWnWoWWWWWWWWWWWWWWWWWWWWWWWmihmnhocandidatequeryresponseprimitiveismoreapproprVmihmnhocommitrequestbVeVfVfVmipwWmipshop'WmissingWWDV!jmay@mention@;mifh@mihn2nhocommitrequestindicationandmihmnhocommitre@ misunderstanding@more@movesection8.2.2toannex@need@network-side@,not@nsap@dnumeric@offoffers@6one@2QUewithforanm@Uranm@Uforanm@Uanm@Uddthefollowingsectionash10@Lpossiblyݥpossiblyremovethereferencetoieee802.15asitisnotsp@predefined@8primitive@dprovideadditionalnormativerequirementsrelatedtotheuse@8query@Vre-written@'reflect@ reliable@removelines47-48andreplacebyareferenceorshortsumma@removepacketidentifier@3replace@replacemaynotwithneednotorwordingwithsimilarintent@replacetextonlines55-56withthismessageisusedbyan@ requirements@responds@sap@Zsection2@server's@zqjintentWGWWWWintentionWintentionallyWinter-operability Winter-operateWinteractionAWinteractions>WinterfaceW8W@W`WWWinterfacesW W'Winternal WinternetWWinterpretationWinterpreted=WintervalW`WWinterworkingWintoWW%W.W2WkWlWmWWWdWWWintra-technology8W8W8WWW W W WWWWWWW&W'W(W)Wissues WitWWWWWWWWWWWWWW W WWWW&W(WitisnoteworthythattherewillbenodirectcommunicationVitemsWitsWWWitselfWjWW.Wj1Wj5Wjob WjustWWkWWWW%Wl2W&W+W-Wl3W&W+Wlaptop&WStjreplaceWWWWW,W=W@WJWTWXWdWWWWWWWWWWWWWWWWWWWWWreplace1with1TVreplaceack-rsprowintable15withfieldnamereservedsizVreplacealloccurrencesofmihconfigurelinkwithmihlinkVreplacehardsoftbyhardsoftVreplaceieee802.21standardwiththisstandardVreplaceinformationbydataVreplaceline8bytextthisprimitiveisusedbythemihftoVreplacelinkactionswlinkactionVreplacem-mtm-rspVVVWsameܟWܠWsap}W~WWWWsectionvW{W|WܙWܥWܩWWWsections}W~WsecurityWsee܉W܊W܌WܐWܕWܖWܛWܞWWseecommentforproposedresolutionVselectedܺWselectionܟWܠWselectorܺWselfܱWsendܿWsentenceWܺWܻWܼWB^MjreliableWreliesW7WremainWremaining.WWWWW WWW&W+WxWyWWWWWWW!W"Wremotely+WremoveᣃWWWWWWWWWWWW WWWW!W'W,W-W.W/W6W9WDWEWHWRWSWhWWWWWWWWWWWWWWWW W W W W!W"W#W$WremovealldefinitionandmentioningofmihnethocandidateVremovealldefinitionandmentioningofmihnetsapVVremovealldefinitionandmentioningofmihnmssapVVremovealldefinitionsandavoidmentioningofmihnethocaVremoveannexeentirelybecauseithasnonornativeorinfor9Vremoveannexjandinsertsomereferenceslikerfcsifpossi.Vremoveannexjrequirementstosupport802.21byl3andabovVVcnotބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބWބ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@\cthingsWthinkW7WnWoWWWWWthirdWWWW܅W܆W܈W܌WܑWܒWܕWܚWܜWܝWܟWܠWܡWܣWܨWܯWܱWܹWܽWܿWWWWWWWWWWWWWWWWWWWWWWW W WWWWWW%W.W1WIWJWKWOWPWRWTWUWVWWW^W`WaWcWeWrWuWvW}W~W݃W݉WݐWݑWݒWݔWݝWݠWݥWݦWݧWݭWݮWݴWݼWݿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW*W.W4W7W;WFW[WpWvWwWxW|WނWމWޑWޒWޓWޛWޜWޝWޞWޟWޠWޤWޥWަWެWޮWްWޱW޽W޾W޿W jmdeferred(juseWWWWWWWW+W2W4WJWWWWWW-W.WRWSWlWwWzWWWWWWWuseavailableadmissioncapacityforsupportednumberofcosVusehowtoextendmiisbasicschemaasthetitle-Vusemaxlinkrateinsteadofthroughputfordefinition1andVusemiisbasicschemaasthetitleaddinthefollowingtext.VuseonemethodandstaywithitRVSVlVVusethenamemihlinksappossiblyincludeanyadaptationlaVusethetermslinkandnetworkpreciselythroughoutthedocuVVVusers@WWW%WusingWWWWWW(W7WWutilizescWvalidWWvalueWWW9W=W^WeWW5WJWvaluesWWW=WWvariableWHWvariable-length=WversaWversionAWveryWWviceWvocabularies.W2jorWWWWWWWWWWWWWWWWWW WWWWWW%W&W'W(W+W,W-W1W5W6W9WDWEWJWYW`WdWhWiWwWxWyWWWWWWWWWWWWWWWWWWW'W@WIWJWMWxWWWWWWWWWWWWWWWWWWWWWWWW W WorderWWWWW&W/WgWWWorderingWorg/2006/09/rdf-basiWoriginalWoriginateWWoriginatedWoriginating WotherWWWW'W<W?WdWWWW0WWother'sWotherwise WtWout WW5W7WtWWW'WGWHWHWHWparagraphWWWW4WW -€noⷃ⺃ăŃƃ %-/03:GH㐃㑃㒃㓃㘃㚃㝃㠃㡃㣃ǃȃɃʃ˃̃̓΃σЃуރ߃[W_Ã%@؃كڃ'0|}Ã%P⒃⮃Ѓ{㚃 Ã%`փ׃⾃Ã%pÃ%ՃÃ%⼃҃Ã%ӃԃÃ&HI⭃㙃Ã& σ@A Ã&0Ã&@҃Ƀ̃Ã&PЃуMÃ'JÃ' zÃ'0Ã'@Ã'Pσ?Ã'`>Ã'pÃ(ᦃʃ˃%/xÃ(P̃̓΃⎃⬃=㘃Ã(`˃uvÃ(34Ã(78Ã(⍃stÃ)FGÃ) 2Ã)0Ã)Pៃ᠃01Ã)pᇃqrÃ)ŃÃ)Ã* XÃ*0Ã*@ᆃᛃᜃUÃ*P/ƃÃ*`Ã*pኃÃ*;<Ã*:pÃ1ănoÃ1@⫃mÃ1PKlÃ1`9Ã1ቃT.kÃ2㐃㑃Ã2PyÃ2`wÃ3SÃ3 9Ã3PjÃ3p-iÃ3hÃ4 gÃ60fÃ6peÃ6dÃ6&'cusedWWWWWWWWWWWWWWWWWWWWW WGWcWpWrWsWWWWWWWWW W WW%W&WMWZW\W^WcWWWWWWWWWWusefulWWWWWWWAWWuseful--it'sWusefuleWusefullnessfWusefulnessWW W(WWWuserW W7W>WAWBW]WeWfWiWpWtWwWWWWWW%WZW\WWWWWWWWWWFWGW^WvariableWWvariousWWWvaryWvendorWverbose<WverifiedWversionWveryWWWWWW<W[WviaWcWvirtualWvisibleWwWWw-cdma W WW0W3W7WwaiteWwaitingeWW^Ljsimilar@sourceidentifer@specification@tstartparagraphwithasanexamplefigure19shows@=statethatdiscoveryofmihposoverl3isoutofscopeofi@subsequently@successfully@suggest@table10@Ntaken@target@th@the@then@these@thisappearstoberelatedtotheissueofwhichmihusers@to@;type/id@underlying@(use@used@vs@with@ n@p207@8@_alltheoccurrenciesofmihinformationwaschangedasmihg@and7but@by3changemadethroughoutthedocument@Hcommentnolongervalidbecauseofresolutionofcomment11@deciding@hdefinition@examples@groupdisagreeswithcomment@hyphen@Al59@mac@Qneedtobedefinedinannexb@Rno@pagere-ordered@nCTcissueW WwWWissuedwWissuesWWissuingwWWWWWWWWWWWWWWWWWWWWWWWW W$W*W0W1W7W<W=W?W@WFWRW[W\W]WcWeWfWgWhWnWoWrWsWtWwWitappearsthatcosvaluesfromthelinkparamtypeofgenerFVitappearsthatipaddressinformationstatusisunnecessarynVoVitisincorrecttosaythatthetransmissionstatuscanbevVitisnoteworthyhoweverthattherewillbenodirectcommunVitmaysoundtrivialbutinitializeuponreceiptofthemihVitemsWiteselfWitsWWWWWW WitselfWjWW.Wj1Wj5WjobWjustWWWWW0W1WcWeWrWsWjustprovidingmacaddressesofpoaisinsufficientfornetwVVWcmayWWWWWWWWWWWW WWWW%W,W7W?WIW]WgWpWuWvWWWWWWWWWWWWW#W&WUWpWWWWWWWWWWWWWWW WWmaybeW&WWmbbhandoversupportfWmeWWWWmeanWWW0WpWWWWWWmeaningWWWtWWmeaningful5Wmeaningless.W3WmeansWWWWWWWW/WWWWWWmeantW3WmeasuredWmeasurementWmeasurementsWmeasuresWWoesnotcrossther1andr3Vthenumberofoctets27isnotcorrectusingthenumbersconVthepoachannelrangeisanimportantcharacteristicofthe:Vthepoacontainerdoesnotneedtocontainthepoamacaddre=V,ajneedWWWW&WkWlWmWWWW Wneeda'WneededWW=WWWWneedsW W=WtWWWWWneedsadefinitionVnegativeWnegotiate WnetWWWWWcWgWtWvWWWWW W W W$WWWWWWWnetworkWWWWWWWWWWWWWWWWXWbW}WWWWWWWWWWWWWWWWWWWWnooctetisencodedforthisdatatypethisdatatypeisuseVnodeWWW+WWWnodesW7WnoneWnormalizedWnormallyWnormativeWWWW WW%W.W9WWWWWWWWWnormativereferencesshouldbeconsideredsuchasthebasesVVnornative9W~;jmayWWWWWWW WW=W?WxWyWWWWWWWW%W8WWWWmaybeeithercarriedusingmediaspecificlinkservicesorVmaybe Wmean+W4WmeaningWmeansW'WWmeasurement2WmeasurementsW2WmechanismW W WWWWmechanismsWWmechnism7WmediaWWWWWWmedia-independentWmedia-specific&W6WmediumWWWWWWWdWmergethetexttosubclause5.1.1orremovethesubclauseVmergethetwoblocksintoonedVmeridianWmessageWWWxWyW~WWWWWWWWWWWWWWWCWDWIWWWWmessagesWW'W(W)WWWW'Wmet WmethodgWWRWSWlWzWmethodskWlWmW/jeWWW W9WdWeWtWwW}WWWW3WJWWWWWWWe-2QWeachWWWWW3W`WkWlWmWWWWeachbitofabitmapnvaluen8ii12isencodedasannVeachcharacterisencodedinorderofappearancewhereeachVeap-tls7Wearlier WeastWeasytWec/i02Wefficient=Wegprs&WeitherWWW(W+W-W6WDWEWJW`WdWWWWWWWIWWWWWWWW W WeitherauserandnetworkpolicyoruserandnetworkpolicieVeitheraddtlvtomessageorremoveparameterfromprimitiveIVIVIVelseiWelsewhereWenableWWWencodedWWWWencodingWencrypt7Wend7Wenhanced)Wentirely'W9WentitiesWWWWWWBWTjtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW;Ha8.2.1⒃' 8.2.2⮃⼃Ѓ㚃8.2.2.1փ׃⾃8.2.2.28.2.2.3Ճ8.2.2.48.2.3.1҃8.2.3.48.2.3.5.2Ӄ8.3.18.6.3.98.6.4.1ʃ˃8.6.4.2andWWWannexWWWW WannexdVannexe VannexfVannexjVannexlVbWWWWWWWWUWXWWb1.1VVVVb2.17Vb2.5VVb2.6Vb2.8UVXVVb-12WWb-4Wb14WWb2.11b2.6b2.8b2.9.1b4WWdWSTe WfWjWkᑃᒃᓃᔃᕃᖃᗃᘃlWmYWZWm1YVZVn/a⛃othersWWWsubclausetableWWWWWWWtableb-12VVtableb-4Vtableb14VVtableb4VVTcothersWfWotherwise~WWWWWWWoutW7W<WnWoWtWWWWWW<WWout-of-scope<WWWWoutdatedWoutline.WoutsideWW?WWWoutstanding WovWoverWWW WWWWWWWoverallW*WWoverflowWoverlapWoverlappingWoverlyWWoverviewWoverwriteWownWp180l52Wp183l132Wp284l61Wp673Wp683Wp73l1-4Wp802.1afWp802.21/d7.1%Wp99l122WpacketWWBWFW1WpacketsW(WWpageWWWWWFWbWeWqWwWWWWWWW/W6WUWpWuWwWyWWWWWWpagexvthetableofcontentsitemsh9.1andh9.2wraparoVWWWpositiveWpossibleWWWWf1jchooseW5WWcite4WcivicWclaim&WclarificationWclarificationofscopeforthisaspectswouldbeappreciatedVclarifiedWclarifyWWᴃWWW}WWWWJWWWWWWWWWWWWesentedacrossallliVclarifymappingtransportaddresswithmihfidVclarifyorcombineVclarifyorre-writeVclarifyorremoveVclarifythattheoldlinkactionsreferstothedestination}VclarifytheuseVclauseWWWWWWWWWWWWWWWWclear WGWclearly W WWW7WWWclearlydefinetheinfoquerybinarydataieorifitexistsadVclearlystateif802.16providesamechanismsimilartothe VclearsWcleverWcode4W_WWcodesWcodingWcollapsed%WcolumnWWW:WWL!cacknowledgementWWW'WacknowledgementforreceiptofmihmessagecanbereceivedeVacknowledgementsWacronym:Wacronymfor3gppspelledwrong:VacronymsGWHWWacrossW WWactionWWWWWPWQWeWwW8WWW_W`WlWnWsWzWWWWWactionsWWWWRWhWtWuWvWwW}WlWzWWWWWWwWW&WadWWaddWWWWWWWWaddabreviationVaddedW.WFWWMWaddingWaddition7W[WadditionalYWWWWWadditionallyFWJWadditionallythefollowingisapplicabletotheabove4commJVaddressWWWWWWW4W7WOWgWnWoWpWuWWWRWSWwWaddressesWWW WkWlWmWnWoWWJcshallWWWWWW?WWWWWW WWshallsWWshim6(WshipWshortestWshouldWWWWWWWWWWWWWWWWWWW W!W$W%W*W.W5WOWPWQWTWWWXWZWdWeWkWlWmWrWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WW.W/W0W4W6W7W9W>W?WCWDWpWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W"WWWshownWWshowsWWW*WwWWNWWWsibWsideW!W}WsidesIWWW%cthettheWtheWtheWtheWtheWtheWtheWtheWtheWtheoWtheWtheWtheWtheWtheWtheWtheWthe@WBWCWOWRWcWfWgWlWoWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhycdifferentWWWWWWWbWWWWWWW6WWWWWWWdifferentiatedWdifferentiatingWdifferentiation(WdifferentlyFWdifficultwWWWWdigitalWdimensionalWdirectWdirection[WWdirectionsWdirectly WdisappearedWdisassociatedWWdisconnectedWdiscoverWWW+WfWWWWWWWWdiscoveryWWWWWWWWWWWdiscussWdiscussedWWdiscussionWWWWWdistinctWdistributedWWWWWWWdoescurrentlinkidentifierrefertotheoriginalortargetVVdoesthescopeofthisstandardincludethefacilitationofVdoesn'tWWWWWWW W W,W0W7WeWrWsWwWdomain WVtljsimilarW W1W7W8W:WWWsimilarlyKWLWMWNWsimpleWsimplifyWsinceWsingleWWWkWlWmWWsize=WWW WsmeWsoWW%WwWWWgWsoftWsoftwaregWsolutionW W)W7Wsolve]WsomeWW WW.WWsomehowtWsomething W%W&WWsomewhere WW&WWsort7WsoundsvWsourceCWDWEWJWKWLWMWNWdWzW{WWWWWWWWWWWsupportedtransportliWsupportingWsupportsWsyntaxWsystemWtableWWWtargetWWtechnologiesWWtechnologyWtermWterminateWtermsWWtextWWWWWWthWthanWWWthatWWWWWWWWWWR*cwhenWWWWWWWW*WeWtWwWWWWWWWWWWW<W@WJWWWWWWWWWwhenatimeoutoccursincompletedstateweshouldnotrepoVVwhenatimeoutoccursinreceivedstateweshouldnotgenerVwhenanmihnetworkentitybroadcastsunsolicitedmihcapabiVwhenmorethanoneaccessnetworkcontainerispresentitisVwhenmorethanonepoacontainerispresentitisimportantVVVcommiܴVwhywouldthelinklayersmacmakehandoverdecisionsevenfܗVܘVwillW܅W܇WܞWܯWܱWwishܜWwith{W|W}W܁W܄WܙWwithinܸWwithout܇W܈WܡWܲWwork܈WܯWworst܌Wwould~WܗWܘWܝWxmlwWxmldoesnotcompilewVxxxxvWyet܈Wyet-to-be-defined܈WyieldWzero܁WQcreadWWreadability%WWWWWWreaderWWWreadersWWWreadilyWreadsWreadyWrealWWreal-lifeW&WrealizationWrealize'WreallyWWWWWWreasonableW=WWreasonsWWWreassemblyWreceiptWWWWreceiveWWeWuWWWreceivedWWW WpWtWWWWWWWWWIWreceiverWWIW Wreceives]WWreceivingWWWrecentlyWreceptionMWMWMWMWMWWWhW|WWWreestablishmentWreferWDWEWWWWWWrefertocontribution21-07-0317-00-0000-sinformationieVreferenceWWWWWWW WW-W8WdWiWWWWWWWWWW0WV^cisݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWݒWUcinteroperabilityWWWWinterpretationWintervalWWWintervalsaWinterworkingWintoWWWWWWWintra-technologyWWW8WWWWWintroduce6WWintroducesWWintroducingWintroductionWWinvokedWinvokesWinvokingWinvolved7WWinvolvementWipWOWgWkWlWmWnWoWpW>W?WWWWWWip-basedWipaddressinformation>W?Wipaddressinformationshouldbeoptionalasotheriprelated>Vipconfigurationmetho?Wipconfigurationmethoandipaddressinformationshouldbeopti?ViprenewalWipv6WWirrelevantWeed to be revised.d50g3381ionality, there is only a single place in the 802.21 standard which need to be revised.d50g3381 2007/09/1309/10/2007 07:08:58 EDT"caނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނWނW_kfcasWWWWWWWWWWWWWWWWWWWWWWW6W7W=WBWDWEWIWVWXW[W\W]WfWhWkWlWmWwW|W~WWWWWWWWWWWWWWWWWWW&W)W>W?WIWJWRWTWUWVWqWtWzWWWWWWWWWWWWWWWWWWWWWWWWW WWWaVasapWasking^WaspectWWWaspects7W)WassignmentWassistedWassisting<WassociatedWW WwWWWWassociatesWassociationWassociations7WassumeWWWWWWWassumedWWassumesWassumingWassumptionW'W7WWW@WWcbe~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W+cdifferent@diverse@ydoescurrentlinkidentifierrefertotheoriginalortarget@Ndon't@pdone@0eachbitofabitmapnvaluen8ii12isencodedasann@encoded@entry@everytime@examplequeryshouldbeforbinarydatainsteadoftlv@Wexamples@experience@factor@figure13is16pagesaway@7final@fit@flag@focused@forLforcommunicationbetweentworemotemihfsthepropagationf@from@gas@generation@fgeographic@ gsm/egprs@$handovercompleteispostedfollowinganimminenthoweverth@ohave@having@WAWpWWWWWWWWW2W3WWWWWWWWWprimitivesWWWWWW&WfWWWWWWWgWWWWWWWWprincipleWWpriorW7WWWWWWWratesWratherWWWrawWrdfWocreliableWreliesWWrelyWremaingWremainingWremoteWW]WeWxWyWWWWWremoveW)WWWremovesentence)VremovetheperiodfromthebeginningoftheparagraphVremovedFWrenameWrenamereferencepointsr1r5asj1j5orsomethingelsesinVrenewalWreorganize%Wreorganizetheannexesforexampleifindannexfandgand%VrepeatedWWrepeatedstatementVrepeatedstatementsVVVresenting=WreqWQWrequestWWWWW WW WDWEW[W]WfWgWiWqWtW~WWWWWrequest/indicationWrequest/responseWfWrequestedgWWWrequestingWWrequestorWrequestsWrequiredWWWWrequirementsWWWWW&W.WgWrequiresWreservationWWWWjtheݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWݥWVvcsomeWWWW7WJWWWWWW&W.WWWWW W WWtechnologiessuchas3gpprequirethepreparationofreVsomehowWsomethingWW]WWWsometimesWsomewhatWsomewhereWWWsoonWsort2WsortedWWWsouldWsoundWWWsoundsWWWsoundslikeyouareattemptingtore-definemechanismsthatVsourceCWDWEWJWKWLWMWNWWWWWWWWWWW Wsource/destinationWsparql-results<WspeakWspeakingWspecWWWW&WWWWWWWW WspecialMW WspecificWWWWWWW WWWW^WWWWWW(W)W7WWWWWWWWWWWWWWWcmay@mechanism@messages@mih@Nsumihheaderisafixedlength8bytes@mihnethocandidatatequeryrequestshouldcontainonlyque@mmihprotocolentitiesisnotdefinedandnotappropriateher@-mihfknowsonlyasourcemihfidanddestinationmihfidthe@mihftransactionacombinationofanmihfrequestorindicat@mishop@amisleading@mobile@mutual@l@orthetypeofpacketidentifier@2mobility@model@fpacketidentifier@2mobility@model@model@ctthatthisstanda@wnot@note@numbered@NofWHoff@on%onmessagesmihmnhocommitrequestandmihmnhocommitin@qonlyanmihfcapablenetworkentityshallrespondwiththis@Torder@Mothers@outside@parameter@periodicnotificationisonaperparameterbasis@7r@*read@andidatelinkbasisjwithWWWWWWWW WWW'W7W>WAWJWTWXW]W^WdWgWwWWWWWWWWWWWWWWWW)WNWOWRWSWlWWWWWWWWWWWWWWWWWWwithinWWWWWwithoutW<Wwithouth=WwordingWWworkWWWworking WworksWwouldWWW&W'WtWwWWwriteWwriting2WwrittenWWwwanWwwwWx+W7WNWxmlWxyz WW&W(Wy+W7Wyes4Wz+W7W7W7W7W7WWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHWHW9W:W;W<WnjacknowledgementWW'WacknowledgementsWacquire+Wacquisition+WacrossW%WactionWWW W7WtW}W7W8WnWsWWWWactionexecutiontimefromnetVactionsWtWvWwW}WWactivation0Wactive`WbWactual&W1WWactuallyWadaptWadaptationWWaddWWWWWWWWWW2WDWEW^W_WeWgWkWlWmWWWWWWWWWWWWWWWWW WWWWW&W.W4W8W=W@WIWJWMWUWWWhWnWrWsWxWyWWWWWWWWWWWWWWW Waddacallflowforfmipoperation&VaddacolumnwhichincludesthereferencetotheclausewherVVqueryrespongVWafterWW3jfunctionWWW&WiWWWJWWWWWfunctionalWWWfunctionalitiesWWWfunctionalityW&WWWfunctionsWWWWWWfurther?WkWlWmWWfutureWWfyi5WvWochangesinwirelVformUWformalߞW߭WvWvWochangesinwirelVformUWformalߞW߭WvWvWalone system. It means that having MIH_NMS_SAP for the interface with the NMS doesn't seem to be appropriate.d640g3664jDelete section 5.6.3.2 2007/09/1709/16/2007 23:46:35 EDTYes Technical_32`11cNMS is used for network management and is to be a stand-alone system. It means that having MIH_NMS_SAP for the interface with the NMS doesn't seem to be appropriate.d640g3664jDelete section 5.6.3.2 2007/09/1709/16/2007 23:46:35 EDTYesd640g3664jDelete section 5.6.3.2 2007/09/1709/16/2007 23:46:35 EDTYes.*YesEKwak, Joseph A, Joseph Aq'jroll-up8WrollbackWrouterkWlWmWWrowWrowsWrrc4Wrscp2WrspWWruleWrulingWsWsacnWWsameWWbWeWkWlWmWWqWsapWWWWWWWWW6WcWWWW W WW#W$WWWWWWWWWsapsW&WWsay WscanWhWWWWscanningWscenarioWschema-W.W0W4W5WWWWWWWWWWW%WXW[W\WhWseecommentforproposedresolutionVseepage66lines35-36andpage71lines32-33[Vseepage71line32-32\VselectedWselectionWWselectorWselfWsendWsenderIWsendingWsendsxWyWsense0Wsent7WvWWsent/receivedWsentenceWWservergWkWlWmW4jcomeupwithamoregenericparameterlistforthelinkupi Vcomes7Wcomformant&WcommaWcommandWWRW]WwWW W WnWsWWWcommandsWWcommentW%W&WWWWcommitWWJWtWvWwWxWyWWW W[WbWeWfWWWWWcommonWcommunicateWWWWWcommunicationWWWWWWcommunicationconnectionreferencetypeVcomplaince&WcomplementWcompleteWWWJWeWwWWWWcompletethecommandeventandinformationdefintionsforeaVcompletethereferencelistwhereverthetextreferencesanoVcompletedeWvWWcompletelyWcompletiondWtWcompliance&WWcomply/Wcomponent7WcomponentsWcomprisingWcomputing=W 6ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g5008jClarify or combinevpKeep MIH PoS (3.18) Delete MIH PoS Network Entity (3.19) Rename MIH non-PoS Network Entity to MIH non-PoS (3.21)eneral Interest^ Technical_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g5008jClarify or combinevpKeep MIH PoS (3.18) Delete MIH PoS Network Entity (3.19) Rename MIH non-PoS Network Entity to MIH non-PoS (3.21)reference or make a reference to a future sectionwAgree 2007/11/1809/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g5008jClarify or combinevpKeep MIH PoS (3.18) Delete MIH PoS Network Entity (3.19) Rename MIH non-PoS Network Entity to MIH non-PoS (3.21)Tjremovelines47-48andreplacebyareferenceorshortsumma,VremovelisttheflagisalsoselfevidentitcanberemovedVremovem6VVremovemihnethocandidatequerycommand VremovemihnetsapVremovemihnetsapfromthestandard VremovemihnmssapVremovemihnmssapfromthestandard VremoveoptionalfromsupportedisqueryparametertypeinmiDVremoveoptionalfromsupportedtransportlistinmihcapabilCVmovethechangebars!VremovethesentenceVremovethestackmarkedasremoteentityandremovetextlocVVremovethestackmarkedasremoteentityremovetextlocaleVVremovethetextaboutthearqmobileintroduceamechanismw VremovethewholesectionVremovethissectionseepage178lines23-43fordiscussionhVremovedWgWrenameWrenamer1r5asj1j5throughoutthedocumentVreperesent3Wrepetitive<W Disapprove 2007/09/17 dÃv2catdmpduWatdmsduWatleastWattachedWattachmentWWWattempt WattemptingWattemptsW WattributesW>W?WaugustWWauthenticated WW@WWauthenticatesWauthentication WWWWW)Wauthentication-wise WauthenticatorWauthor'sWauthorisation)WauthorisedWauthorizationWauthorsWavailableWWWWW WW'W+WkWlWmWnWoWqWWWWW*WWaverageWawareWawayWWWW3W4W5WWW/WNWWWb-10Wb-13Wb-15Wb-2Wb-8Wb-9Wb13WbackW WvWWbadWbadandpoorsignalstrengtharethesameinmymindVballotWmWbandsWbar!WbarsWbasedWWWWbasis[W`WkWlWmWWO"c8-octetWW8-octetvalueinorderofsignificanceV8.2MW8.2.3.5WW8.5W6W8.6WWWWWWWWWWWWWWWectingWWngWWWWWWs limited understanding of these terms.,}F DisapproveGGeneral Interest^ Editorial_149`62a 8.2.3.5.2cA"When the timer expires without receiving a response message, the requestor may try the combined MIH function discovery and capability discovery procedure using a different transport than previous or terminate the MIH function and capability discovery procedure."d571g5031jA "When the timer expires without receiving a response message, the requestor may try the combined MIH function discovery and capability discovery procedure using a different transport than previously or terminate the MIH function and capability discovery procedure." wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_149`47a 8.2.3.5.2cW"Only MIH network entity shall respond to broadcasted MIH_Capability_Discover request."d570g5032jY"Only MIH network entities shall respond to broadcasted MIH_Capability_Discover request." request.":pwaitWwaittillthelastreviewofthedraftVwasW#W,WOWRWSWWWwayWWweWwellWwhatWwhenWAWWWWWwhereWWwhethernWoWwhich/WWwhoseWWwillW3WWW/WAWWwimaxWwishWwithWWWWW WW0W3WHWWWWWWW W$WAWWWW WwithinWWWwithoutWAWwon'tWWworkW^WWwouldWWWwsaWx Wxxx1general Vx-refWWv0WWWW/W2W^WAW05WW07W1WWWWWWW/W0W2W3W<WWWAWWW1furtherclarifythatthepacketidentifierisacontainerVVVVVVVVVVVV[ disapprove€]] ]cthisthisclausepurportedlyspecifiesaprotocolyettherearenVthiscommentappliestothisclauseaswellastothedocumeVthisisredundantasitcanbeperformedusinglinkactionshVthisisthemaximumdatatransferratenotthemaximuminforVthisiswithregardtothefunctionalarchitecturefig4thaVacommonlyusedcommunicationstermanditisVthrougputWtimeWWWWWtimeoutsWtimerWtlvWWtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtooWtoolsWtransferWtranslateWWtransmissionWWtransmitWWWtransmittedW  ucAoSince Net_HO_Commit contains actions to effect the handover, and the response has the status of those actions, the link to the old PoS may not be accessible (e.g. break before make) to receive the response until after L3 connectivity has been established on the new link and only if the MN knows the old PoS L3 address thus, the old PoS may not receive this response.od409g5193vAAdd the following to clarify: "Since Net_HO_Commit contains actions to effect the handover, and the response has the status of those actions, the link to the old PoS may not be accessible (e.g. break before make) to receive the response until after L3 connectivity has been established on the new link and only if the MN knows the old PoS L3 address thus, the old PoS may not receive this response."w Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNo vERajkumar, AjayF GProducer^ Technical_120`12c120`12coS may not receive this response.ocalT cBuld not cross the theshold(s)? If so, then the L2 mobility manager in the mobile node should consume this report and it should not be sent up to MIHF. If the report is supposed to indicate that link parameters have crossed a threshold for the **best** link the mobile node's L2 mobility manager can find thus indicating that MIHF should consider roaming to another network, then that would be an appropriate use of this primitive.d95g5507jClarify the text.pAAdd the following description in the function subclause: "In case of 802.11 network, this event is generated when higher protocol layers wish to monitor the performance parameters for a network. These higher layers may be on the network side (for network initiated handovers) and MIHF on the local MN can transfer these paramters. For local MN initiated handovers, the local SME and MSCGF would monitor link layer properties and the MIHF would normally be interested only in the Link_Going_DownB .indication."QwAgree{k) done 2007/12/1909/16/2007 21:41:08 EDTYessWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g5008jClarify or combinevpKeep MIH PoS (3.18) Delete MIH PoS Network Entity (3.19) Rename MIH non-PoS Network Entity to MIH non-PoS (3.21)wAgreel_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g5008jClarify or combinevpKeep MIH PoS (3.18) Delete MIH PoS Network Entity (3.19) Rename MIH non-PoS Network Entity to MIH non-PoS (3.21)wAgree a future section 2007/11/1209/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g5008jClarify or combinevpKeep MIH PoS (3.18) Delete MIH PoS Network Entity (3.19) Rename MIH non-PoS Network Entity to MIH non-PoS (3.21)wAgreeoS Network Entity to MIH non-PoS (3.21)wAgree7jadditthereVaddmissinglisttothenameyVaddmissingmessagetolistWVaddmissingopeningbracketunsignedint2VaddmobilitymanagementieVaddnewstatediagramsorremovethiscapabilityandanyassMVaddperiodVaddr2UVaddtextinthisscenariothesourcemihnodemaysilentlydVaddtextseesection6.5.5formessageparametertlvencodinVaddtextthisisnotincludedifstatusisnotsettocode0VaddthedefinitionfornetworksecurityVaddthefollowinglinkactiontypelinkhandoveralsoaddth8Vaddthefollowingsentenceinannexbthisannexdefinesdat=Vnb-9VaddedWaddingWadditionWadditionalWWW.WadditionallyWaddressW WgWkWlWmW|WWaddressedWadjustment=Wadjustments=WadmissionWadoptWWadressWadvertiseWafterWwWWWuse in common MIH Aclinkconfigparamallowsonetorequestthatareportbegen149`16a8.2.3.4est contains DeviceStatesRequest parameter of type DEVICE_STATES_REQ. The type is a bitmap allowing to request different state information. However the response contains Device States Response List of type DEVICE_STATES_RSP. The type is a choice, thus containing only one elementd17g4936j?Define Device States Response List as LIST (DEVICE_STATES_RSP)  2007/09/1709/04/2007 16:19:39 EDTYesuE Seifert, RichF DisapproveGGeneral Interest^ Technical_149`16a8.2.3.4tates Response List as LIST (DEVICE_STATES_RSP)  2007/09/1709/04/2007 16:19:39 EDTYesuE Seifert, RichF DisapproveGGeneral Interest^ Technical_149`16a8.2.3.4d16g4937 2007/09/1709/03/2007 16:49:33 EDT-clabelWlabelled1WlackW(W+W,Wlack-of-itWlackingrWlanguageWlansWlargeWWlastWW/WWWWlater6WWWlatitudeWWlatterWWWWWlaughableWlayarWlayerWWWWWWWWW7W;W?WWWWWWWWWWWWWWWlayer2macandllcVlayer-dependentWlayer-specificWlayeringWWandlTWsupportedmiheventlisTWsupportedtransportliTWsupportingcWsupportscWsyntaxWsystemWtableWW>Wtarget<WZWtechnical߁WtechnologiescWdW߁WtechnologycW߁Wterm]WterminateJWterms WWtextWLWMWeWmWnW߂WthCWthan(W)WJWthatWW(W)WQW[W\WaWcWjW߁WWxG wlvA(Please verify) Change Available Resource Set description from "A list of available resource for each link." to "A list of available resources for each PoA in PreferredCandidateLinkList. The order of this list is the same as the PreferredCandidateLinkList." w PrincipleyRef 417{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNo o server addresses to the IP configuration methods since not all will be present)d418g5184jAAdd a statement requiring that the number of entries in each of the lists (LINK_POA_LIST and QOS_LIST) be the same; Combine Preferred Candidate Link List, Available Resource Set, IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address and IP Address Information Status into a single type and return a list of that type; Further, if resources on a candidate are dependent on a particular PoA then all of these parameters need to be on a link and PoA basis.w Principle 2007/12/07cannexWWWW%W.W5W9WWWWWWWW/W4W5WOWQWiWjWkWWWWWWWWWWWWWWWannexjdoesnotaddmuchvaluetothespecVannexjdoesnotaddvaluetothefinalspecVVVannexkisinformativeanddoesnotenforceuniformmappingVannexm6seemsredundantandnotaddinganyvaluegiventhaVannexm6seemsredundantandnotaddingmuchvaluebecauseVannexneedstobeupdateforconsistencytotherestoftheOVQViVjVkVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW$W&W.W4W<WJWKWLWMWNWeWkWlWmWqWWWWWWesWDTF(jserver'sWWserviceWW>W@WWWWWWWWWservicesWWW&WcWsession&WsetW'WeWkWlWmWWWWWWWW WD to indicate that the link address could be the address of an MN or a PoA 2007/09/1709/04/2007 16:19:39 EDTYesrE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_102`17ctypod19g4934jchange LINK_SACN to LINK_SCAN 2007/09/1709/04/2007 16:19:39 EDTNosE Golmie, NadaF DisapproveGGovernment/Military^ Technical_102cd18g4935 2007/09/1709/04/2007 16:19:39 EDT"zc802.11-2007W802.11gW802.11uWWW802.15WWW802.16WWW WWW802.16eW802.1abW802.1xWW802.21WWWWWWWW&W6W7WWWWWWWWWWWWWWWWWWWWEWWWWWWWWWWWWW802.21miissupportsstaticinformationparametershoweverfV802.21--yetW802.21-parW802.3WWWW9WW9.1W9.2W98eWEZ vmihyWWWWWWWWW'WAW}WWWWWWWWWWWWW W WmihfunctionsisusedinthepluralsenseofmihfunctionVmihlinkhoimminentmihlinkhandovercompleteVmihlinkupmihlinkdownVmihmnhocommitcommandnowforlocalonlyxVyVmihnmssaphasbeendeletedVmihscanisdeletedbyothercommentcmt444VNo.vby 407w Superceded{l) none needed 2007/12/1409/16/2007 03:08:31 EDTNo31 EDTNoxERajkumar, AjayF GProducer^ Technical_121`32cIn order to be able to perform a local handover (i.e. replacement for switch command) the destination MIHF ID would not be remote.d406g5196jChange that the destination may be local or remote. Also, specify that it sends a MN_HO_Commit.request message to the destination MIHF only when the destination is not local.v407w SupercededSuperceded:39 EDT;jandthismessageistransmittedovercontrolplaneusingalVand/orWWWWWWannexWWWWWWWW W%W&W.W5W9W=WWWWWWW'W/W3W4W5W=W^WcWWWWWWWWWWWWannex-kWannexes<WanotherWW&WW0WWanswers@Wany W&W'W/W7W<W]WgWwWWW=WMWWWWWanythingWanywayWapWapostrohpeWappeargWappearanceWappearsWapplicability<WapplicableW9WapplicationWapplication/sparqlWapplication/sparql-qW;Wapplication/xml:Wapplies3W9/04/2007 16:19:39 EDTNoqE Golmie, NadaF DisapproveGGovernment/Military^ Technical_118d20g4933 2007/09/1709/04/2007 16:19:39 EDT"ERajkumar, AjayF GProducer^ Technical_132`12cSThe first line references the MN MIHF (which is incorrect) as this is a N2N messaged383g5219jDelete the first linewAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_132`7c:It is the MIH User (not MIHF) that processes this message.d382g5220jChange "MIHF" to "MIH User".vChange "MIHF" to "MIH User".wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNolinewAgree{k) done 2007/12/1209/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_132`7c:It is the MIH User (not MIHF) that processes this message.d382g5220jChange "MIHF" to "MIH User".vChange "MIHF" to "MIH User".wAgree{k) done 2007/12/1209/16/2007 03:08:31 EDTNoo o o hange the PoA TLV to fixed type 2007/10/07386g5216j Change the PoA TLV to fixed type 2007/10/07:31 EDTE}vzDepends on 407...(MN_HO_Commit's actions depend on local node only) Clarify: These local actions are for local node only.w Principle{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNocup W$W0WvWWWW WW+W,WZW\W`WWWWWWup-to-dateWup/down[WupcomingWupdateWWOWQWiWjWkWupdates(WuponWWWupperWeWWWWWupper-layerBWuptoWusageWWWWWW&W@WWWuseWWWWWWWWWWWWWWW'W+W=WWWWWW WWGWHWlWWWWWWWWWWWWusecorrectpluralofmniemnsVusecaseWoܐWܱWܳWܴWܷWWWhow܈WܝWܟWܠWܯWWhowdoesthelinklayerknowthattheipaddressneedsrenewܝVhowever܀W܈WܯWWWWWhtml}Whttp}Wi܈WܯWܺWܼWWWid܎W܏WܓWܾWܿWideaW;E{ERajkumar, AjayF GProducer^ Technical_121`35cOThe "Current Link Identifier" is inconsistent with the other handover messages.d403g5199jIChange "Current Link" to "Source Link" for both the name and description.wAgree{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo {ERajkumar, AjayF GProducer^ Technical_121`35cOThe "Current Link Identifier" is inconsistent with the other handover messages.d403g5199jIChange "Current Link" to "Source Link" for both the name and description. Link Identifier" is inconsistent with the other handover messages.d404g5198jIChange "Current Link" to "Source Link" for both the name and description.wAgree{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo {ERajkumar, AjayF GProducer^ Technical_121`35cOThe "Current Link Identifier" is inconsistent with the other handover messages.d403g5199jIChange "Current Link" to "Source Link" for both the name and description.o ydeferredsameas497Vredsameas497VVredsameas497VVVredsameas497VVdefferredWdefferredrefcmt497VrefWWWWWWWWWWWWWWWref238Vrefcmt105VVrefcmt106VVrefcmt114Vrefcmt35Vrefcmt363Vrefcmt471Vrefcmt556VsameWWsee8W{€markedᆃᇃቃኃዃῃ㑃㒃㓃€noƒ %()*+,-./1349:;OPQRST[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⦃⧃⬃⮃ⱃⴃrstuv /cthethreeitemsmakeanormativeassumtionorevenstandardiVthetitleisnotdescriptive-Vthetitleisnotdescriptivemoreoversomedescriptionshoul.VthetypeanddescriptionforthehandoverstatusdonotagreVthetypeiecontainernetworkshouldcontainmeanstodiscovVthetypeiecontainernetworkshouldcontainthemeanstodiVVVtheirWWvWWWWthemrWsWWWWWWthemselvesWde supports only a single link layer technology, such as 802.11 ESS handovers." 2007/09/1709/16/2007 15:56:25 EDTYesdngle link layer technology.d546g4407j"In most cases, the mobile node is capable of supporting multiple link-layer technologies, which may be wireless or wired. However it is possible that the mobile node supports only a single link layer technology, such as 802.11 ESS handovers." 2007/09/1709/16/2007 15:56:25 EDTYesdd545g4408 2007/09/17VWV  cB= in the same broadcast domain by definition "authenticated" ?+d516g5086jA802.21 needs to clearly state working assumptions regarding authentication of underlying links and how an MIH entity implementing MIH protocol is expected to behave depending on states XYZ of the underlying access technologies. For example, state that "any locally originating request is considered authenticated vs. remote requests only when conditions XYZ are met (list may be different per access technology)". It is ok to say it is out of scope for 802.21, but the implementor needs a clearBR guideline where to look for a technical solution, otherwise no inter-operability.@vBThere is work being carried out by Security group to address this.w Principle{l) none needed 2007/12/1909/16/2007 13:36:45 EDTYes ERudolf, MarianF DisapproveGProducer^ Technical_71`54a7.3.10c7.3.10chernet, is any PoA trying to contact another onedrichardWWWWWWWWWrudolf W W W WWWWWWWW%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;Wrudolfmarian V V V VVVVVVVV%V&V'V(V)V*V+V,V-V.V/V0V1V2V3V4V5V6V7V8V9V:V;V*C=ELach, Hong-YonF DisapproveGProducer^ Technical_52`1c, Line 21 (i.e., Info Response Binary Data List, Info Response RDF Data List, Info Response RDF Schema URL and Info Response RDF Schema List) Page 137, Line 19 (i.e., Info Response Binary Data List, Info Response RDF Data List, Info Response RDF Schema URL and Info Response RDF Schema List)IwAgree{j) in progress 2007/12/0809/16/2007 06:10:15 EDTYes =ELach, Hong-YonF DisapproveGProducer^ Technical_52`1c_52`1ctype. Order of types should be according to items / paragraphs 1) through 5) of this sectiond47g5555jreorder table entirespDuplicate with 47{l) none needed 2007/11/1809/10/2007 07:08:58 EDTMarkedNoisapproveGAcademic^ Editorial_33`45a6.2.2cEFinal layout by IEEE editorial team will result in tables to "float".d46g5556jjReplace "The following set of service primites" with "The set of service primitves listed in Table 2 ...."{k) donec]handover decision making does not always require both, mobile node and network infrastructured32g5570j2insert "may": .... decision making MAY involve ...wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYessities according to the table starting at line 8d550g5052jQNumber the entities in Figure 2, according to the list starting on page 20 line 8 2007/10/3109/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_10`43a4al_20`8a5.4.2cIn Figure 2, you have numbered the communication links according to the classification scheme starting on line 21 of this page. You might alsoi want to number the entities according to the table starting at line 8d550g5052jQNumber the entities in Figure 2, according to the list starting on page 20 line 8 2007/10/3109/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_10`43a4jeitherchangecurrentlinkidentifiertosourcelinkidentifDVEVeitherchangen2nhocommittousesourceandtargetlinkidJVeithercorrectthislisttoindicatethatthesestatisticsaVeitherinserttheethertypeforl2mihifoneexistsalready-Veitherintroduceatleastaformaldefinitionforagsm/egpr6Veithernegotiateawindowsizeorsetitto1 Veitherprovideanormativerequirementforthenumberofpas VratewhyVelementWpWeliminateWelseiW'WelsewhereWenableWWW*WencodeWencodedWWWWencodingWWencrypt7Wend7WWWWWW4W=WWendingWendoWenhanced)WenhancementsWensureWWWWensuringWentireMWxWentirely'W9WentiresWWentitiesWWWWWWBWWWdRjchangerequestisreceivedtorequestmessageisreceived~VVchangesectiontosub-clauseasusedinotherplacesanother0Vchangesentencetothealgorithmdefined&maybeusedtocalcVchangetexttotheprimitiveisinvokedbyamihuseronanVchangetexttotheprimitivetosetparameterthresholdsthaVchangethatthedestinationmaybelocalorremotealsospecxVyVchangethedefinitiontobeconsistentwiththe802.21parVchangethedescriptionofresponselinkeventlistfromlistVchangethefollowingconventionsareusedVchangethelocationinformationsuchthatitisprovidingthVchangethepoatlvtofixedtypeVchangethesecondsentenceofdefinitioncolumntoifmimet:V;VchangethestacktonodeandremotestacktoremotenodeVa/ "higher layers" and b/ "MIH Users"d30g4923j 2007/09/1709/10/2007 07:08:58 EDTYes/jlinksW W7W%WWWlinktypeWlistWWWWWWWWWWWW W WW&W'W+W2WFWGWOWRW^WkWlWmWWWWWCWWWiWjWyWWWWlistallnormativereferencesoriftherearenonethenindiVlistdevicestatesrspVlistofsupportedcommandsonthelocalmihfVlistofsupportedeventsonthelocalmihfVWWWWWWWWWWWW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW6joneWWWW%W&W'W-W:WfWwWWWWJWRWSWdWlWwWzWWWWonepossibilityistomakethesemihfgeneratedprimitivesfVonewayforwardistohavemihusertomihuserexchangetakwVone-octetWonlyWWWW W WWWW&W'W/W0W5W<WxWyWW7WWWonlyanmihfcapablenetworkentityshallrespondwithmihcVonlymihnetworkentitiesshallrespondtobroadcastedmihcVopeningWoperate'WoperatingW1Woperation&W'WWoperationsWoperatorWoperator-4WoptimizationBWoptimizedWoptimizingWoptionWWW&WW WWWoptionalWWW&W]WgWWWWW>W?WCWDWJWoptionallyWoptions&W+WDTYesܧd597g3707 2007/09/17ivsayingWscanWWscanningWscenariosWschema<WWW6WschemeWW(WscopeW]WWWWWWWWsdo1WsearchWsecondWWsectionWW/W2W7WwWWWWWWWW0W6WGWIWWWWWWsection5.1.7hasbeendeleted7VVsection7.4.27VsectionsWWEWsections6.5.5andsection8.5addresssimilarissueVVWsentenceWWWW{W}WWsentencesWseparateWsequenceaWsequentiallyWserver'sWWservice5W@WAWWWWWWservicesWWWWset W WshallWWWWWW W WshouldWWW,WwWWEWshouldweaddsignalstrengthVshowW Wshowthebitorderinginthefigure VspeedWDT[jcombinations&WcombineWkWlWmWcombinedWcome W7WnV8.3.4WWWWationV8.3.4WWWWtionV8.3.4WWWWWWW.4WWW.3.4WWW.4WWerest^ Technical_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g3710jClarify or combine 2007/09/1709/16/2007 21:41:08 EDTYesܫESreemanthula, Srinvias3709j8remove reference or make a reference to a future section 2007/09/1709/16/2007 21:41:08 EDTYesܪESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_7`10a3.18cFWhat is the difference between "MIH PoS" and "MIH PoS Network Entity"?d594g3710jClarify or combine 2007/09/1709/16/2007 21:41:08 EDTYesܫESreemanthula, SrinviasEDTYesܫESreemanthula, SrinviasGGeneral Interestd593g3711 2007/09/1709/16/2007 21:41:08 EDThcidentifyWJWieWWW6WpWwWyWWWWWWWWWWWieeeWWWW WW7WWWWWWWWWWWWWWWWWWWWWW%WEWFWPWWWWWWW.W1W]WfWgWnWoWrWsWtWuWvWWWWWWifatleastonequeryisrequiredthereshouldbesomeminimViftheintentisfortwomihfstomutuallydiscovereachothfVifthemihgetinformationprimitivemustcontainatleastoVimminentWW_WwWimplementationWWWWWWWimplementationsWimplementing/Wimplementor'W,W7WimplementsWimplicitlyW WimpliesWimplyWimportantWWWimposeWWWWimpossibleWimprove%WimsiWf2joffers@Wok Wold WeW}WWWomitted:W;WonWWWWWWWWWWW W WWWW%W&W7W=W?WIWbWhWkWlWmWWWWWWWWWWWWWWWWWWWW!W"W)W8W^WcWqWWWWWWWWonline34replacetextforanmihackmessagewithforanmVߗVߗVߗVߗV09/1709/16/2007 18:16:08 EDTYesܮELevy, Joseph SF DisapproveGProducer^General required specified performance.d591g3713j@Provide additional requirements which will define MIHF Services. 2007/09/1709/16/2007 18:16:08 EDTYesܮELevy, Joseph SF DisapproveGProducer^Generald590g3714 2007/09/1709/16/2007 17:59:40 EDT6 @Q@C@pW@X@@@@Tj>@j@?@jj@j @ccjcAvA6v4cAjcAkjccAS@cv@cA\vAS@cB@Cv@g@pcA@g`@cAwe@v;@K@:EWF @ pAFvAj @J @@@v@@@d@8cA5C5C5C(v.+@,@-@/a0@1c3@N57@jFa4:㎃55.1.15.1.25.1.4➃5.1.55.1.775.1.8Ã5.2.15.2.3.55.3.1߃5.3.2.25.3.3.55.3.4݃ރ5.4.2ẃ5.4.35.5.15.5.25.5.3ۃ܃5.5.45.5.55.5.65.6.15.6.265.6.2.65.7.2ṃ'()✃كڃ̃6"#$6.2ⷃ6.2.1+6.2.26.2.5 *׃؃)6.3.1ⵃⶃ"㡃㢃tWreceivedܿWWreceiver7WreceivingܟWܠWWXWreceiving/sendingWrecipientWrecommendW#Wrecommendtomakeatleastk2andk3mandatoryeventually#VrecommendedWreduceWreestablishmentWreferencceGWreferencevWܩWWWW WWWW6WWWreferencesWWWWWW"W'W jprimitiveWW&WjWtWWWWWW7WWWWWprimitivesWWW&W@WcWfWtWWWWWWCWDWIWZW\WWWWprimitvesWWprinciple'WpriorWprioritiesWprioritizedWWpriorityWWproblem]WwWWproblems]WwWprocedureWproceduresWWWprocessWWprocessesWprocessing?WwWproduce'WproducedBWproformaWWproject:WproperWproperlyZW\WWpropertiesWproperty WproposeWproposedWprorityWWprotocolWWWW WWW%W&W+W7WBWWWWWWWWWWWWWWWWWWWWWWWWWprovideWWWWWWWWWWVmarian W W W WWWWWWWW%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;WmccannWWWWWWWWmccannstephenVVVVVVVVmeylemansWWWWWWWd587g3717jFRemove list. The flag is also self evident, it can be removed totally. 2007/09/1709/16/2007 16:08:43 EDTYesܲEWilliams, Michael GF DisapproveGProducer^ Technicalc}Link_Scan.response specifies MAC_ADDRESS (in Scan Response Set) Scan can be performed for network types without MAC_ADDrESSESd586g3718j"change from MAC_ADRESS to LINK_ID. 2007/09/1709/16/2007 16:08:43 EDTYesܳEWilliams, Michael GF DisapproveGProducer^ Technicalilliams, Michael GF DisapproveGProducer^ Technicald585g3719 2007/09/1709/16/2007 16:08:43 EDTca7.4.17.2.2P7.4.18Rh7.4.19Ãgⲃ 㞃7.4.19.1.17.4.19.3.27.4.19.4.27.4.2.1.2B7.4.207.4.20.3.2O7.4.22ឃ7.4.23Wᤃ7.4.23andothersV7.4.24ᣃ⯃ 㔃7.4.24.1.2W7.4.24.1.2andothersV7.4.24.2.2W7.4.24.2.2andothersV7.4.277.4.27.1.27.4.27.2.27.4.3 7.4.4ᧃ7.4.87.4.97.57.5.1.17.67.6.1.1.17.6.1.2.2722172227391741942742024742112I7422274222474231274232275112~88.1؃كڃ0@chavingWWWWWhe'Whe'sWheaderWWHWWWWWWheadingmWhelpWhelpfulWWhelpsWhenceWhereWWWWWWJWWWWwWWheretargetpoaisspecifiedasmacaddressaswellasinmnVhessidWheterogeneousWWWWhexNWhigherWWWWWWWhighestWhighlyWhoWWWWWWWJWKWLWMWNWeWgWiWqWrWsWtWuWwW~WWWWWWW W W WIWKWTWUWVWYW[WWWWWWWWWhocWWhoghooghiWhome WWhopefullyWmann, MarcF DisapproveGAcademic^ Editorial_17`32a5.3.4c&incoherent usage of singular or plurald36g4917 2007/09/1709/10/2007 07:08:58 EDTNo cB placement of the handoff function to the detailed design of messages and information elements. It is completely unclear how the functions and information provided by this draft would fit within the framework of the established 802.1X standard, the EAPOL protocol and its use of EAP, and the P802.1af amendment. Security of information transfer is required, but a major issue in handover/roaming/discovery in secured networks is determining the policy for making tentative decisions on uC;nsecured information and confirming those decisions later.d650g5604wDisagree{l) none needed 2007/12/1909/17/2007 18:08:47 EDTYesd645pA% In this draft we will still keep it this way so that we won't forget to update it. If we update the URL with a bogus address, it may cause confusion. Decision should be "Principle" Resolution is: "A valid URL will be placed when a persistent URL is assigned within next couple of revisions." %stuvoMP{kQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWnWoWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWW to the rest of the documentd189g5413j6`4cIEEE Style is not appliedd190g5412j"Change "This table" to "Table L-4"wAgree 2007/11/3009/13/2007 13:56:26 EDTMarkedYesQE Cypher, DavidF DisapproveGGeneral Interest^General_284`1cDAnnex needs to be update for consistency to the rest of the documentd189g5413jto be update for consistency to the rest of the documentd189g5413j x 200m). If the 19th bit has a resolution of 100 m, then the square cannot be 200m x 200m. Since only the change is to go from corner to corner is represented by hex "c" to "d" or "b" to "c".d192g541009/14/2007 16:50:16 EDTV9avremove 802.15 from Figure 1 and from page 4, line-14. Leave it on page 2 where it is used as an example to describe pico cells.w Principle{k) done 2007/12/1909/16/2007 01:46:33 EDTYess it is not specifically defined within this base standard.vremove 802.15 from Figure 1 and from page 4, line-14. Leave it on page 2 where it is used as an example to describe pico cells.w Principle 2007/11/2609/16/2007 01:46:33 EDTMarkedYes 2007/11/1809/16/2007 01:46:33 EDTMarkedYesEMccann, StephenF DisapproveGProducer^ Technical_2`33ifically defined within this base standard.vremove 802.15 from Figure 1 and from page 4, line-14. Leave it on page 2 where it is used as an example to describe pico cellsw Principley Ref Cmt 363 2007/10/0709/16/2007 01:46:33 EDTYesEMccann, StephenF DisapproveGProducer^ Technical_2`33phenF DisapproveGProducer^ Technical_2`336:33 EDTYesa*E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_61`42a7222cSThere is only one Primitive listed in Table 11, however the text is in plural form.d135g5467j)Change "primitives are" to "primitive is"wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s nly one Primitive listed in Table 11, however the text is in plural form.d135g5467j)Change "primitives are" to "primitive is"wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedYes te MIHFs?)vChange as follows on pg 83 line 27 " Registration request code. Depending on the request code, the MIH User can choose to either register or re-register with the remote MIHF "wAgree 2007/12/0109/13/2007 13:56:26 EDTMarkedYesE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_71`14a7391cSentence is missing punctuationd136g5466j Add period{k) done 2007/12/0109/13/2007 13:56:26 EDTYes EDTMarkedjrequestWWW WWtWvWwWxWyW~WWWWWWW W*WbWeWfWWWWrequest/indicationWrequest/responseWOWrequestedWWWWJWWWrequesting^WrequestorWrequests WrequiredWWWWWrequirement&WW WrequirementsWWWWWWWWrequiresWrequiringkWlWmWreservationWW W*WWWreserveWreservedWresideWresolutionWresolved&WresourceWkWlWmWWWWWWWWresourcesjWkWlWmWrWsW W*WKWrespectWWWWW]WgWjWtWvWWWWWWWWCWDWWresponse/confirmWresponsesWresponsibility]WresponsibleWrest5Wrestrict'WWljclarifytheuseVclarifywhetherthisisamistakeieaddoptionaltotlvorJVclauseWWWWWWWWWWWWWWWWLWXWWWWWclausesWWclear WGWWclearly W WWW7WWWWclearlydefinetheinfoquerybinarydataieorifitexistsadVclearlystateif802.16providesamechanismsimilartothe VclearsWcleverWcloudWcode4W_WWWcodesWcodingWcollapsed%WcolumnWWW:Wor target MIHF to the other (i.e. peer) MIHF indicating the status of the handover completion." 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_97`4446c GProducer^ Technical_97`4446cd425g4528 2007/09/1709/16/2007 03:08:31 EDTleteannexjVdeletecurrentlinkidentifiefromallmihhandoverprimitivesVcisisannexeneeded9VisitthenumberofclassesofservicecosasthedefinitionqVistherecommendationvalid802.11isnotprovidinganymanaVisthisawishlistordoesanylinklayeractuallysupportVisn'tW WvW"d580g3724j"Longitude should be normalized to within +/- 180 degrees. Positive values are East of the prime meridian and negative (2s complement) numbers are West of the prime meridian." 2007/09/1709/16/2007 15:56:25 EDTYesܹEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_175`5aB.1.1n."d580g3724j"Longitude should be normalized to within +/- 180 degrees. Positive values are East of the prime meridian and negative (2s complement) numbers are West of the prime meridian." 2007/09/1709/16/2007 15:56:25 EDTYesܹEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_175`5aB.1.1 Interest^ Editorial_175`5aB.1.1d579g3725 2007/09/1709/16/2007 15:56:25 EDTEFamolari, DavidFApproveGGeneral Interest^ Technical_153`6c_[8.6] For extendibility of MIH, there is a need to allow defining experimental TLV type values.d501g5101j$21-07-0312-00-0000-extendibility.doc.1, page 149, line 42: Since sending or listening to an unsolicited MIH discovery response is an optional feature and an exception to the way normally the protocol works (a response is sent/received only after receiving/sending a request), this option is not represented in the transaction state machines aboveLpWAW]W^W_WjWpWtWvWwW~WWWWWWWWWWWWWWWWWWWWWWWWWW WWW#W$WIW|WWWWWWWWWWWWWWWWWWWWWWWWWenormous+WenoughݡWݤWenterWWentire܅WݚWWކWentitiesܗWܘWܫWWWW0WWentityܧWܪWܾWܿWWWWWW.WޥW޲WentriesYWZW[WentryܔWޛWenumerated'Wequal~WWequationWequipment W}) ?{doneWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWWW W!W"W$W)W,W-W.W0W1W2W4W6W:W;W<W>W?W@WAWBWCWDWEWFWHWKWLWMWNWOWPWQWRWSWTWVWXWYWZW^W`WaWbWcWdWeWfWgWhWiWjWkWmWnWoWpWrWsWtWuWwWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWook at comment 384 and changes made therein. Changes to be made on top of change specified in comment 384 Plesae refer to 21-07-0396-01-0000w Principle{i) to do 2007/12/07L|cplacesWZW\WWplaneWW7WWplaysWpleaseWWWWWWjT E Jette, AlanF DisapproveGProducer^ Technical_63cMIH_NMS_SAP is used to interface between an MIHF and a local Network Mgmt System (NMS) stack. The local NMS stack should be left up to the implementation.d259g5343j$remove MIH_NMS_SAP from the standardpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/19 to the MN. Thereafter the Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagree{c) instructions unclear 2007/12/0709/14/2007 14:42:22 EDTMarkedYes E Jette, AlanF DisapproveGProducer^ Technical_63cMIH_NMS_SAP is used to interface between an MIHF and a local Network Mgmt System (NMS) stack. The local NMS stack should be left up to the implementation.d259g5343j$remove MIH_NMS_SAP from the standardpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/07t 106 2007/11/141cinFWGWHWIWJWMWRWYWZW\WlWrWtWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWnder way in 802.3 to define power management features that will interact with the MAC operation - e.g., by changing data rates - what is the relationship between the .21 work and these kinds of features in wired LANs?power management features that will interact with the MAC operation - e.g., by changing data rates - what is the relationship between the .21 work and these kinds of features in wired LANs?ct with the MAC operation - e.g., by changing data rates - what is the relationship between the .21 work and these kinds of features in wired LANs?WUWUWcaccomplishedWaccordingWWW"W#WKWLWMWNWWWWaccordingtotableb-2page176networkerrorisindicatedbVaccount~WWWaccrossWackWWWWWWWWWW'WWackfailureisnotrelatedtoplrackfailureisatransmitVack-rspWWack/repMWt is "simply out of scope". The minimum that 802.21 must describe is where the signalling or some of the services (notably, command service) it provides is dependent on prior sility, I also think it is too simplistic to say it is "simply out of scope". The minimum that 802.21 must describe is where the signalling or some of the services (notably, command service) it provides is dependent on prior sd471g4482 2007/09/1709/16/2007 07:13:12 EDT cAThe text states that the link down notification is delivered when a L2 connection is broken on the specified link and no more packets may be sent on the specified link. From this definition, it appears that a link down event will be generated whenever an STA makes a transition from 1 AP to another; this is out-of-scope for 802.21 which is facilitating inter-technology and intra-technology (when these are between different networks--e.g., different SSIDs in WLANs) handovers. The text in 7.3B.5.4 also states that this event may be passed to the MIH user which is interested not in L2 transitions, but in handover between networks.yd92g5510jmCorrect the text to state that link down is generated whan all possible L2 links to a given network are down.p3remove all definition and mentioning of MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/11/2609/16/2007 15:23:06 EDTMarkedYesd538g5064cription߇WsubsequentWypYcdoescurrentlinkidentifierrefertotheoriginalortargetVVdoesitmeanthatthelowestnumberedsuchoctetisfirstorVdoesthescopeofthisstandardincludethefacilitationofVdoesn'tWWWWWWW W W,W0W7WeWrWsWwWWdomain WW/09/1709/16/2007 03:35:02 EDTNoECheng, Yuu HengF DisapproveGGeneral Intereston of "Target Link Identifier" to "Specifies the intendend target link of the handover). 2007/09/1709/16/2007 03:38:14 EDTYesECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_111`48a 7.4.20.3.2c(Kenichi) IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address, and IP Address Informaiton Status should be list.d447g4506jXchange those datatype as LIST(datatype). 7.4.20.4.2, 7.4.21.3.2, and 7.4.21.4.2 as well. 2007/09/1709/16/2007 03:35:02 EDTNoECheng, Yuu HengF DisapproveGGeneral InterestTclintWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcolbanWWWcolbanerikaVVVcoleEWFWGWHWcoleterrylEVFVGVHVcypherIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWfamolaridavidVVVVVVfederCWDWEWFWGWHWIWJWKWLWMWNWfederperetzCVDVEVFVGVHVIVJVKVLVMVNVE Xie, QiaobingF DisapproveGUser^ Editorial_174cQThe entire Annex B is poorly organized. The grouping is not clear nor consistent.d354g5248te Network Securityw Principle 2007/12/0709/15/2007 22:08:13 EDTMarkedYesE Xie, QiaobingF DisapproveGUser^ Editorial_174cQThe entire Annex B is poorly organized. The grouping is not clear nor consistent.d354g5248initionvDelete Network Securityw Principle 2007/11/3009/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^ Editorial_174cQThe entire Annex B is poorly organized. The grouping is not clear nor consistent.d354g5248issing definition must be filled.d355g5247jDefine the missing definitionvDelete Network Securityw Principle 2007/11/1809/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^ Editorial_174cQThe entire Annex B is poorly organized. The grouping is not clear nor consistent.d354g5248:46:33 EDTYesz crdfW.W4W6Wre-associatesWre-defineWWre-definingWre-drawnWre-establishWre-transmit'Wre-transmittedWWWreachWonalWWWWWWWWWWWWWoptionallyiWiWiWiWiWlyiWiWiWiWiWiWiWWWWWWWWWoptionallyiWiWiWiWWWWWWWWoptionallyiWiWiWiWiWiWiWallyiWiWiWiWiWoptionsߢWnsߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWߢWWWWWoptionallyiWoptionsߝWߢWߢWߢWWWWWoptionallyiWoptionsߝWߢWߢWߢWߝWߢWߢWߢWߢWߢWߢWߢWWWWWW.W7W<W[WnWoWwW{WcwhenthemihtransportisreliabletheacknowledgementmechaVwhenthemimetypeisapplicationsparql-resultsxmlthisfi<VwhenthetimerexpireswithoutreceivingaresponsemessageVwhen/ifWwheneverbWWWWWWwheneverapplicabletheieee802.21standardshalluseexistVwhereWWWWWW W7WKWLWMWNWWWWWZW\WgWWWWwherearethenormativereferencesVwhereasWWwhereinWwhetherWWzWWWWWWWWW WWWWWWWWWWWWWWW WWW%W'W+W7WIW]W^WwW|W~WWWWWWWWWWWWWW/W@WMWZW\W^WcWWWWWWWWWWWWWWWW%ctgkWthWthanWWWWWWW&W=WgWWWWWthatWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWW1W7W<W=W?W@WFW802.16 MIH MAC management message." 2007/09/1709/16/2007 15:56:25 EDTYes2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_153`37a8.6.1.1c"and this message is transmitted over control plane using L2 management frame, such as 802.11 management action frame and 802.16 MIH MAC management message."d572g3732j"and this message is transmitted over control plane using a L2 management frame, such as a 802.11 management action frame or a 802.16 MIH MAC management message." 2007/09/1709/16/2007 15:56:25 EDTYesd571g3733 2007/09/17ttvtguWWWWWW@WWWWWWWtguneedsthisfeatureincurrentversionofdraft@VthanWW&WAWthatWWWWWWWWWWW&W'W@WEWiWWWWWWWWWWAWEWWWWW Wly it's referring to a link in a different network. If it's referring to another PoA in the current network, then the Link_Detected event will be sent to the higher layers constantly (e.g., whenever a neBJw AP is detected in a WLAN). This does not help inter-technology handover.8d94g5508jClarify the text. 2007/11/1209/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_69`25a7.3.6.3coveGProducer^ Technical_69`25a7.3.6.3cnetwork, then that would be an appropriate use of this primitive.d95g5507jClarify the text. 2007/10/07WޞWlcinterfacesWWWWWintermixed/WinternalEWWinternetWWWWWWWyouWWWWWWWWWWWWWWJWyesvWyet|WWyouvWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWzero W W WWWzero W W W W WEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145en only twice. Note that the IEEE SA has ruled that state diagrams are normative, which means that the state diagram must be correct.)d569g3735j6Update the state diagram to match the text description 2007/09/1709/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145oveGGeneral Interest^ Technical_145d568g3736 2007/09/1709/16/2007 15:56:25 EDT:<EmeylemansWWWWWWWWW5.5.2cFig 11 conflicts with Figures 9 and 10 for 3GPP and 3GPP2. Fig 11 correctly includes the MIH_LINK_SAP whereas the latter two illustrate an MIH_3GLINK_SAPd42g4911jChange Fig. 9 and 10 2007/09/1709/10/2007 07:08:58 EDTYes\EEmmelmann, MarcF DisapproveGAcademic^ Technical_25`1a5.5.2ccFig 11 conflicts with Figures 9 and 10 for 3GPP and 3GPP2. Fig 11 correctly includes the MIH_LINK_SAP whereas the latter two illustrate an MIH_3GLINK_SAPd42g4911jChange Fig. 9 and 10 2007/09/1709/10/2007 07:08:58 EDTYes\EEmmelmann, MarcF DisapproveGAcademic^ Technical_25`1a5.5.2cter two illustrate an MIH_3GLINK_SAPd42g4911jChange Fig. 9 and 10 2007/09/1709/10/2007 07:08:58 EDTYes\EEmmelmann, MarcF DisapproveGAcademic^ Technical_25`1a5.5.2cAcademic^ Technical_25`1a5.5.2cd41g4912 2007/09/1709/10/2007 07:08:58 EDT?_Ã(@%/xÃ(P̃̓΃⎃⬃=㘃Ã(`˃uvÃ(34Ã(78Ã(⍃stÃ)FGÃ) 2Ã)0Ã)Pៃ᠃01Ã)pᇃqrÃ)ŃÃ)Ã* XÃ*0Ã*@ᆃᛃᜃUÃ*P/ƃÃ*`Ã*pኃÃ*;<Ã*:pÃ1ănoÃ1@⫃mÃ1PKlÃ1`9Ã1ቃT.kÃ2㐃㑃Ã2PyÃ2`wÃ3SÃ3 9Ã3PjÃ3p-iÃ3hÃ4 gÃ60fÃ6peÃ6dÃ6& interoperability to be expected between two independent implementations that might claim conformance to this standard. d649g5603 2007/10/0309/17/2007 18:08:47 EDTMarkedYesE Jeffree, TonyF DisapproveGProducer^GeneralcqjfigureWWWWW*WHWWWWQWWWWWWWWfigure-7WfirstWWWW&WbWWWWWfirstintroducesomethinglikeapicssomewhereintheannex&VfixWWWW WWWfixthefontthisisthereisseveralotherplacesindraftVfixthemodellingsothatthestandarddoesn'tplayfastandVfixthepdfand/orthetextsothepagenumberscorrespondVfixthetext V 2007/09/1709/16/2007 15:56:25 EDTYesShe requests within each category are prioritized from highest to lowest. However, if more than one of these categories are present, how are the categories prioritized? Are the first items in each category that is present have the same priority?md563g4390j:Define the priorities of the items in different categories 2007/09/1709/16/2007 15:56:25 EDTYesSd562g4391 2007/09/17W$WgLg5152jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p7Remove the intended, since it is HO_Complete primitive.wAgree{k) done 2007/12/1909/16/2007 03:38:14 EDTYes s ource link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).wAgree 2007/12/0109/16/2007 03:38:14 EDTMarkedYesLE Feder, PeretzF DisapproveGProducer^ Technical_131`54cA The description of the "Source Link Identifier" and "Target Link Identifier is confusing. For the case where the MN_HO_Complete message is sent to the new target PoS then source and target link identifier are one and the same (At least according to the description). d450g5152k of the handover).wAgree 2007/10/31/2007 03:38:14 EDT{jBinvestigate if this capability is needed and how to best implementv21-07-0305-02-0000w Principley Ref Cmt 114{k) done 2007/12/1909/15/2007 22:08:13 EDTYes he conditions will be reported.d350g5252jBinvestigate if this capability is needed and how to best implementp(- change needed in section 7 and annex Bv21-07-0305-02-0000w Principley Ref Cmt 114{j) in progress 2007/12/0809/15/2007 22:08:13 EDTYes s E Xie, QiaobingF DisapproveGUser^GeneralcMIH event subscription should allow the subscriber to set certain conditions to qualify the events, so that only those events that meet the conditions will be reported.d350g5252jBinvestigate if this capability is needed and how to best implementp(- change needed in section 7 and annex Bv21-07-0305-02-0000w Principley Ref Cmt 114{j) in progress 2007/12/0109/15/2007 22:08:13 EDTYes l_51`25a6.5.4cThe sentence is ambiguous.d349g5253g5253jinbothline38and37changedefaultvalueformime-typefroVinchapter8.6.4.2mihgetinformationresponsechangethetVinmostcasesthemobilenodeiscapableofsupportingmultiVinthecaseofremotediscoverythisprimitivemaycontaintVinthetablesthatdefineprotocolmessagesincludearefereVinabilityWincludeWWJW|W09/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_143`7a8.1If the two terms are syonymous, then be consistent in usage. If the two terms do not refer to the same thing, then please use two terms that are not so close to each other.d565g3739j#See comment for proposed resolution 2007/09/1709/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_143`7a8.1d564g3740 2007/09/1709/16/2007 15:56:25 EDTH109/16/2007 21:41:08 EDTYes s t^ Technical_41`3a6.3.5cA`Desciption on Link_handover_imminent and its MIH counterpart indicate that the L2 somehow decides that handover is necessary. This goes against the very first MIH design principle set forth in section 5.2.1. Who makes handover decisions? Is this event equivalent to a parameter change if configured or a predictive event that the link may be down soon?`d601g5001jClarifypper 21-07-0430-00-0000v/Please refer to contribution 21-07-0430-00-0000w Principle{k) done 2007/11/2809/16/2007 21:41:08 EDTYesalent to a parameter change if configured or a predictive event that the link may be down soon?`d601g5001jClarifypper 21-07-0430-00-0000v/Please refer to contribution 21-07-0430-00-0000w Principle{k) done 2007/11/2809/16/2007 21:41:08 EDTYeses 2007/11/2809/16/2007 21:41:08 EDTYesciple 2007/11/18IWW.?* 2007/12/1909/14/2007 02:24:47 EDTYessre 16 is confusing by showing two unrelated stacks. Showing one stack would be good enough.d347g5255he serving PoS to the UE, but the UE won't be able to query the candidate networks unless the UE is connected to the candidate networks. That assumption is highly unlikely.d348g5254jJremove all definition and mentioning of MIH_Net_HO_Candidate_Query commandwDisagree 2007/11/1809/15/2007 22:08:13 EDTMarkedYesE Xie, QiaobingF DisapproveGUser^General_42`5a6.4.1c_Figure 16 is confusing by showing two unrelated stacks. Showing one stack would be good enough.d347g5255ndidate_Query commandwDisagree 2007/11/1809/15/2007 22:08:13 EDTMarkedYesE Xie, QiaobingF DisapproveGUser^General_42`5a6.4.1c_Figure 16 is confusing by showing two unrelated stacks. Showing one stack would be good enough.d347g5255nlikely.d348g5254cindicatesWWWWWWWindicating_WgWWindicationW W W WeWtW~WWWWWWWIWZW[W\W_W`WaWWWWWWindication/responseWindicationsWW W]WindicatorWindividualWGWindividuallyWinefficiencyWinexact@WinfoWWWWWWinformaitonOWinformationWWWWWWWWWWWWW%W=W>WAWgWnWoWWWWWWWWWWWWWWWWWWWWWWWWW)W4W6WIWpWWWWWWWWWWWWWinformationelementsbeforethemnisauthenticatedwiththeVinformationonhowtoextendtherdfrepresentationshouldb4VinformationalWW1EEmmelmann, MarcF DisapproveGAcademic^ Technical_60`53a7.2.2.1cKeep the main part of the standard technology independent and do not reference all / a range of tables in Annex L for technology specific mapping. Simply say that such a mapping is found in Annex L.d53g5549jReplace this paragraph with: "The primitives defined as part of the MIH_LINK_SAP are described in Table10. Annex L contains their mapping to several specific link technologies. "wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYes EEmmelmann, MarcF DisapproveGAcademic^ Technical_59`15a7.1cAwitems a) through e) contain a mapping of the MIH_LINK_SAP to media-dependent / technology specific SAPs. There are two issues with this. First, such a mapping of 802.21 functionality to a specific technology is very beneficial but should be included in a (possible normative) Annex. Second, such a mapping should be structured by "technology" and not by the name of the SAPs.wp_@ăσ`ᾃ8⠃⢃p;⟃⡃GHÁἃὃABF‚!:‚"‚#‚$7➃Â%?@‚&ể߃‚'‚(ƒރ‚)‚*ẃ‚1‚2‚3‚4Ꮓᐃ‚6܃‚7ۃ‚8‚:>‚A‚B6⹃ $㥃㬃‚Cᎃṃ'()✃كڃ̃‚Dῃ$+ⷃ㣃‚‚‚\‚‚eÃ![Ã!0QÃ!@PRhÃ!`Ã!Ã!Ã!giÃ"jÃ" OmoÃ"0lÃ"@knpÃ"PqsÃ"`rÃ"ឃᢃ Ã"tÃ#uvÃ# ᝃᤃwxy{|}Ã#0ᣃz~Ã#@⁃Ã#P᥃Ã#`Ã#CÃ#E℃⅃Ↄ?CEMccann, StephenF DisapproveGProducer^ EditorialcBStrictly speaking references to IEEE 802.21, are self-referential.d361g5241j3Replace "IEEE 802.21 standard" with "this standard"{k) done 2007/12/1909/16/2007 01:46:33 EDTYesEMccann, StephenF DisapproveGProducer^ Technical_2`12c|Does the scope of this standard include the facilitation of handovers between heterogeneous networks during emergency calls.d360g5242j=Clarification of scope for this aspects would be appreciated.pmdiscussion with the commentor concluded that nothing needed to be done within the 802.21 spec to support thisv)Michael/Stephen to provide explanation...w Principleydeferred{l) none needed 2007/12/1909/16/2007 01:46:33 EDTNo EMccann, StephenF DisapproveGProducer^ Technicalnism, which may provide useful information to the MIHF IS. Comment forwarded by IEEE 802.11u chair on behalf of IEEE 802.11u Ad Hoc Meeting, 30th August 2007.d359g5243ed.?JE Cypher, DavidF DisapproveGGeneral Interest^General_10`6a4a64311cATable 5 does not include the MIH_Link_Actions as a command. Throughout the document there appears to be a problem differentiating between MIH_Scan and MIH_Link_Actions. If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses.d129g5473j]If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses.vby 444 MIH_Scan is deletedw Superceded{l) none needed 2007/12/1409/13/2007 13:56:26 EDTYes E Cypher, DavidF DisapproveGGeneral Interest^General_10`6a410`6a4d129g5473j]If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses.vby 444 MIH_Scan is deletedw Superceded{l) none needed 2007/11/2609/13/2007 13:56:26 EDTMarkedYesE Cypher, DavidF DisapproveGGeneral Interest^General_10`6a4MarkedYes:ERudolf, MarianF DisapproveGProducer^ Editorial_10`7a4cAcronym for 3GPP spelled wrongd468g5134jPChange to "3rd Generation Partnership Project", similar for 3GPP2 one line below{k) done 2007/12/1909/16/2007 07:13:12 EDTNo;ERudolf, MarianF DisapproveGProducer^ Editorial_6`63a3.15c"UMTS Layer" is ambiguousd467g5135j"the 3GPP lower layers are L1, MAC, RLC and PDCP in the case of W-CDMA FDD/TDD and L1/LAPDm in the case of GSM CS and L1/MAC/RLC in the case of GPRS/EGPRS"{k) done 2007/12/1909/16/2007 07:13:12 EDTNoEWilliams, Michael GF DisapproveGProducer^ Technicalc,no Info Response Binary List TLV in Table C2d583g4370jIn chapter 8.6.4.2 MIH_Get_Information response change the table entry from "(Info Response Binary List TLV)" to "(Info Response Binary Data List TLV)" 2007/09/1709/16/2007 16:08:43 EDTYes?chael GF DisapproveGProducer^ Technicalc,no Info Response Binary List TLV in Table C2d583g4370jIn chapter 8.6.4.2 MIH_Get_Information response change the table entry from "(Info Response Binary List TLV)" to "(Info Response Binary Data List TLV)" 2007/09/1709/16/2007 16:08:43 EDTYes?d582g4371 2007/09/17casanexampletheieee802.11lowerlayersarethemacsublaVasapWasking^WaspectWWWaspects7W)WassessWassignmentWassistedWassisting<WassociatedWW WwWWWWassociatesWassociationWassociations7Wassociations/andWassumeWWWWWWWassumedWWassumesWassumingWassumptionW'W7WWW@WF DisapproveGGeneral Interest^ Technicala7.3.6ct of supported events on MIHF."d557g4396j-"List of supported events on the local MIHF." 2007/09/1709/16/2007 15:56:25 EDTYesYEChaplin, Clint FF DisapproveGGeneral Interest^ Technicala7.3.6cd556g4397 2007/09/1709/16/2007 15:56:25 EDTW݊W݊W݊W݊W݊W݊W݊W݊WtocommaݰVfrom/toWfroms#WfrontW݊W݊W݊W݊WW݊W݊W݊W݊W2r cB>yering as defined in this (or any) standard; indeed, there may not be any defined or exposed interfaces corresponding to the service primitives defined here. Thus, while this clause may be useful in defining the information manipulated within a system, conformance to this clause is not necessary for interoperability.,d12g5590jjDelete all "shall" statements and conformance requirements for this clause and all service specifications.vAThe term, "shall", as per the IEEE Standards Style Manual (Dated January, 2007) clause 13.1, is used properly. The 802.21 protocol requires interaction with entities (e.g. above and below) through service access points (SAP). To accomplish this requirements on behavior must be specified. The use of the words, shall, are necessary to describe this behavior. There are no requirements placed on the implementation of the SAP or coding of the information as is the current practice within tB he IEEE 802.wDisagreet€Yp)ERudolf, MarianF DisapproveGProducer^ Editorial_32`35a5.7.2cRemove sentenced485g5117j"For example, wireless networks & could be enhanced for carrying the MIH messages." This is a standard that describes a technical solution, not a conference paper that describes what *could* be done (in theory).premoved the examples{k) done 2007/12/1909/16/2007 07:13:12 EDTNo*ERudolf, MarianF DisapproveGProducer^ Editorial_35`16a6.2.5cfFigure 12 should be moved to section 6.2.1 because it shows the overall flow of events when using MIH.d484g5118jMove figure 12 to 6.2.1.pfFig 12 is meant to show the registration flow. Some enhancement is made to fig 12 to make this clearer{e) editor disagrees 2007/12/1909/16/2007 07:13:12 EDTNo+ERudolf, MarianF DisapproveGProducer^ Editorial_33`32a6.2.132a6.2.132a6.2.1to 6.2.1. 2007/11/1409/16/2007 07:13:12 EDTNo+ERudolf, MarianF DisapproveGProducer8cthereisnowayforthiseventtoindicatethatitwasgener\Vthereisonlyoneformatprovidedinannexd5Vthereisonlyoneprimitivelistedintable11howeverthetVthereneedstoclarifyhow'swirelesslinkconditionschange%Vthereseemstobearbitrarydecisionsmaderegardingthemih'Vthereseemstobelimitedusefulnessofthelinktransmissio(VthereshouldbeawaytoindicatethatthenetworkitselfisVthere'sWWWWthere'saperiodmissingattheendofforvariousparameterVthere'saperiodmissingattheendoflayer3handoverVthere'saperiodmissingattheendofonthespecifiedlinkVthere'sanextraperiodatthebeginningoftherearetwokiVnitiateahandoverprocesvVtheseparametersarenotavailablefornetworkinitiatedhanqVthesholdWtheyWWW<WJWeWkWlWmWqWWWWWWWW/WMWWW'creplacementxWyWreport[WaWeWWWWWaWWreported WWWWWreportingW[WWWreports[Wrepresentation4W6WrepresentativeWWrepresentedWW6WNWrepresenting=WreqWQWW2WWWrequestWWWWW WW WDWEW[W]WfWgWiWqWtW~WWWWWWWWWBWIWJW[W_W`WbWeWfWWWWWrequest-responseWrequest/indicationWrequest/responseWfWrequestedgWWWJWrequestingWW WWWrequestorWrequestsWWrequireWWWWWWW2WJWWrequirementWrequirementsWWWWW&W.WgWWrequiresWrequriedWreservationWW W*WWWS  cAThe stated scope and purpose of 802.21 is to define extensible media access independent mechanisms to facilitate handovers between and among IEEE 802 systems as well as certain external systems. This document only partially addresses that stated purpose. For example, the informative Annex L specifically identifies the need for certain amendments to several IEEE 802 technologies. These recommended amendments are identified by contribution numbers and, as such, may not be readily available tBo the Standards user, nor is there any indication that these proposed amendments have actually been adopted by the specific technology, therefore calling into question both the viability of and the ability to implement the proposed 802.21 standard.d62g5540jvrepresentW FF DisapproveGProducer^ Technical_52`48a6.5.5.2cVThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the 802.11u HESSID.d83g5519jAdd this capability. 2007/11/1209/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2approveGProducer^ Technical_52`48a6.5.5.2cVThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the 802.11u HESSID.d83g5519jAdd this capability. 2007/11/1209/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2ORK should contain the means to discover the 802.11u HESSID.d83g5519jAdd this capability. 2007/11/1209/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2YesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2proveGProducer^ Technical_52`48a6.5.5.2lIP{l) none needed 2007/12/1909/03/2007 16:49:33 EDTYes s OwP QRjS TUyVWvXYZ[a\x]k^b_`iabmcd efghijklmgno efghijklmgnoesandrewf@ƒheubaumkarlf@„ disapprove„1„P disapprove @l @rx cBEMS (Element Management System), where the latter may reside on the NE. (http://authors.phptr.com/morris/glossary.html) According to the above text, NMS is used for network management and seems to be a stand-alone system. It means that having MIH_NMS_SAP for the interface with the NMS in Figure 4 - general MIHF reference model and SAPs doesn't seem to be appropriate. Furthermore, the primitives for NMS are rather to be system functions and implementation specific. d639g4963jaDelete MIH_NMS_SAP and Network Management System in Figure 4 and apply it to all related sectionswAgree{k) done 2007/12/1909/16/2007 23:46:35 EDTYesE Kim, EunahF DisapproveGGeneral Interest^ Technical_23`3cing MIH_NMS_SAP for the interface with the NMS in Figure 4 - general MIHF reference model and SAPs doesn't seem to be appropriate. Furthermore, the primitives for NMS are rather to be system functions and implementation specific. d639g4963=AjspecificationW'W5WWWWW=WWWWspecificationsW4W8WWWspecifiedWW`WcWtWWWWW8WWspecifiesWKWLWMWNW}WspecifyW<W>W]WxWyWWWWWWWpWspecifyinformationelementpVspecifytheminimuminformationthatneedstobeincludedfoVspell7WGWHWspelloutmnandpoainthedefinition3.7HVspelloutpoaGVsquareNWstackWWWWWW!W"WWWWWstadnardEWstandardWW)WWWWWWW W WW=WW WstandardsWWWWWWstanndard?WstartWWtartsWstateWW W WWW7WvWWWWWWWWMWWWWWubscriptionWsubsequentbWs ycmihmihconfigurelinkcommandisnotdefinedthereamihlinkcVmihdeploymentmodelwhichspecifiesthelocationofmihfpoVmiheventsubscribeandunsubscribearelistedpartofserviVmiheventsubscriptionasdefinedhaslimitedcapabilityforVmiheventsubscriptionshouldallowthesubscribertosetceVVVmiheventscommandsandinformationservicemessageexchangeVmihgetinformationresponsechangethetableentryfrominfVmihhandoverprimitivesprovidelimitedhandoverfunctionaliVmihhandoverprotocolbehaviorismissingfromthesection8Visafixedlength8bytesHVmihisabouthandoverbetweendifferentaccesstechnologiesVmihisnottheonlywaythroughwhichthehigherlayersandVmihn2nhocommitcurrentlydoesnotallowtheoptionofreqVmihn2nhocommitdoesnotallowtheoptionofrequestingreVmihn2nhocommitshouldalsoallowtheoptionofrequesting V cA6MIH_NET_SAP defines the interface between an MIHF implementation and various local transport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. In the contrary, it would impose needless constraints to the implementation.6d105g5497j3remove all definition and mentioning of MIH_NET_SAPwDisagree{l) none needed 2007/12/1909/12/2007 02:37:36 EDTYes Yes ederperetzJKL disapproveN0QeO$ O disapprovePNePfederperetzLO disapproveQ disapproveRN0RfederperetzMQ disapproveS#T$T disapproveUS#UfederperetzNT disapproveV disapproveWYWchengyuuhengOV disapproveX disapproveY$YchengyuuhengPX disapproveZA[!0[ disapprove\ZA\chengyuuhengQ[ disapprove !v]This is just an example. Change text: "As an example for IEEE 802.11 this refers to the SSID"w Principle{k) done 2007/12/1909/10/2007 07:08:58 EDTYesse. that this IE shall contain the SSID for an 802.11 network. Nevertheless, it is a good idea to have such information somewhere but a normative annex (one for each considered technology) which contains such mandatroy values would be better. Having this, the main chapters of the standard are kept technology-independent and the reader has a single point where technology specific valBues for certain parameter or IEs are assumed. Besides, if a (new) technology supports 802.21 in the future by adding new service primitives / functionality, there is only a single place in the 802.21 standard which need to be revised.d50g5552j5Delete ref to 802.11 and create an annex as suggested2j5Delete ref to 802.11 and create an annex as suggested\ÃT`[ÃTpZ9 2007/09/1709/04/2007 16:19:39 EDTEMeylemans, MarcFApproveGProducer^ Editorial_32`33a5.7.2c*There is a period in front of the sentenced370g5232jRemove period (.)pSame as Cmt 44{k) done 2007/12/1909/16/2007 02:47:09 EDTNoo sentenced370g5232jRemove period (.)pSame as Cmt 44{k) done 2007/12/0209/16/2007 02:47:09 EDTMarkedNoÃv dDTÃiÃiÃiÃjÃj Ãj0Ãj@ÃjPÃj`ÃjpÃjÃjÃjÃqÃq Ãq0Ãq@ÃqPÃq`ÃqpÃqÃqÃqÃrÃr Ãr0Ãr@ÃrPÃr`ÃrpÃrÃrÃrÃsÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0Ãt@ÃtPÃt`ÃtpÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃuÃuÃvNcdiverseWdividedWdividingWdoWWWWW?WeWnWoWWWWWEWWWWWWWWWWWWdocuementsWdocumentW&WWWWWWWOWQWiWjWkWzWWWWWdocument'sWdocumentationWdocumentsEWdoesWWWWWWWWWWWW WWWWWW0W1W7W?WDWEW[WnWoWpWtWwWWWWWWWWWWWWWWWWWWWWWW*W2WIWRWTWVW[WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W,W0W7WeWrWsWwWdomain W2zvto{W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W Wtomakethismappingnormativethe802.11specalsoneedstoVtoolsWWtopWWWWtowardsWtrafficWtragetlinkactionsWWtransactionWWtransactionidisnotsufficientformatchingarequestareVtransaction-id'W W WtransferWtransmittedW2WtransparentWtransportWW2W<WWWtriggeredtrueW]W W WWWtrying(WttheWtupleWWWtwoWW'WW WtypeWWWWW WW/W0W3WWW^WaWpWWtypeieroamingpartnerstypeieroamingpartnerWVtypesWue2Wul/Wumts/W2WZoE Xie, QiaobingF DisapproveGUser^ Editorial_51`25a6.5.4cThe sentence is ambiguous.d349g5253ve„T disapproveU2„UstephensadrianpT disapprove„V disapproveW+3„WstephensadrianpV disapprove„X disapproveYP&„Ystephensadrianp X disapprove„Z disapprove[:„[stephensadrianp Z disapprove„\ disapprove]%„]stephensadrianp \ disapprove„^_aF„_ disapprove`^„`jeffreetony_ disapprove„a disapproveb^„bjeffreetonya disapprove3j802.11u W8WW802.15WWW W(W802.16-20004/d/e8W802.21WW WW&W'W6W7W8W802.21needstoclearlystateworkingassumptionsregarding V802.37W802.3&3gpp2W9=WaWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW"W#W%W&W'W)W+W,W2W5W6W7W8W=W@WBWGWIW^W_W`WeWhWiWkWlWmWtWwWxWyWWWWWWaone-octetselectorfieldfollowedbyavariablelengthvalVa-1=Waaa7Wabout W6WWaboveWW&W]WacceptancevWaccessWWW WW&W'W0W1W7WbWkWlWmWWaccess-specificWaccordingWaccounteWaccuraciesWackWjagreedWair7W8WWalgorithmWWalignWWaligndefinitionordonotre-defineitinthisparagraphValigntextwithtypeorchangetypetoalignwithdescriptioValikeWallWWWWWWWWWWW WW3WIWkWlWmWWWWWWWW W#W$WWWWWWWWWWallocated WallowW W<W=WWWWallowthediscussionofapplicabilityofmihonlyinthesec<VallowableWallowances*WallowedWWallowsWalongWJWgWalready-W7WFWalsoWWW7WRWwWxWyWWWWW3W8WWalternative'WWalternativelyW'WDWEWJWeWgWWalwaysWJWWWJWamandmentWamendment,W8WamendmentsWamongIWW|OjQChange MIH_Information.request/response with MIH_Get_Information.request/responsep[all the occurrencies of MIH_Information was changed as MIH_Get_Information in this section.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes PE Cypher, DavidF DisapproveGGeneral Interest^General_296`4cIEEE Style is not appliedd190g5412j"Change "This table" to "Table L-4"wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes QE Cypher, DavidF DisapproveGGeneral Interest^General_284`1cDAnnex needs to be update for consistency to the rest of the documentd189g5413j9g5413j9g5413j.wAgree 2007/11/3009/13/2007 13:56:26 EDTMarkedYesconsistently 2007/10/0709/13/2007 13:56:26 EDTYes0/0709/13/2007 13:56:26 EDTYes link between 9) and 10) 2007/10/0709/13/2007 13:56:26 EDTYesiE Cypher, DavidF Disapprove7 2007/09/1709/13/2007 13:56:26 EDT W>E&jpossiblyWWWWTable 10 2007/09/17l_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g3769jlRemove the stack marked as "Remote Entity". Remove text "Local Entity" from the stack on the left-hand side. 2007/09/1709/16/2007 15:23:06 EDTYesENatarajan, Kadathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g3769arked as "Remote Entity". Remove text "Local Entity" from the stack on the left-hand side. 2007/09/1709/16/2007 15:23:06 EDTYesENatarajan, Kadathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g3769adathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g3769 2007/09/1709/16/2007 15:23:06 EDTYesC McB invoking them from any other layar violates the 802.11 architecture. When the 802.21 plays in the context of the 802.11 SME, then it becomes reasonable for the 802.11 WG to architecturally define 802.11 specific interfaces for 802.21.d273g5329jCorrect the 802.21 architecture. The 802.21 entity must reside inside the 802.11 SME. This way, 802.21 can define mechanisms that can use 802.11 SME components. Likewise, same for 802.16 SME.v&Please refer to TGu draft contributionw Superceded{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYessiagram and description to include the 802.11 Authenticator in consideration. The MIH_NET_SAP should go this interface.vbThis can be taken care of by 802.11 (TGu) people as part of updating the 802.11 reference diagram.wAgree 2007/11/1809/14/2007 16:50:16 EDTMarkedYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_26`26a5.5.3ce@ƒbajkogaboreSjremovereferencetovariableoctetsfromthefigureHVremoveremoteentitystackandremovetextlocalentityfromVVremovesection7.4.18andalsorelatedsectiondatatypemihRVremovetableb-10VremovetagandthecontentsSVremovethechangebars!VremovetheieoraddthedefinitionVremovethesentenceVremovethestackmarkedasremoteentityandremovetextlocVVVVremovethestackmarkedasremoteentityandremovethetext!V"VremovethestackmarkedasremoteentityremovetextlocaleVVremovethetextaboutthearqmobileintroduceamechanismw Vremovethewholesection7.3.10VremovethisprimitiveorclarifyitspurposelinkhandoveriVremovethissectionseepage178lines23-43fordiscussionhVremovedWgWremovingWrenameWrenamer1r5asj1j5throughoutthedocumentVreorderWW<WrephraseWWWW:joutline'Woutside?WoverW(W7WcWWoverall%W&WownW7WWp207Wp208WpacketWBWFWQWjWkWrWpageWWW+W=W[W\WgWhWWWW0WQWiWjWkWpage214line2changecospackettransferdelayjittertockVpage224line35missinglistinsupportedlcpmissingmobiljVpage226line60missinglistinsupportedlcpmissingmobiliVpage285line27changemihconfigurelinetomihlinkconfiQVpairIWWpaper)WparWparagraphWWWW4WWWWWW/14/2007 14:42:22 EDTYesE Jette, AlanF DisapproveGProducer^ Technicalmand are not defined.d260g4693j)remove MIH_Net_HO_Candidate_Query command 2007/09/1709/14/2007 14:42:22 EDTYesE Jette, AlanF DisapproveGProducer^ Technicald259g4694 2007/09/1709/14/2007 14:42:22 EDT<W=W>W/2jlayerWWWWW?WwWWWWWWlayer2macand/orllcVlayersWW;WWWWWlcpVWiWjWleadingWleast'W5W6W7WWWleave5WWleft]WwWW'Wleft-handWWWW!W"WWWWWlengthWWW=WWWWWWlevelsWliesWlifetimeWlikeW WWW%W&W'W.W1W7WWWlikewiseW|WWstatesWWWWW5WDWTWUWWWYWkWWWWW&W'W)W*W8W:WKWLWMWstatesthatanmihusermustgeneratearesponsetotheindiVstatesthatitmayindicatethatthemnmayhavestartedahVstatesthatitpreparesresourceforhandoverthisisjustaVVstatic4Wstating߶WIWstation8WstationaryW8PJE Kim, YonghoF DisapproveGProducer^ Technical_47`2a6.5.2chBetter wording is recommened for "A similar mechanism may be available for IEEE 802.16 for this query.'"d334g5268jiChange into " IEEE 802.16 also allows an MN to query using PKM management message before authentication."wAgree{k) done 2007/12/19t.d335g5267j/Clarify mapping transport address with MIHF ID.v The MIHF does know the transport address. How the transport address is determined is outside the scope of this draft. The network MIHF entity may have FQDN as it's identifier The MN may not have a FQDN.w Principle 2007/12/0109/15/2007 00:01:16 EDTMarkedYesE Kim, YonghoF DisapproveGProducer^ Technical_47`2a6.5.2chBetter wording is recommened for "A similar mechanism may be available for IEEE 802.16 for this query.'"d334g5268jiChange into " IEEE 802.16 also allows an MN to query using PKM management message before authentication."wAgree{k) done 2007/12/01M cto%W'W*W+W,W-W.W0W1W2W4W5W6W7W<W=W>W?W@WAWBWDWEWFWJWKWLWMWNW[W\W]W^WaWbWeWfWgWiWjWkWlWmWpWtWuWvWwWxWyW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWW#W$W%W&W'W(W)W4W7W8W@WBWEWGWHWMWNWOWQWUWWWZW\W^W_W`WcWiWjWkWmWyWzW{W}WWWWWWWWf_Ã7 bcÃ7@aÃ7p`Ã7^_Ã7]Ã8\Ã80[Ã8@ZÃ8pYÃ9VWXÃ9 TUÃ90.⪃RS㖃Ã9PᕃᗃᘃᙃQÃ9p5Ã9ᔃÃ9Ã9ᒃÃ:Ã:0ሃ,-EÃ:@Ã:pPÃ:YZOÃAPÃB`NÃBp⩃ÃF_164`14a8.6.3.12e to state the security considerations for the IEEE 802.21 protocol. 2007/09/1709/14/2007 23:15:41 EDTYesZE Julka, VibhorF DisapproveGProducer^General_175`19cThis section is a duplicate of the information that is given in 6.5.5. Suggest we delete text on lines 19 through 47 in section B.1.2d299g4654j+Delete text on lines 19-47 in section B.1.2 2007/09/1709/14/2007 18:36:55 EDTNo[E Julka, VibhorF DisapproveGProducer^General_164`14a8.6.3.12roducer^General_164`14a8.6.3.12d298g4655 2007/09/1709/14/2007 18:36:55 EDT*WmihfsthepropagationfVsc12W*WW120W124W127W13WWWW"WWW14W1526W16WWW!WWW17/WW173wWyW176W18WW180W186FW19WWW196pW19thNW2WWWW W5W=WFWWW WW'WWWWWWWWWWWW2sentencesline41and52saythesamethingV2-3'W2.11W2.4-ghzW2.5-ghzW2007WW/WW200mNW202W21WWWW07-0315-00-0000-dW21-07-0316-00-0000-mW21-07-0317-00-0000-sW21-24bW22W228UW23W230eWwW231wW24W25W25.133W252wW26WFW27WWWWuWWW28-31eW2ndW2sW3WWW4W5W=WWWtWWWW3.3WW{rEMyles, Andrew FF DisapproveGProducer^ Technical_72`59a7.3.11.1cAThe purpose of this primitive is unclear. The text indicates this event is generated when a "native link layer or switch decision has been made and its execution is imminent". This does not make sense to me. If the mobile node's L2 mobility manager can make this decision to go to a new PoA, why must MIH be informed? This is **not** needed for intra-technology handover (as is stated on p73L1-4) since the L2 mobility manager would not handover between networks, only within its current networB@k (otherwise it would risk losing the L3 connection altogether)..d96g5506med? This is **not** needed for intra-technology handover (as is stated on p73L1-4) since the L2 mobility manager would not handover between networks, only within its current networB@k (otherwise it would risk losing the L3 connection altogether)..d96g5506itly for that link typed527g5075l Interest^ Technical_33a6 Y{neededWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWW W!W"W#W$W&W(W)W*W+W,W5W8WmWpWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWnextWWW/WnoneWWWWWWWWWWWWWWWWWWWWWWWWW!W"W#W$W)W*W+W,W5WAWWWWWWWW07&|julkavibhorVVVVVVVVVVVVVVVVVVVVjunghoonWWWWW%WWWWWWWWkapilWWWWWWWWWWWWWkarockiWWkarockipiotrVVkevinWkimWWWWWWWWWWWWWkimeunahVVVVkimyonghoVVVVVVVVVkwakWWWWWWWWWWkwakjosephaVVVVVVVVVVlach<W=W>W?W@WAWBWlachhong-yon<V=V>V?V@VAVBVleeuwenWWlevyWWWWlevyjosephsVVVVmWWmarcWWWWWWWWWWWWWWWWacmisleadingW@Wmisleading--theWmissesWmissingWW&W+W-WYWfWWWWWWWWW1WgWmWyWWWWWWWWWmissingaparenthesisforthetypeofpacketidentifier1Vmissingbracketinunsignedint2VmissingcommaVmissingcommaafterlastwordinlineVmissingdefinitionmustbefilledVmisusedWmixesWmlmeWWWWWWmlmesapc-sapmih3glinksaplsapcssaparenotshowninfVmlme-sapWmnWWWWWWW&W0WJWKWLWMWNWdWeWiWuWvWwW}W~WWWWWWWWWWWWW@WUWYW[WbWeWfWWWWWWmn'sWmnsWWWWWWWWW&W'W5W7WkWlWmWtWvWW17jKIf Annex C is normative, make it a clause in the body of the specification.pgroup disagreedwDisagree{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_151`21a8.4.1.1cThe figure description does not line up with the octect header. For example, the first octet has only 7 bits defined with no reserve bit.d319g5283j0Add a reserve bit at the endo fo the first octetpgroup disagreedwDisagree{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_144`45a8.2.2czThe state machines account for sending and receiving messages. However, they do not account for registration or discovery.d318g5284jFrom clause 5, there was a registration and discovery process for initiating an MIH connection. Include these processes as part of the state machine definition.efinition.efinition.320g5282TYeszcitWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W$W*W0W1W7W<W=W?W@WFWRW[W\W]WcWeWfWgWhWnWoWrWsWtWwW|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W$W&W(W0WBWIWJWYWmWpWqWwWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWW0W1WcWeWrWsWwWjustprovidingmacaddressesofpoaisinsufficientfornetwVVWb*cbIEEE Style is not applied to the this clause as per IEEE Standards Style Manual 2007, 10.6 page 17d128g5474j@Format according to IEEE Standards Style Manual (use lower case)wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s 11/2609/13/2007 13:56:26 EDTMarkedYes, IEs, and clauses.d129g5473j]If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses. 2007/11/0609/13/2007 13:56:26 EDTMarkedYesE Cypher, DavidF DisapproveGGeneral Interest^General_10`6a4th in all relevant, tables, TLVs, IEs, and clauses.d129g5473j]If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses. 2007/11/0609/13/2007 13:56:26 EDTMarkedYesE Cypher, DavidF DisapproveGGeneral Interest^General_10`6a4avidF DisapproveGGeneral Interest^General_10`6a4d133g5469 2007/09/17nical_465]cieee802.11unowsupportsanativegasgenericadvertismentVieeestyleisnotappliedPVieeestyleisnotappliedtothethisclauseasperieeestaVWWWWWWWWWWWWWW W WW'W.W1W]WfWgWnWoWrWsWtWuWvWWWWWWWWWWWWWWWWW@WIWNWmWWWWWifatleastonequeryisrequiredthereshouldbesomeminimVifmlme-sapmessagesarepermittedinstate1theywouldalsViftheintentisfortwomihfstomutuallydiscovereachothfVifthemihgetinformationprimitivemustcontainatleastoVifthereisnoreferencespleasechangeclausetexttothereVimminentWW_WwWimplementWimplementationWWWWWWW W W#W$WWimplementsWimplicitWjreplacemaynotwithneednotorwordingwithsimilarintentVreplacereferencebytablek-2VreplacesentenceiflinkdownisnotwithiflinkdownorliVreplacetextonlines11-12withthismessageisusedbymihVreplacetextonlines14-15withthismessageisusedbymihVreplacetextonlines41-43withthismessageisusedbyamVreplacetextonlines50through55withthesourcemihfmayVreplacetextonlines55-56withthismessageisusedbyanVreplacethecolumnthatprovidesthemappingbetween802.21Vreplacetheexistingserviceprimitivesasdefinedin3gpp/3VreplacethefollowingsetofserviceprimiteswiththesetoVreplacethesentencestartingonline43bycommunicationbeVVV>WAWreportWQWaWreportedWreportingWreportsWWWWrepresentationWrepresentedWWreqWceWWWWWWWXvjchangedescriptiontoabitmapnwherenmustbeamultipleVchangeeithertochangingalinkimpliesortochanginglinkVchangeentitymihbasicurltobeassignedVchangefig9and10Vchangefigure26toshowmihprotocolheaderhasfixedlengtVchangefortransportservicesoverl2theprimitivesarespecVchangefrommacadresstolinkidVchangeguildtoguide{Vchangeintoieee802.16alsoallowsanmntoqueryusingpkmVchangeitPVQVchangeittostatus9Vchangelinkidtolinktupleidspecificallyforlinkaction7VchangelinksacntolinkscanVchangemaytoshalliealwaysgeneratesanindicationwhenVVchangemihinformationrequest/responsewithmihgetinformaOVchangemihnethocommitrequesttomihnethocommitrequesVchangemihftomihuserVWWWWWWWWWWWWWWW WWW)W-WclayersWWWWWWWWWBWeWWWWWWWWlayoutWlcpWVWyWleadsWleastW W'W5W7WKWLWMWNWWWWWWW WWleftW!W WWlegacyWlengthWWW=WHWWW6WWWless<WgWletWlet'sWlevelW WWWWWlevelsWliasonWlikeWWW0WWWWWWWWlikelyW WWlikewiseWlimitW WlimitedWWWWW'W>WAW(WlimitingWW@WWWlineWWWFWeWjWWWWWWWRWxWWWWline1WlinesWWWbWeWvWW WgWGWJWKWLWMWNWPWQWRW[W^WaWbWcWeWcsapsWW&WWWWWsaveWsayWWW7WWWWsayingWWsaysWscaleWscanWWRWWWWWscanningWscenarioW&Wscenarios&WschemaWSWW.WschemeWscope6W7W<W?WWWWWWWWWWWWscratchWsdo'WWWsdo'sWsduBW 2007/09/1709/10/2007 07:08:58 EDTYesMEEmmelmann, MarcF DisapproveGAcademic^ Technical_145`34 machine. 2007/09/1709/10/2007 07:08:58 EDTYesLEEmmelmann, MarcF DisapproveGAcademic^ Technical_146`54a8.2.2.2c[Text states that max. 2 retransmissions are allowed but the state machine does reflect thisd57g4896jAdjust state machine. 2007/09/1709/10/2007 07:08:58 EDTYesMEEmmelmann, MarcF DisapproveGAcademic^ Technical_145`34g4897 2007/09/1709/10/2007 07:08:58 EDTd&ENatarajan, Kadathur SF DisapproveGProducer^ Technical_106a7.4.19cMThe purpose and usefulness of MIH_Net_HO_Candidate_Query command are unclear.d537g5065jQRemove all definitions and avoid mentioning of MIH_Net_HO_Candidate_Query commandvAThe name of these Net_HO commands need to change. " The Network controller provides a list of candiddate network choices to MN. The MN indicates resources required on each of these candiddate networks. The Network controller then queries each of the candiddate networks for available resources and reports this information back to the MN. Thereafter the Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagreee Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagree#-NjplacewWgWplaceblocksincorrectdrawingsoftwareordersothatthelgVplacementWplacesW0WplaneW(WplayWpleaseWWWWWWWWWWWW2WWWWWWW6Wpleaseaddthefollowingsectionas8.3VasedontVpleasedefinesomewheretheactionsthatanmihprotocolentVpleasesee309VVpleaseseethecontribution305Vpleaseseethecontribution306change1Vpleaseseethecontribution306change2Vpleaseseethecontribution307Vpleaseseethecontribution308VVpleasestateclearlyifmihsignallingexchangesusingdataVplugfestWpoaWWbWkWlWmW|WWWWWpoasbWpoorWportionsWposWWWpositiveWpossibilityW]WfWWpossibleWWBWWWWpossibly.WWW|:levyWWWWlevyjosephsVVVVmWWmarcWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW, MarcFApproveGProducer^ Editorial_105`17a 7.4.19.1.1cThe 'Requested Resource Set' parameter should be Optional because the 'Query Resource Report Flag' in the request or indication can be True or Falsed378g4575j\Make 'Requested Resource Set' parameter optional in both the response and confirm primitives 2007/09/1709/16/2007 02:47:09 EDTNo EMeylemans, MarcFApproveGProducer^ Editorial_105`17a 7.4.19.1.1er^ Editorial_105`17a 7.4.19.1.1d377g4576 2007/09/1709/16/2007 02:47:09 EDTtanswerstothosequ.Vtrationbyc-nem-rspderegistrationVwuYcmac-hs Wmac-wlanZW\WmachineWWWWWmachinesWWMWmacroWmadeWW=WWW'WWmagic WmainWWWWmajorWmakeWWWWW&W5WuWWWWWWWW WWmakerWityWincludesWWWWW)VeVthedefaultmimetypevalueisincorrect(V)V)VeVthedefaultmimetypevalueisincorrect(V)V)VeVthedefaultmimetypevalueisincorrect(V)V)Votherhthedefaultmimetypevalueisincorrect(V)V)V)ViVthedefaultmimetypevalueisincorrect(V)V)VViVthedefaultmimetypevalueisincorrect(V)V)VnctionthatcouldbVtheimplementordoesn'tcarewhatmayormaynothavebeenpVtheinfofrommnisinformativeandsoitdoesnotcontaintܶV2JE Cypher, DavidF DisapproveGGeneral Interest^ Technical_160`49a8632cA%Consistency: The MIH_Get_link_Parameters response message contains the Device States Response List, while the MIH_Get_link_Parameters request message has the DeviceStatesRequest marked as optional. Why is it is required in the response message when it was not requested in the request message?%d196g5406move parameter from primitives.vLAdd CandidateLinkList in the request message in section 8.6.3.13 on page 165wAgree 2007/12/0109/13/2007 13:56:26 EDTMarkedYesJE Cypher, DavidF DisapproveGGeneral Interest^ Technical_160`49a8632cA%Consistency: The MIH_Get_link_Parameters response message contains the Device States Response List, while the MIH_Get_link_Parameters request message has the DeviceStatesRequest marked as optional. Why is it is required in the response message when it was not requested in the request message?%d196g5406nciple 2007/11/18YcfromWWWWWWWWWWWW W WWWW.WFWWWWWWWWWWWW/WNWZW\W_W`WWWWWWWWWfromline1to13thecontextdoesnotreallyrelatetocommaVfrom/toWfroms5Wfront WWfunctionWWWWWWWWWWfunctionalWfunctionalityWW]WWW*WWWWfunctionsWWWWWW&WWWWfundamentallyWfurther?WfurthermoreWWfutureWWWWgWWW%W[W]WgWuWWWW(W/W3WWWWWWWWWWWyWWWgenerateIWtWWWgenerated WW[W\WaW~WWWWWWgenerates]W Wx^citappearsthatcosvaluesfromthelinkparamtypeofgenerFVitappearsthatipaddressinformationstatusisunnecessarynVoVitisbettertoincludealistoflinkidentifiersinmihreBVitisentirelyunclearwhatitmeanstoclaimconformancetoVitisimportanttonotethatwithcertainaccessnetworksanVsverydifficulttocross-referencethesectionswheretVitisverydifficulttorelatetheprimitivestotheprotocoVitmaysoundtrivialbutinitializeuponreceiptofthemihVitsays802.21allowsanmntodiscoverheterogeneousnetworVitshouldbemadeclearthatinthecasethattheoperationVitemsWWiteselfWitsWWWWWW WWWitselfWjWW.WWj1Wj5WjobWjustWWWWW0W1WcWeWrWsWwWWjustprovidingmacaddressesofpoaisinsufficientfornetwVVfcgasWgatewayWgatheringWgenaratedWgeneralWW%WFWWWWWgenerallyWWWgenerateIWtWWWgenerated WW[W\WaW~WWWWWWgenerates]Wa unified interface to the MIH Users." Replace "The service primitives exposed by this unified interface. . ." to "The service primitives defined at this interface. . ."| 2007/09/1709/16/2007 06:10:15 EDTYes߸ELach, Hong-YonF DisapproveGProducer^ Technical_8`44cSub-clause 3.44: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d461g4492veGProducer^ Technical_8`44cSub-clause 3.44: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d461g4492 2007/09/1709/16/2007 06:10:15 EDTYeshjAdd a cross-reference for primitives defined in clause 7 indicating which protocol message they refer to. Alternatively add a cross reference in clause 8.6 to sections in clause 7 that define primitives relating to that protocol message.p%- added x-ref to all messages in 8.6 {k) done 2007/12/1909/14/2007 23:15:41 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_170`1a8.6.4.1ceA request-response mechanism will not scale to accommodate large numbers of MIH-capable mobile nodes.d324g5278jProvide the capability for the MIH-capable mobile node to broadcast information to devices at a PoA in addition to the request/response mechanism.vSection 7.4.27: "It is assumed that the available information could be broadcast in access technology specific manner such as in 802.11 and 802.16."w Principle{k) done 2007/12/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical3>EEmmelmann, MarcF DisapproveGAcademic^ Editorial_17`32a5.3.4c&incoherent usage of singular or plurald36g5566jBeither: "A user and network policy" or "user and network POLICIES"{k) done 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_13`1a5.1.4cAYSection 1.3 states that HO policies are not within the scope of 802.21. Given so, why have MIH services to consider network traffic performance and how well they meet the application's need. This evaluation is part of the "handover decision making entity" and the MIH services to do, as far as I understand, only provide input to such an entity.Yd35g5567jClarify or rephrase paragraph paragraphion's need. This evaluation is part of the "handover decision making entity" and the MIH services to do, as far as I understand, only provide input to such an entity.Yd35g5567jClarify or rephrase paragraphDisapproveGAcademic^ Technical_21`2 jtheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWWWW!W"W%W'W(W-W.W/W2W3W4W5W8W:W;W<W=W@WAWEWHWJWMWNWZW\W_W`WdWgWqWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWDTNoERudolf, MarianF Disapprove0 2007/09/1709/16/2007 13:36:45 EDT\ctypicallyWtypoWWtypoinlinksacnVtypointhealgorithmdefined&maybeusedtoguildthecalcuVuaWucdWueWuir@Wuirbitusageisnotclearwhichentityissupposedtosett@VumtsWW/W2W3W;Wumtslayerisambiguous;Vuna^WcWunable^Wunacknowledged WunambiguousWunclearWWW4WfW}WWW W$WWWWWWWWWunclearwhatoldlinkactionsisreferringtothemnornetw}VundefindeWunderWWWWunderlying W@WWWW2jretransmittedWretransmittedmihresponseisreceivedduetoalostmihackVreturn^WkWlWmWJWreverseWrevisionXWrewordWWrewordsection5.1.8VrewordthegoalaccordinglytomentionthisasadesirablegVrewriteWWrewritethisclauseandotherportionsofclause5toprecisVrewritingWrfWrfcs.W9WridWright4Wrlc;WWWWWWWWWW-W.W7Wsection2 W9WsectionsWW7Wsecure7WsecurityW7WseeWWWWWWWWWW%WseecommentforproposedresolutionVselectedWselectionWWselectorWselfWsendWsendingWsense0Wsent7Wsent/receivedWsentenceWserver'sWWserviceWWservicesWWW&Wsession&WsetW'Wsets&WsetupWWacmihftransactionacombinationofanmihfrequestorindicatVmihfsWfWAWaWWmiisWWWWWWWWWmikWmillisecondsWmimeW:W;W<Wmimo/ofdm/WminbWeWfWmincardinalityTWmindWminimalWminimise=WminimizesWminimum&W7WWmipshop.WmiscWmisccommentsinusrfileVnnexbthisannexdefinesdatVVhefollowingsentenceinannexbthisannexdefinesdatVVnceinannexbthisannexdefinesdatVVinannexbthisannexdefinesdatVVnesdatVVnb-9<VaddedvWaddingWadditionAWadditional6W7W9WWadditionally`Waddress<W߄WWWWWW6WaddressedvWadjustmentߴWadjustmentsߴWadmission Wadopt2W3Wadress;WadvertiseGWafterߏWW+W_WWbWwWWENatarajan, Kadathur SF DisapproveGProducer^ Technical_31cA6MIH_NET_SAP defines the interface between an MIHF implementation and various local transport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. To the contrary, it would impose needless constraints to the implementation.6d533g5069implementation.[d534g5068j3remove all definition and mentioning of MIH_NMS_SAPwAgreey Ref Cmt 106 2007/11/1809/16/2007 15:23:06 EDTMarkedYesENatarajan, Kadathur SF DisapproveGProducer^ Technical_31cA6MIH_NET_SAP defines the interface between an MIHF implementation and various local transport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. To the contrary, it would impose needless constraints to the implementation.6d533g5069ormativVDcwouldbenicetohavethemiheventsintable4orderedaccoVwouldn'tWWwouldn'titbeusefultoreferencepreviouslydefineddefiniVwpaWwrapWwrongW/W2W:WWW WwwanWxNWxmlW<WxmldoesnotcompileVxvWxxx WWxxxxWxyzWyankedWyes1WWyetWWWfWW WWyet-to-be-definedWyieldWyouWWWWWWzeroWtions or qualifiers. With that only events meeting those conditions or qualifiers will be notified to the subscriber.d538g4415Kadathur SF DisapproveGProducer^GeneralcMIH event subscription should allow the subscriber to set certain conditions or qualifiers. With that only events meeting those conditions or qualifiers will be notified to the subscriber.d538g4415 2007/09/1709/16/2007 15:23:06 EDTYesܠWWWWWWWWWWM IpAChange "This notification is delivered when a layer 2 connection is broken on the specified link and no more packets may be sent on the specified link" to "This notification is delivered when a layer 2 connection is no longer available for sending frames, that is, when the L2 connection with network is terminated and not during PoA to PoA transistions for the same network." No change made for 7.3.5.3 Delete "normally" in the first sentence of 7.3.5.4. (Note: Probably should delete the lB\ast sentence since it doesn't need to be furthur described. Link_Up ends with two sentence.)JvAdd clarifying text from TGu draft (Vivek or Qiaobing, the resolution I put it in the Editor's Note. Please verify, Updated with Vivek Dec 5 email.).w Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYes s j Please see the contribution #305pSuperceed by 615.vby 615w Superceded{l) none needed 2007/12/0209/16/2007 21:41:08 EDTYes994W{bcrecognizingWrecommendationWW&WrecommendationsWWrecommendedWrecommenedWreducesWredundantWWWWhW|WWWWreestablishmentWrefWreftotable8access-network-aux-ithetablesouldnotcontVreferWDWEWWWWWWrefertocontribution21-07-0317-00-0000-sinformationieVreferenceWWWWWWW WW-W8WdWiWWWWWWWWWW0WWWWWWW d272g4681 implementing 802.21, we cannot get any guidance on whether this goal is met. And, in extension, it is not proven if the mechanisms defined in this amendment are sufficient for interoperability. This comment Bis against the entire draft. d272g4681 2007/09/1709/14/2007 16:50:16 EDTYescmobileWWWWWWW%WNWWWWWWWWWWWWWmobility7WWxWWWWWWmodelWWWWWWWWmodellingWmodelsWWWmodificationsWmodule WmodulesWmoreWWWWWW&W=W]WgWnWoWWWWWWWWWmoreoverWW.W6WmostWW WW W WmostlyWWmoveW WWWmovereferencesbibliographytosection2normativereferenc Vmoved*WWWWmovementWmpduWmpdusWms/WmsduWmuchWWWmultipleWW[WWWWmustWWWWWWWWWW&W'W5W7WkWlWmWtWvWWWWW]jcdataWWWWWWWWWWWWW4WBWZWfWWWWWW(W2W9W=WWdatatypeforsysteminformationshouldbedefinedVdatabasesWWdatatypeWVWdatatype1Wdatatype2WdatedWday.WdbmWdcdWdecideWdecidesWdecisionWWWWWWWacethe802.3&3gpp2boxesinfigure11bytߋVߋVߋVߋVߋVߋVߋVߋVߋVߋVߋVto -25 dBm (TS 25.133 LINK_PARAM_TYPE indicates LINK_PARAM_UMTS for use, let's say with RSCP or CPICH_Ec/Io, the 802.21 THRESHOLD sets a value in the range of 0...65535. However, CPICH_RSCP in W-CDMA would be a reported and measured value in the range -120 to -25 dBm (TS 25.133d512g3792 2007/09/1709/16/2007 12:18:13 EDTo"crequiredWWWWWWWW2WJWWWrequirementWW WrequirementsWWWWW&W.WgWWWWWWrequiresWrequriedWreservationWW W*WWWas ruled that state diagrams are normative, which means that the state diagram must be correct.)d569g4384j6Update the state diagram to match the text description 2007/09/1709/16/2007 15:56:25 EDTYesMEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145en only twice. Note that the IEEE SA has ruled that state diagrams are normative, which means that the state diagram must be correct.)d569g4384j6Update the state diagram to match the text description 2007/09/1709/16/2007 15:56:25 EDTYesMEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145oveGGeneral Interest^ Technical_145d568g4385 2007/09/1709/16/2007 15:56:25 EDTI vcAeThese lines state that "the MN may initiate a handover process and begin setting up an L2 connection" but, wasn't that the intent of the link actions? In order to send the response we must have completed the actions (so that we can send back their status). If the actions tear down the old link and bring up another, isn't that what a handover is all about?ed408g5194jA It sounds as if the response contains the "acceptance" rather than the "execution" status of the Link Actions. If this is true (and it should explicitly state this) then there is no way for the entity that sent the Net_HO_Commit request to know if the actions were completed successfully. vThe entity can identify if the actions were completed via the the parameter "Link Action Result List." See more details at page 178.wDisagree{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNowERajkumar, AjayF GProducer^ Technical_121`8c21`8c.27.4.12.1.26 2007/09/17:5jcontrolWconventionsWW WcoreWcorrectWWWWWWWWWWW>WAWBWWWWW WWgWWWWWcorrectdefinitionbyreplacinginformationtransferwithinAVcorrectdefinitionbyreplacingspecifytheinformationtob>VcorrectdefinitionofprotocoldataunitapossibledefinitiBVcorrectfigure26showingthemihprotocolheaderhasafixeVcorrectfigure26toshowmihheaderhasfixedlengthof8oV page iii, line 35) "Michael HogHooghi" should be spelled "Michael Hoghooghi" (he's a former co-worker).d63g4890jChange to "Michael Hoghooghi". 2007/09/1709/11/2007 11:49:56 EDTNoGEKiernan, Brian GFApprove HogHooghi" should be spelled "Michael Hoghooghi" (he's a former co-worker).d63g4890jChange to "Michael Hoghooghi". 2007/09/1709/11/2007 11:49:56 EDTNoGEKiernan, Brian GFApprove891 2007/09/17j21-07-0317-00-0000-sW21-07-0317-01-0000U21-07-0373-00-0000@W21-07-303-00-00002W21-07-304-00-0000-or6W21-07/320r0W21-07/321r0W214kW2170W224jW226iW23-43hW24%W25-49W25.133W25.2152W26WWWWuWWW27WQWqWuW28uW285QW287QW288QW29WuW2g/3gW2ndW2sW3%W5W=WQWWW3-mbms/W3.23W3.7HW305WW306WWW307W308WW309WW32QW32-32\W32-33[W33+W34W35jW35-36[W36W37W3gppWW'W0W4W6W8W;WW3gpp/3gpp2W3gpp2WW:W3rd:W4WW4-55W40QW41WW41-43W42W43WjW46WQW47-48,W49WWWjW5<WWWW5.1.1WcsyntaxWsyonymousWsystemWWWWWWWUWWWW WWW#WWWWWWWsystemsWWWWsytaxWsytaxofprimitivesintextdoesn'tnotmatchsyntaxinadjoVtWWtableWWWWWWWWW3W4WWWWWW3WwWyWWWWWWWWWWWWtable10statesairinterfaceforlinkgetparametershoweveVtable14ipisnotatransportprotocolsimplystatingthatVtable5doesnotincludethemihlinkactionsasacommandtVtableb4linktypeumtsismeaninglesssupposedlyw-cdmafd3Vtableb4thresholdwhichisusedextensivelyforlinkconfiVtableb-13Vtableb-15datatypeforrdfinformationquerywrongdefaultVVWWWWWWWWWW W W WW Vu 2007/12/1909/03/2007 02:30:39 EDTNoEStephens, Adrian PF DisapproveGProducer^General_194`21cTable B-13. This table mixes chalk and cheese. WMM is not an IEEE 802.11 protocol, but a proprietary protocol of the WFA SIG which is almost the same, but not quite. Similar comments related to WPA. and CWG.d7g5595j~Replace with 802.11 terminology. (WFA should be able to communicate their compliance levels using vendor-specific signalling).vTake out WFA specified parameters/values Define another bit specifying security. Bit 12 RSN is supported. Bit 16 onwards everything is WFA specified......w Principle{k) done 2007/12/1908/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_174`22aB.1.1cian PF DisapproveGProducer^ Technical_174`22aB.1.1cn to the new conditions.apX- adopted the replacement sentence but left out the additional description text proposed{k) done 2007/11/269/17=jstatethatdiscoveryofmihposoverl3isoutofscopeofiVstated]WstatementWW&WkWlWmWWWstatementsWstates WWWWstatingJWstatisticsWstatus WW_WdWeWkWlWmWvWW2W9WstayRWSWlWWstepsWstill]WwWstring~WWstronglyWstructures/drawings WstyleWsub-clause0WsubclauseW"W#W$WWWW WsublayerWsubmittedWsubnetWsubparameter WsubscribeWWsubscriberWsubscriptionWsubsequentbWN |}~〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㐃㑃㒃㓃㔃㕃㖃㗃㘃㙃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ ied in the protocol messages.d322g4631jxIn the tables that define protocol messages. Include a reference to a clause where the data type, list, etc. is defined. 2007/09/1709/14/2007 23:15:41 EDTYesrotocol messages.d322g4631jxIn the tables that define protocol messages. Include a reference to a clause where the data type, list, etc. is defined. 2007/09/1709/14/2007 23:15:41 EDTYes jvs W4W7WwWw-cdma/W3W4W7W;WwasGWWJWwayW(WvWwWWwaysWwe]WiWwWWwellWWOW8WwerevWwestWwfaWwgWwhanWwhatWWW)WGW}WWWwhatever'WwhenWWWW WW6W7W`WbWwWxWyW}WWWWWwhenanmihnetworkentitybroadcastsunsolicitedamihcapaVwhenthetimerexpireswithoutreceivingaresponsemessageVwhereW W WW7WWWWW WwhereverWWwhetherhWwWJWwhichWWWWW2W3WWWWWWWWWWWWWWwhileWwhoWwholeWWwhyWwillWWW'WWWwindow WwiredWwirelessW)W%Wxv$change LINK_ACTIONS to "LINK_ACTION"wAgree{k) done 2007/12/1909/16/2007 16:08:43 EDTYes s dication (7.4.23 and 7.4.23.2) and also in MIH_Net_HO_Commit request (8.6.3.15), there is undefinde type LINK_ACTIONSd581g5021jShould be LINK_ACTIONv$change LINK_ACTIONS to "LINK_ACTION"^&cincludes^WWWWWWincludingWWinclusionWWincoherentWWincoherentusageofsinglevsdoublequotationmarksVincoherentusageofsingularorpluralVincompatibleWincompleteWWinconsistencyWJWinconsistentzW{W3Winconsistentontableformatsforprimitiveparametersegp3Vincorporate)WincorrectWIWWW:W;WWincorrectlyWincreasingWWWincrementingWincudeWindeedWindefiniteWindependenceWindependentW'WWWWWWWindicateWWW=W\WaWbWwWWWWWindicatedWWWWWWWWnical_32`44a5.7.2c DisapproveGProducer^ Technical_32`44a5.7.2cd507g3797 2007/09/1709/16/2007 12:18:13 EDTL5EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_79`15a 7.4.1.1.3c"In the case of remote discovery, this primitive may contain the SupportedMihEventList, SupportedMihCommandList, SupportedIsQueryTypeList, and SupportedTransportList parameters to enable mutual discovery of each other's capabilities."d561g5041j"In the case of remote discovery, this primitive may contain the SupportedMihEventList, SupportedMihCommandList, SupportedIsQueryTypeList, and SupportedTransportList parameters of the local MIHF to enable mutual discovery of each other's capabilities."wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes s e SupportedMihEventList, SupportedMihCommandList, SupportedIsQueryTypeList, and SupportedTransportList parameters of the local MIHF to enable mutual discovery of each other's capabilities."wAgree{k) done 2007/12/0709/16/2007 15:56:25 EDTMarkedYes 07/10/3009/16/2007 03:08:31 EDTNoRcI do not see a way for the network to query a mobile node to determine what radios it has present (e.g, GSM, 802.11) and whether or not they are powered up.d72g5530jAdd this capability.vAThe MIH_Get_Link_Parameters primitive in the draft (pg 98, subclause 7.4.15) addresses this. If you invoke MIH_Get_Link_Parameters with no link identifier, it shall return back the available links on the MN. You can then query the power up state of each individual link.wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEHeubaum, Karl FFApproveGProducer^ Editorial_268`9aH.7.1cMInsert "The" before "Following handover flow refers..." (not proper English).d71g5531j1Change to "The following handover flow refers..."{k) done 2007/12/1909/11/2007 12:03:15 EDTNo ooowered up.d72g5530jAdd this capability.v which shows the mobility management architecture that 802.21 specification is based upon.#'noensWWWWWWWnoensrichardhVVVVVVVohba7W8W9W:W;W<W=W>W?W@WAWBWCWDWohbayoshihiro7V8V9V:V;V<V=V>V?V@VAVBVCVr this purpose.d411g4542jDelete "prepares resources, " 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_114`40cStates that it "prepares" resource for handover. This is just a query, no resources should be allocated and/or reserved (since there is no method for releasing them if the handover doesn't proceed). The N2N_HO_Commit should be used for this purpose.d411g4542er. This is just a query, no resources should be allocated and/or reserved (since there is no method for releasing them if the handover doesn't proceed). The N2N_HO_Commit should be used for this purpose.d411g4542 2007/09/1709/16/2007 03:08:31 EDTNoWQWUWWgx109/16/2007 23:46:35 EDTYess45a5.6.2.6.jtheseWWW5W]WfWkWlWmWWWWWEWWWWthesesWtheyWWWWWtWthing0WthingsWthisWWWWWWWWWWWWWWWWWW WWW"W#W&W(W)W-W0W7W@WCWGW`WbWgWhWjWnWoWvWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW.W3W=WBWJWMWPW^WcWWWWWWWWWWWWWWWWWW W WW(W,W7WWthroughoutWWthroughputWFWthus]Wtile$WtimeWWWWtimerW`WWtitleZWtlvWWWWhcasimilarmechanismmaybeavailableforieee802.16forthi Vastawithipv6interfacedoesnotneedtoknowwhethertheVa-1wWyWaaa7WabbreivationGWHWWWW<WgWvWWWW'WaboveWFWJWabreviationWabritrary1Wabsence6Wabsenceofamedia-dependentsapforgsm/egprsthereisonly6VabsoluteWabstractWabstractionsWacWacceptedWaccessWWWW W WWWW&W1W5W6WOWWWWWWW WWWaccessibleuWaccommodateWaccomplishedWaccordingWWW"W#WKWLWMWNWWaccordingtotableb-2page176networkerrorisindicatedbVaccount~WWWackWWWWWWWWWW'WackfailureisnotrelatedtoplrackfailureisatransmitVack-rspWW\FEZuniga, Juan CF DisapproveGProducer^ Technical_293`47cnon existing primitived276g5326j@replace M-MTM-RSP (Deregistration) by C-NEM-RSP (Deregistration)wAgree{k) done 2007/12/1909/14/2007 17:39:46 EDTYes E Sood, KapilF DisapproveGGeneral Interest^ Technical_46`60a6.5.2ca6.5.2cent and some functionality is still needed inside these messages in order for them to be useful for other wireless technologiesd277g5325jXInclude the missing functionalities in the N2N Commit messages as defined in 21-07/320r0vKeep the TargetPoAwAgree 2007/12/0109/14/2007 17:39:46 EDTYesEZuniga, Juan CF DisapproveGProducer^ Technical_293`47cnon existing primitived276g5326j@replace M-MTM-RSP (Deregistration) by C-NEM-RSP (Deregistration)wAgree{k) done 2007/12/0109/14/2007 17:39:46 EDTMarkedYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_46`60a6.5.2cion+WWwdÃ1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23Ã32Ã3 1Ã300Ã3@/Ã3P.Ã3`-Ã3p,Ã3+Ã3*Ã3)Ã4(Ã4 'Ã40&Ã4@%Ã4P$Ã4`#Ã4p"Ã4!Ã4 Ã4Ã5Ã5 Ã50Ã5@Ã5PÃ5`Ã5pÃ5Ã5Ã5Ã6Ã6 Ã60Ã6@Ã6PÃ6`Ã6pÃ6 Ã6 Ã6 Ã7 Ã7 Ã70Ã7@Ã7PÃ7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBackWNo o1YjlistofsupportedmiisquerytypesonthelocalmihfVlistofsupportedtransporttypesonthelocalmihfVlistedWWlisteningWlistskWlWmWWWWWW&Wlocally WW+WlocatedWlong2WlongitudeWlongitudeshouldbenormalizedtowithin180degreespositivVlook WW2WlostWlowerWW;Wlsb=WmacWWWWWW;WmachinesWmain5WmakeWWWWWW5W=WfWmaketheannexnormativeVmakes0Wmaking+W]Wmakingtheseparametersoptionaldoesn'tsolveanyproblemi]VmanagementWWWWW(W<Wmandatory5Wmap5WmappedWmappingWWmappingsWmarkedWWmasked=WmatchWWWmaterialWWmaxWmaximumWmaximumdataratein802.11termsisthehighestavailablebVEE Cole, Terry LF DisapproveGGeneral Interest^General_292aL.1cfI do not agree with providing a references to named internal IEEE WG 802.21 documents in the standard.d201g5401ted IS Query Parameter Type in MIH_Capability_Discover.{response,confirm} primitives and MIH_Capability_Discover response message.wAgree{k) done 2007/12/0709/13/2007 16:03:47 EDTMarkedYes EE Cole, Terry LF DisapproveGGeneral Interest^General_292aL.1cfI do not agree with providing a references to named internal IEEE WG 802.21 documents in the standard.d201g5401Type in MIH_Capability_Discover.{response,confirm} primitives and MIH_Capability_Discover response message.wAgree{k) done 2007/12/0109/13/2007 16:03:47 EDTYesEE Cole, Terry LF DisapproveGGeneral Interest^General_292aL.1cfI do not agree with providing a references to named internal IEEE WG 802.21 documents in the standard.d201g5401201g5401|߃||_|o&j8-octetW8.2.1W8.2.2WWWW8.2.2.2W8.2.3.5.1W8.3W8.3mihprotocolstepsV8.3.1W8.3.1informationqueryV8.3.2W8.3.2resourceavailabilitycheckV8.3.3W8.3.3resourcepreparationV8.3.4WWRWRWRWrenceRWRWRWRWRWferenceRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWeRWRWRWRWRWRWRWRWRWRWRWerenceRWRWceRWRWRWenceRWRWRWRWRWRWRWRWrenceRWRWRWWRWRWRWRWWRWRWRWRWX*jisn'tWissuetWwWWer^GeneralcA The draft is very verbose and inserts too many out-of-scope examples only to mention that they are out of scope. While the intention of assisting comprehension is appreciated, it also adds ambiguity about the scope and makes the definition/specification less focused. d466g4487jAllow the discussion of applicability of MIH ONLY in the Section 5 and informative annexes. The other sections shall only DEFINE and SPECIFY MIH, without any repetitive examples of applicability in mobility management, etc. 2007/09/1709/16/2007 06:10:15 EDTYesߴon less focused. d466g4487jAllow the discussion of applicability of MIH ONLY in the Section 5 and informative annexes. The other sections shall only DEFINE and SPECIFY MIH, without any repetitive examples of applicability in mobility management, etc. 2007/09/1709/16/2007 06:10:15 EDTYesߴd465g4488 2007/09/1709/16/2007 06:10:15 EDTdÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCÃCÃCÃDÃD ÃD0ÃD@ÃDPÃD`ÃDpÃDÃDÃDÃEÃE ÃE0ÃE@ÃEPÃE`ÃEpÃEÃEÃEÃFÃF ÃF0ÃF@ÃFPÃF`ÃFpÃFÃFÃFÃGÃG ÃG0ÃG@ÃGPÃG`ÃGpÃGÃGÃGÃHÃH ÃH0ÃH@ÃHPÃH`ÃHpÃHÃHÃHÃIÃI ÃI0ÃI@ÃIPÃI`ÃIpÃIÃIÃIÃJÃJ ÃJ0ÃJ@ÃJPÃJ`ÃJpÃJÃJÃJÃQ~ÃQ }ÃQ0|ÃQ@{ÃQPzÃQ`yÃQpxÃQwÃQvÃQuÃRtÃR sÃR0rÃR@qÃRPpÃR`oÃRpnÃRmÃRlÃRkÃSjÃS iÃS0hÃS@gÃSPfÃS`eÃSpdÃScÃSb007/09/17GProducer^Editorial (was Technical)c,no Info Response Binary List TLV in Table C2d583g5019jIn chapter 8.6.4.2 MIH_Get_Information response change the table entry from "(Info Response Binary List TLV)" to "(Info Response Binary Data List TLV)"{k) done 2007/12/1909/16/2007 16:08:43 EDTYesEWilliams, Michael GF DisapproveGProducer^ TechnicalcThe info from MN* is informative and so it does not contain the ACTION_EXECUTION_TIME like the NET* messages. Therefore, NET* is using LINK_ACTIONS_REQ and RSP.d582g5020jACTION_EXECUTION_TIME from NET*wDisagreey deferred.{l) none needed 2007/12/1909/16/2007 16:08:43 EDTYes EWilliams, Michael GF DisapproveGProducer^ Technical_121cOn messages MIH_MN_HO_Commit.request and MIH_MN_HO_Commit.indication (7.4.23 and 7.4.23.2) and also in MIH_Net_HO_Commit request (8.6.3.15), there is undefinde type LINK_ACTIONSd581g5021jShould be LINK_ACTIONNK_ACTIONINK_ACTION "LINK_ACTION"_McareWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW$W&W.W4W<WJWKWLWMWNWeWkWlWmWqWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW W'W/W>W?WZW\WgWmWtWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWarethenonormativereferencesusedbythisstandardegwhaVW9Wlevyjosephs6V7V8V9VmqWrWmarcW W W W W WWWWWWWWWWWLcpagesWWpairIWpairedWpairing WparaWparagraphWWtWWWWW/WWWparagraph/bullethWparagraphsWWparamW2WFW[W^WaW2WparameterWWWGW[W`WWWW6WDWIWYWWWWWWparametersWWWWWWWWW WGWUW^WaWfWqWWWWWWWW2W3WJWaWWWWWWWWWWparametersdcducdsibsystemparametersarenotdefinedVparametersforlinkgetparametersprimitivelinkparamtype2VparametesWparenthesis1WparmetersWparsing=WpartWW6W=WWWWWWWWWWWWWpartiallyWparticularW[WWWWWWpartnerWWWKWLWMWNW csub-clause5.2.1itisbothunnecessaryandinexacttoempha@Vsub-clause5.2.1itiscontradictorytostatethatmihfmay?Vsub-clause5.6.1aserviceprimitivedescribesaninteracti>Vsub-clause6.5.5.1regardingthesizeofthelengthfieldin=VsubclauseW"W#W$WW0WWWsubclausesWsubjectWWsublayerWsubmittedWsubnetWsubscribeWWWsubscribedWsubscriberWWWWsubscriptionWWWWWWsubsequenteWsubset5WsubtractingWsuccessWsuccessfulWeWWsuccessfully WWWsuchWWWW W WW=W?WWWWWWWWWWW&W'WWWWWWWWWWWWsuffersWsufficientWWWsuggestWWWWWWWWWWWWdisapprovevoteor supported access networks and be made available to the MIH Users."d500g3804j'Remove "for supported access networks". 2007/09/17H rjformat>W3WWformataccordingtoieeestandardsstylemanualuselowercaVformer%WqWforwardwWfqdnWfragmentationWfragmentation/reasseWframeWWframes WW(W7WframeworkWfrequencies1WfromWWWWWWWWWWWWWWWW'W5W6W7W@WFWHWdWgWWWWWWWWWWWWWWWWWW W W!W"WCWDWIWMWQW_W`WjWxWWWWWWWWfromclause5therewasaregistrationanddiscoveryprocessVfromline12deletetextandgeneratesanerrorVfromline49deletetextandreportserrorVfromline65deletetextandreportserrorVionsݴWvertical/horizontalUWveryܣWܭWܮWܯWܰWW*WIWݷWݺWWWW;WRcfitWWfitsWfixedWWHWWWWWWflexibleWflow*WflowswWWfocused<WfollowedWwWfollowingJW_WtWfontWfontofparametersinlistneedstobemadeconsistentVforWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW%W'W+W/W0W4W6W7W:W=WBWCWGWJWKWLWMWNWYWZW[W\W]W^W_WcWeWfWqWrWsWxWyW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWK jAInsert a new paragraph and replace the single sentence starting at "Another possibility" with the following text. Then leave the remaining text after the sentence to follow the replacement text. The IEEE 802.21 supports another important aspect of optimized handover, link adaptation. A user may choose an application which requires a higher data rate than available on the current link, necessitating a link adaptation to provide the higher rate, or necessitating a handover if the higher rateBs is unavailable on the current link. After a handover from one point of attachment to another, the new link may provide different bandwidth or different transmission conditions (for example delay). These new conditions may affect protocols during and after the transition. Rapid notification of the changes is essential to optimizing the adaptation to the new conditions.api- adopted the replacement sentence but left out the additional description text proposed by the commentor{k) doneeHab2.5VVb2.6VVb2.7VVVVb2.8UVXVVb2.9;V<VVb-12WWb-4Wb14WWb2.11b2.6b2.8b2.9.1b4WWc9dWST.e WfWg-generalŃhWWh7.1Vh6&iWjWkᑃᒃᓃᔃᕃᖃᗃᘃWlWEWWl1EVmYWZWm1YVZVn/a⛃othersWWWtableWWWWWWWtableb-12VVtableb-4Vtableb14VVtableb4VVVVVon. In the contrary, it would impose needless constraints to the implementation.\d235g4718j3remove definition and all occurences of MIH_NMS_SAP 2007/09/1709/14/2007 03:15:28 EDTYesEGiesberts, Pieter-PaulF DisapproveGProducer^ Technicalcd234g4719 2007/09/1709/14/2007 03:15:28 EDTWKWexpectedWPjIremove Annex J "Requirements to support 802.21 by L3 and above transport"wAgree{k) done 2007/12/1909/15/2007 22:08:13 EDTYes E Xie, QiaobingF DisapproveGUser^ Technical_203`1c&The missing definition must be filled.d355g5247jDefine the missing definitionvDelete Network Securityw Principle{k) done 2007/12/1909/15/2007 22:08:13 EDTYes s agram and description.w Supercededydeferred 2007/11/2609/16/2007 01:46:33 EDTYesE Xie, QiaobingF DisapproveGUser^General_316cAnnex M.6 seems redundant and not adding much value because similar materials have been covered in the example call flows in Annex H and Information Service examples ind357g5245j remove M.6wAgree 2007/11/2609/15/2007 22:08:13 EDTMarkedYesich is what the 802 architecture is based on. You really should have discussed this with 802.1 experts long before presenting this kind of material for Sponso:)jconditions W%WWconductWconference)WconfigWconfigurable`WconfigurationgWkWlWmWconfigurations%WconfigureWWLWQWXWoWconfiguredW`WconfirmWWWWCWDWconformance%WWWconnectedWconnectionWWbWWconsequenceWconsider WWW+W9WWWconsiderationWconsiderationsWconsidered WWWconsistentWW3WWconsistentlyWWWwWxWzWconsistentlyaddorremovemobilitymanagementfromentiredxVconsistentlyuseonevaluewVconstructstWcontainW%W2W^WcWcontained7WcontainerWWWWWcontentW0WWcontentsSWWWcontextW0Wcontexts WWcontinutity&WcontributionWWWWWWYWWW2W6WV 'jBative is to entirely remove 3GPP from the list of access technologies that 802.21 can operate with (everywhere in the 802.21 draft specification).Ã$PÃ$`Ã$pÃ$Ã$Ã$Ã%Ã% Ã%0Ã%@Ã%P~Ã%`}Ã%p|Ã%{Ã%zÃ%yÃ&xÃ& wÃ&0vÃ&@uÃ&PtÃ&`sÃ&prÃ&qÃ&pÃ&oÃ'nÃ' mÃ'0lÃ'@kÃ'PjÃ'`iÃ'phÃ'gÃ'fÃ'eÃ(dÃ( cÃ(0bÃ(@aÃ(P`Ã(`_Ã(p^Ã(]Ã(\Ã([Ã)ZÃ) YÃ)0XÃ)@WÃ)PVÃ)`UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23Ã32Ã3 1Ã300TDTDTCW|EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_34`54a6.2.5cWhat type of authentication is referenced here? There is no security specified for IEEE 802.21. I assume the reference is to link layer security. If it is, please state so or provide an authentication mechanism.d311g5291j?Explain type of authentication is referenced in this paragraph.ted.w Principle 2007/11/2609/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_34`54a6.2.5cWhat type of authentication is referenced here? There is no security specified for IEEE 802.21. I assume the reference is to link layer security. If it is, please state so or provide an authentication mechanism.d311g5291j?Explain type of authentication is referenced in this paragraph.e events are incorrect they may be retracted.w Principle 2007/11/1809/14/2007 23:15:41 EDTMarkedYeschaelF DisapproveGGeneral Interest MpsuperceedWW\WWsuperceedby429\Vsuperceedby615VVsuperceedby624Vsuperceeded[WWWWW W>WWWsuperceededby260V Vsuperceededbycomment116wheregroupdisagreedtomove8.2Vsuperceededbycomment207>Vsuperceededbycomment454VVVVsuperceededbyresolutionincmt429[VsupersededWsupersededbycomment11VsupportWsupportsAWsytemWtableWWWWW2WRWWWtablec-2page207line24mapsthepoatlvtolinkidVtablesWtalksWtargetWW WWtd-scdma3Wtdd3WtechWtermWterminatedWtextWWWWWW/WWtguWWthanAWthatWWW W,WnWoW}WW}WWWWWWWWnWoW}WWW}WWWtionofea2V*#ctheieee802.21standardspecifiesmihfunctionthatcouldbVtheimplementordoesn'tcarewhatmayormaynothavebeenp,VtheinfofrommnisinformativeandsoitdoesnotcontaintVtheinformationmodelproposedinfigure19isoverlycompliVthelinenumbersarepositionedsuchthatthechangebarsovVthelinkactionrequestissenttomacwimaxhoweverthecor_Vthelinkactionrequestissenttomacwlanhoweverthecorr`VthelocationusedintheinformationmodelisforthepoafoVVthemaymakesitsoundoptionalVVthemediadependantnativedefinitionsforthemihcommonteVthemihfunctionsinmnandnetworkentitiescommunicatewitVthemihmnhocompletemessagemaybesenttothetargetposUVissingdefinitionmustbefilledVthemobilenodeiscapableofsupportingmultiplelink-layerVtheneedanduseofthemihnethocandidatequerycommanda V^cinformativeW%W/WWWWinformedWinfrastructureWinitWWinitializeWinitiatepWvWWinitiatedgWqWwWinitiatingWinitiatorWinputWinsertWWinsertthebeforefollowingconventionsareusednotproperVinsertthebeforefollowinghandoverflowrefersnotproperVinserts<WinsideWWinstanceWWinstancesWinsteadWWWW WZW9WinsufficientWWWintFWWint2^WWintegrationWintendWintendedWWWWWWintentfWvWWintention<Winter-operability&WWWinter-operabilityrequirementsregardingminimumsetofmand&Vinter-operableWinter-operablyWinter-techWWinter-technologyWWWWinter-workingWtcpositiveW+W,Wpossibility'WWpossibleWWWWW]W(WWWWpostwWposted_WbWeWyWyWyWyWyWyWyWyWyWyWarts (like Annex F and G and H collapsed into one), a.k.a F becomes F.1 and G becomes F.2, H becomes F.3 and so on.ITEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_25`40a5.5.3c0The IEEE 802.11 PoA is likely an ESS, not an AP.d306g5296jChange "Aps" to (ESS or BSS)..vRemove AP in parenthesis.wAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYess609/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_25`40a5.5.3c0The IEEE 802.11 PoA is likely an ESS, not an AP.d306g5296jChange "Aps" to (ESS or BSS)..vRemove AP in parenthesis.wAgree{k) done 2007/11/2609/14/2007 23:15:41 EDTMarkedYeso, MichaelF DisapproveGGeneral Interest^ Technical_18`6a5.3.4cAThe first sentence of the paragraph states that geographic information can be used to obtain handover candidate information. However the rest of the paragraph goes on to discuss how the information is transported to the MN and how the mechanism is out of scope.d305g52975297ciassumethatthetlvtypeassignmentisnormativeforthisVibelievethisisalreadyintheieeedictionaryFViblievetheuseofacronymsintheabbreivationtobeconfuGVHVicannotbelievethataproposedstandardsuchasthiswhichVidonotagreewithprovidingareferencestonamedinternalEVidonotseeawayforamobilenodetousemiistodeterminVidonotseeawayforthenetworktocommandamobilenodeVidonotseeawayforthenetworktoqueryamobilenodetoVidon'tunderstandthelogicbehindclassifyinglinkeventsVidontthinkthisisunambiguousVihaven'tyetfoundanystatementaboutconventionsregardin Vice>WAW both 802.11 and EGPRS, must support L3 IP trasnport option (but doesn't need L2), must support the following SAPs and the following list of primitives. Or, define above minimum MIH protocol sets per access technology if supported in the MN. Like, any MN that has an 80 jaddacross-referenceforprimitivesdefinedinclause7indVaddaparagraphinthisclausetostatethesecurityconsideVaddareservebitattheendofothefirstoctetVaddastatementrequiringthatthenumberofentriesineachkVlVmVaddastatementtoallowthepossibilityofmihinformationVaddastatuscodeindicatingsuccess_VaddastatusresultthehandovercompleteindicationtoaccoeVaddasubclausedefiningconventionsforpdustructures/draw VaddaccessnetworkidentifierastheefirstparameterVaddanoptionwheremihn2nhocommitcanrequestreservatio VaddbitforlinkactioncommandsVaddbitformihlinkactioncommandnVaddblanklinkbetween9and10hVaddcpichec/i0andcpichrscpwhicharethe2mostimportan2VadddefinitionVaddhyphentoparameter-extractionVaddipconfigurationmethodtonethocandidatequeryrespongV:46:47 EDTYes"cmutualWmutuallyfWTWTWedstobecorrectedlink--which$Wlink-commandsTWTWmawithegprsforexalink--which$Wlink-commandsTWTWlink-commandsTWTWesofoldandnewacclink--which$Wlink-commandsTWTWoldandnewacc߄Vlink--which$Wlink-commandsTWTWWWWWWW W%W݇WݡWݤWݦWWstacksWWWݡWݤWݧWWstageWstand-alone{W|W}Wstandard܈WܯWWWWW W-WݐWݑWݒWݔWWWWWWWWWWWstandardized܇W܈WܯWstandardizesWstandardizingWWݦWݧWstandardsvWWWWstartednWstartingWstartsWWWstate܈WWWWWWWW%W-WdWݜWݪWݾWWWWWWWWWWWWWstated W(EEmmelmann, MarcF DisapproveGAcademic^ Technical_30`1a5.6.1cFig 11 conflicts with Figures 9 and 10 for 3GPP and 3GPP2. Fig 11 correctly includes the MIH_LINK_SAP whereas the latter two illustrate an MIH_3GLINK_SAPd42g5560jChange Fig. 9 and 10v by comment 40w Superceded{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYes EEmmelmann, MarcF DisapproveGAcademic^ Technical_25`1a5.5.2ca5.5.2clmann, MarcF DisapproveGAcademic^ Technical_30`1a5.6.1cFig 11 conflicts with Figures 9 and 10 for 3GPP and 3GPP2. Fig 11 correctly includes the MIH_LINK_SAP whereas the latter two illustrate an MIH_3GLINK_SAPd42g5560jChange Fig. 9 and 10v by comment 40w Superceded{l) none needed 2007/11/2609/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_25`1a5.5.2cF DisapproveGAcademic^ Technical_25`1a5.5.2c_25`1a5.5.2ccd48g5554 2007/09/1709/10/2007 07:08:58 EDT/qjeitherremovethemihnethocandidatequerycommandorbettVeitheruse802.1abtoachievethisresultordemonstratewhyVelementWpWeliminateWelseiW'WelsewhereWenableWWW*WencodeWencodedWWWWencodingWWencrypt7Wend7WWWWWW4W=WWendingWendoWenhanced)WenhancementsWensureWWWWensuringWentireMWxWentirely'W9WentiresWWentitiesWWWWWWBWWWWWQWWWWWWWQWWWWQWWWLWQWWWQWWWWWWWWWQWWWWWWWWWWWWWWWWWWWWWQWWWWWWWgeWusagesWKcZThe contents of PoA System Information IE are not defined within the 802.21 specification.d90g5512j$Remove the IE or add the definition.p4 POA sytem information IE is defined at page 48 L59.v3The definition is in there (page 193 in draft D7.1)wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2c|The PoA channel range is an important characteristic of the network and should be included in the TYPE_IE_CONTAINER_NETWORK.d89g5513jW?W@WAWFWIWJWKWLWMWNWOW]W^WbWcWeWfWiWkWlWmWuWvWwW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWW W#WV_@jr1WTWVWr2UWr3TWVWr5Wr99/WradioWradio/dualWramificationsWranameWranamehomenetworktohomesubscribernetworkinthisclausVrangeWWrangesWrapidWrateWWWFWQWWratherWvWrawXWrdf.W0W4Wre-defineWre-orderWre-orderrowsoftable10Vre-organizeWWre-use1Wre-writeWWre-writedefinitiontodescribethefunctionandresultsVre-writingWre-writtenWttenWWeGProducer^ Technical_31`1a5.6.2cAbsence of a media-dependent SAP for GSM/EGPRS. There is only a MIH_3GLINK_SAP, but nothing is defined for GSM/EGPRS cellular, even though both seem to be in scope for 802.21 as part of 3GPP access technologies.d472g383221 as part of 3GPP access technologies.d472g3832 2007/09/1709/16/2007 07:13:12 EDTYeskgjaOn line 34 replace text "&for an MIH ACK message" with "&for an MIH ACK or MIH Response message."p=comment no longet applicable due to resolution of comment #11wAgree{l) none needed 2007/12/1909/14/2007 18:36:55 EDTYes E Julka, VibhorF DisapproveGProducer^ Technical_144`15a8.2.1cPNeed to add text to say how redundant ACK message are handled by the source MIHFd285g5317jAdd text "In this scenario the source MIH node may silently discard the duplicate acknowledgements." to the end of sentence ending with "&.by the source MIH node."p9no longer applicable because of resolution of comment #11vG Please refer to contribution 21-07-0302-01-0000-StateMachineSBCommentsw Principle{k) done 2007/12/1909/14/2007 18:36:55 EDTYes E Julka, VibhorF DisapproveGProducer^ Technical_143`50a8.2.150a8.2.150a8.2.1dd following text "and not within the scope of this standard."ee 2007/11/1409/14/2007 18:36:55 EDTYesucmanagementWWWWWWW#WWWWW#WxWWWWWWWWmanagerWWWmandated&W5Wmandatory5WWWWWWWmandatroyWmanipulatedWmanualWWWmanyW<WgWWWWmanyfiguresaremissingthevertical/horizontallinesindicgVmapWkWlWmWmappedWWWmappingWWWWWWWmappings5WWmapsWmarkedJWmarketWmarksWmatchWWWWWWWmaterialWmaterialsWWmaxWWmaximumWWWervices (notably, command service) it provides is dependent on prior sd471g3833 2007/09/1709/16/2007 07:13:12 EDTconlyanmihfcapablenetworkentityshallrespondwiththisVonlymihnetworkentityshallrespondtobroadcastedmihcapVoperateWoperatingWWoperationW&WWW'WoperatorWWWWoperator'sWoperatorsWWopportunityWopposedwWWoptimizationWoptimizeWoptimizingWoptionWW WWWWWWWWWWWWWWWWWWWWW W W WW&W'W,W1W7WDWEWYWeWgWnWoWwW}WWWWWWWWWWWWWWWWWWWWWorderWWW%WvWxWyWWorganizationWorganizedWoriginalWWWotherWWWWWWWWWW?WzW{WWWWWWother'sWbjRemove Packet Identifierp?- clarification made on the packet id - defer 2) to next round vA 1) Further clarify that the packet identifier is a container structure whose syntax and semantics will be decided by the upper layer (i.e., the user/subscriber of this event). MIHF and link layer just pass and return it and do not need to understand the syntax and semantics. 2) Consider adding a primitive to show explicitly that this packet identifier is passed along with the outbound data from the upper layer. w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYes1:08 EDTYes07/12/0809/16/2007 21:41:08 EDTYessexistent packet identifier common at both higher layers and link layers. TCP/IP layer uses its own sequence numbers which are not visible to MAC layers while MAC layer uses its own sequence numbers for link acknowledgements. What packet identifier is supposed to be used here?.d610g49927.3.10c/jissues WtWitWWWWWWWWWWWWWW W WWWW&W(W0W1W4W7W9WGWJWPWQW]W`WtWvWwWxWyWWWWWWWWWWWW9WJWRWSW^WcWlWWWWWWWWWW WeworthythattherewillbenodirectcommunicationVitsoundsasiftheresponsecontainstheacceptancerathervVitemsWitsWWWiWWWWitselfWWjWW.WWj1Wj5WjitterQWjob WjustWWkWWWW%W5Wk-1QWk-2WQWkeptWknowtWvWwWknowingwWl-4PWl1;Wl1/lapdm;Wl1/mac/rlc;Wl2W&W+W-W0W7WcWWl3W&W+W7WWWlaptop&Wlatest8WTclines38-52thestatisticalparameterslistedontheselinesVlines7-45theconceptofcountersismisusedonthispage8VlinkWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWW0W2W3W7W?WCWDWEWFWGWJWKWLWMWNWPWQWRW[W^WaWbWcWeW߁WߦWpWWWWWWWWWWWWWWWwirelesscW߁WߦWpWWWWWWWWWwirelesscW߁WߦWpWWWWWWWWwirelesscW߁WߦWpWWWWWWWWW G pthroughoutWW WtillWtimeWtimingWtlvWWWWWWtlvsWtoWWWWWWWWWWW WWWWW$W*W0W3WHWOWVWWVWVWVWdover".s generalinterestVVVVVVVVVVVVVVVVVVVV VVVVVVVOVPVQVRVSVTVUVVVWVXVYVZVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV-V.V/V0V1V2V3V4V5V6VEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVVWjwInclude current link identifier in the commit request and use the information from the link detected for the targetPoA.p*Add the source link identifier in 7 and 8.wAgree{k) done 2007/12/1909/04/2007 16:19:39 EDTNo E Golmie, NadaF DisapproveGGovernment/Military^ Technical_118cThe parameter TargetPoA does not have a proper type in the request and indication primitives. TargetPoA is defined as LINK ID but the definition of LINK ID is to contain the address of an MN only.d20g5582jiUpdate the definition of LINK ID to indicate that the link address could be the address of an MN or a PoAp0Updated in subclause 7. Checked in subclause 8. vUse LINK_TUPLE_Id insteadw Principle{k) done 2007/12/1909/04/2007 16:19:39 EDTYes s s eƒ3'ƒapprove3ƒheubaumkarlf approveƒ%"ƒapprove%ƒheubaumkarlf approveƒapprove}Fƒjestablishment0WetcW'W7W<WWWethernet&WethertypeW(W-Weven'W0W7WJWeventWWWWW]WbWwWWW+W,WeventsWWW?WtWWW(WWeventually5W7Weverywhere'WevidentWexampleWW WWW&W'W)W+W7W8WZWWWWW WexamplesWWW<Wexcedes0WexceedWexcellentWexceptionW7WexchangeBWwW'Wexchanged>Wexchanges WW7W>Wexchanging]Wexclusively7WexecactionQWexecutionWvWWexecutiveWexistWWexistingWWW1WWWAdd this capability. 2007/09/1709/11/2007 17:46:47 EDTYes4EMyles, Andrew FF DisapproveGProducer2007/09/1709/11/2007 17:46:47 EDTYes4EMyles, Andrew FF DisapproveGProducer46:47 EDT.(E Koh, BenjaminF DisapproveGProducer^General_71a7.3.10cAThere seems to be limited usefulness of the Link Transmission events due to lack of flexibility. For example, is it possible to specify a specific application data packets? Differentiation between protocol packets (e.g Binding Updates, Shim6 probe messages, etc)d230g5372jCIncrease the degree of flexibility for usage of the related events.vThis seems like trying to manage a priority queue and this kind of scheme may not be widely/reaily available. Further optimization seems difficult.wDisagree{l) none needed 2007/12/1909/14/2007 02:24:47 EDTYes 2/1409/14/2007 02:24:47 EDTYes s s W+Wuting+W+WWcomprisingWcomputing+W+W+W+W+W+W+W+Wuting+W+W+Wnt%WcomponentsWcomprisingWcomputing+W+Wg+W+W+W+W! cANeed to state at least a working assumption or list of 2-3 options for technical solution to MIH transport for 3GPP-based cellular technologies. If this specification is to apply to encompass 3GPP cellular, then an implementor must know which options he can use to realize the needed signalling. Independent of which SDO standardizes the solution, there must be at least a limited set of choices available ?d487g5115jAFor example, assume and describe here whatever MIPSHOP will produce one day can be used as one realization for IP-based external transport interfaces. Alternatively, describe a means to transport at least a limited set of MIH messages through GMM or GTP messages, like Direct Transfer etc., even if any formal specification would be incumbent to 3GPP one day. needa t least to describe or at least outline the principle of 2-3 technical approaches to guide an implementor. The only other alterny if supported in the MN. Like, any MN that has an 803%hvotherWWW4WWW&W+W,W@WGW}WWWWWWWotherissueswiththisfeaturecouldbeclarifiedseparately@Votherl2addresscanbecombinedwithlinkaddress4VouiWout WGWWWoutboundWoutsideWWWoverWWWownWp192WWp192l13WVp201WWp201l14WVp48WWp48l15WVp50WWp50l22figure19WVp52WWp52l62WVpacketWWWpageWWWW<WaWvWWWWIWWW&~ERajkumar, AjayF GProducer^ Technical_122`37cNeed to account for a locally generated MN_HO_Commit request (i.e. with destination MIHF as the local MIHF). Otherwise, it would trigger an indication (and corresponding response), which we don't want.d400g5202j>Change "request is received" to "request message is received".wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ation (and corresponding response), which we don't want.d400g5202j>Change "request is received" to "request message is received".wAgree{k) done 2007/12/0909/16/2007 03:08:31 EDTNo o o side of the link (e.g. when destination MIHF ID is the Network then the old link action specifies what action the Network should take).on MIHF ID side of the link (e.g. when destination MIHF ID is the Network then the old link action specifies what action the Network should take).ation can be True or Falsed378g5224kumar, AjayF GProducer^ Technical_131`64,djnotWWWWWWWWWW)W7W=WGW]WbWtWwWxWyWWWWWWWJWWWWWnoteW=WtWWnotethatforanetworkentitycomprisingofmultipleinterfVnoteworthyWnotification`WdWWnotificationsWnotionWnowWnowhereiWnowhereelseinthedocumentdowereferenceaparticulartyiViViVWnumeric=WoccurrenceWoctetWoctetsW=WHWofWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW"W#W$W&W'W(W+W,W0W3W4W5W6W7W;W<W=W>W?WBWCWIWKWLWMWNWXW]W^W`WbWdWiWWWhhcthismessageisusedforcommunicationbetweenthemihfonaVthisparagraphleadsmetounderstandthatthemihlinksapVthissectionisaduplicateoftheinformationthatisgivenVthissectionisduplicateoftheinformationthatisgiveniVthissectionisgrosslydisconnectedandsuffersfromlackoVthissectionmustbeextendedtogiveaclearideatotheim7VthisseemstoassumeanonexistentpacketidentifiercommonVthisstandardprovidesausefulsetoftoolstomakemihworVthissubclauseisaboutthemihnethocommitindicationpriVWWWWthroughoutWWthroughoutwholedocumentincorrectuseofindefinitearticlVthroughoutwholedocumentneedtobeconsistentintheuseoVthroughputWWFWthroughputisacommonlyusedcommunicationstermanditisVthrougputWthuskWlWmWuWtied1WWWWWWW"W#W$WvENoens, Richard HF DisapproveGProducer^General_282c-Annex J does not add value to the final spec.d104g5498jRemove Annex JwAgree{k) done 2007/12/1909/11/2007 17:47:21 EDTYes s ability benefits standardizing this interface will bring to the implementation. In the contrary, it would impose needless constraints to the implementation.6d105g5497j3remove all definition and mentioning of MIH_NET_SAPvby comment 105w Superceded{c) instructions unclear 2007/12/0209/12/2007 02:37:36 EDTYes ENoens, Richard HF DisapproveGProducer^General_282c-Annex J does not add value to the final spec.d104g5498jRemove Annex JwAgree{k) done 2007/12/0209/11/2007 17:47:21 EDTYessseral_282c-Annex J does not add value to the final spec.d104g5498jRemove Annex JwAgree{k) done 2007/12/0109/11/2007 17:47:21 EDTMarkedYesDTdmihposnetworkeܪV&XyjcaseWW0W7W;WWcasesWWW=WcategoriesW&WcategorizeWcause8WcellidWcellular WWcenterNWcertain W WWchangeWWWWWWWWWWW!W$W3W:WCWDWEWGWIWJWKWLWMWNWOWPWQWZW^W`WaWbWcWxWyWzW{W~WWWWWWWWWWWWWWWWWWWWWWWW0W7W9W:W;WKWLWOWPWQWXW[W]W_W`WkWoWqWuWvW{W|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWthenameaVVchangedescriptionofsourcelinkidentifiertospecifiesthKVLVMVNV߄WconWWWWWWWWWWWWWWWWWW&W7W?WFW[W`WbWfWkWlWmWpWuWWWWWWWWWWWWWWW WWWWW#W$W/W3W4W=WAWpWuWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWW WWW.WKWLWMWNWRW[W]WeWnWoWWWWWWW5WWWone-octetWone-to-onekWlWmWone/twoWonlyWWWWWWWWWWWWWW,W6W<W[WcWeWuWWWWWWWWWWW'W5WNWWWWWWWWWWWh,pcommentnolongervalidbecauseofresolutionofcomment11VVVcommentnolongetapplicableduetoresolutionofcomment11VcommentorWWcommitxWWWW WcompleteWKWLWMWNWconcernWWconcernedWconcludedWconfigWconfigurationWWconfigureoWconfirmmWconfusionWWWWconnectionWWconsistencyWconsistentWW0W3WcontainerWcontentWcontriWcontributionWWcontrol Wcontroller WconventionWcorrectWcosqWcountryWcoupleWcoverWcreateWcurrentWdataW WWWdatatypesectionisupdatedforbetterorganizationseeifVVVonseeifVVVVVVescribed at the end 2nd paragraph.d289g531331 EDTNoERajkumar, AjayF 403g4550 2007/09/1709/16/2007 03:08:31 EDTn=cthereforeWWWWWWWWWWWthereof7WtheseWWWWWWWWWWW WW.W7WqWvWWWWWWWMWWWWWWWWtheselinesstatethatthemnmayinitiateahandoverprocesvVtheseparametersarenotavailablefornetworkinitiatedhanqVthesholdWtheyWWW<WJWeWkWlWmWqWWWWWWWW/WMWWW:12 EDTYes!W!W(Wapplies!W!Ws!W!Wies!W!W!W!W!W!W!W!W!W!W!Won/sparql-qW)Wapplication/xml(Wapplies!W!Wplies!W!W!W!W!W!W!WjTPlease clarify and remove. Or add IP subnet prefix information of the new interface.vdJust providing IP Renewal flag is not sufficient. This may be valid when PoA and PoS are co-located.wDisagree{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_87`32a7.4.4cAMIH Event Subscription, as defined, has limited capability for practical uses. It should be possible for event subscription to set parameters for individual events that are being subscribed for. The parameters will be correspondingly be applicable only for that specific event. As an example, link-detect may result in inefficiency due to reporting of not so relevant networks. It should be possible to subscribe to see only specific network identifiers.d606g4996j Please see the contribution #305pSuperceed by 615.v,Adopt contribution #305-2 with modification.w PrincipleyRef 615.{l) none neededone neededWW[BcthepurposeandusefulnessofmihnethocandidatequerycomVV VVVthepurposeofthisprimitiveisunclearthetextindicatesVthereferencemodelfor802.11isincorrectthemodelshowsVtherequestcontainsdevicestatesrequestparameteroftypedVtherequestforthemihlinkactiondoesnotallowtosetacVtherequestedresourcesetparametershouldbeoptionalbecaVVthesectionistitledbinaryinformationqueryhoweveribelVthesecurityclausestatesthatinformationonlinksecurityVinkareVthetextappearstoindicatethatalinkdetecteventisposbVthetextinthestandardstatesthisstandardmaycontainVthetextstatesthattheanisresponsibleforprovidingasVthetextstatesthatthereshouldbeatleastonequeryVthetextsdescribesthisaseitheranmihusertomihuserewVtheirWWvWthemrWsWWthemselvesWBvcalculate@cells@Mchangestackinallplaces@changeupperlayerstomihusers@channel@commandsarenotsentfrommihftomihusers@{commenter@contain@ecurrentlinkidentifie@decisions@Adefineddeleteddeployment@fdifficult@4o the request/response mechanism. 2007/11/1309/14/2007 23:15:41 EDTYesaelF DisapproveGGeneral Interest^ Technical_170`1a8.6.4.1ceA request-response mechanism will not scale to accommodate large numbers of MIH-capable mobile nodes.d324g5278jProvide the capability for the MIH-capable mobile node to broadcast information to devices at a PoA in addition to the request/response mechanism. 2007/10/0709/14/2007 23:15:41 EDTYesit does (and processes).d463g3841y what it does (and processes).d463g3841 2007/09/1709/16/2007 06:10:15 EDTYesf$ccgeographicWgetWpWtWWWW2WJWWWWgive7WWgivenWIWJWaWWWW&W)WWWWWWWgiventheobvioususageofmihinafmipscenarioitbehoove&VgivesWglobalWgoWW%WWNWWWgoalWgoesWWWgoingWWW+W,WWgoodWWW%WWWWgprs0Wgprs/edge7WgrayWgrosslyWgroup$WWWgroupedWgroupingWWgsmWW mobile node knows the desired network. Since it is not needed, it is just extra information to get out of sync between the access network and the MIIS..d86g4867jDelete the PoA MAC address. 2007/09/1709/11/2007 17:46:47 EDTYes0EMyles, Andrew FF DisapproveGProducer^ Technical1709/11/2007 17:46:47 EDTYes0EMyles, Andrew FF DisapproveGProducer^ Technical tjAThat the MIH User upon receiving the Net_HO_Commit.indication, issues the appropriate primitives to carry out the actions specified in the request (i.e. issues MIH_Link_Action primitive). Upon completion, the MIH User constructs the appropriate response and issues a Net_HO_Commit.response. Note: somehow the MIHF needs to know that the actions are in response to a handover request otherwise, it would not know to issue the handover imminent/complete events.vChange "Upon receipt of the MIH_Net_HO_Commit.request, the MIHF issues" to "Upon receipt of the MIH_Net_HO_Commit.indication, the MIH User issues .." (Qiaobing, please verify).w Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNouERajkumar, AjayF GProducer^ Technical_120`9c120`9c the appropriate response.Md410g5192jter. 2007/10/3009/16/2007 03:08:31 EDTNopERajkumar, AjayF GProducer^ TechnicalpERajkumar, AjayF GProducer^ Technical wagreecdefghijklmnoqrstuvwxyz|~〃ぃゃッ㄃ㅃㆃ㇃㈃㊃㋃㌃㎃㏃㔃㕃㖃㙃㛃㟃㢃㤃㦃㧃㩃㪃㫃㷃Ƀʃ˃уԃՃփ؃كڃۃ disagreeኃጃᓃᖃᩃ᪃᫃ᯃᶃẃῃƒÃȃك &'5=IJv ⮃ⲃƒƃ΃σЃ҃ӃԃՃ  &()+,58p㒃㚃㞃㥃㨃㰃㳃㴃㶃㸃㹃㼃㽃㿃ÃŃƃ ofWoutWqWWWoutofscope/unresolvableqVVVprincipleᆃዃᑃᒃᘃᚃᛃᜃឃ᠃ᢃᧃᨃᬃᭃᮃᰃ᱃ᲃ᳃ᴃᵃ᷃ḃὃăŃƃ̃̓΃ЃԃՃփۃ c|oERajkumar, AjayF GProducer^ Technical_111`6263cA$It appears that IP Address Information Status is unnecessary. What does IP Address Information Status do? We already have IP Configuration Methods (along with one or more server addresses). If one of the server addresses is not listed then I think we can figure out that it was not available.$d415g5187Delete this parameter.ppbut kept the same param in N2N response/confirm as it is unclear whether the comment applies to that case or notvmake this optionalw Principle{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo oERajkumar, AjayF GProducer^ Technical_111`6263cA$It appears that IP Address Information Status is unnecessary. What does IP Address Information Status do? We already have IP Configuration Methods (along with one or more server addresses). If one of the server addresses is not listed then I think we can figure out that it was not available.$d415g518701- ESreemanthula, SrinviasF DisapproveGGeneral Interest^General_15`56a5.3.2.2cFigure 13 is 16 pages away.d595g5007j8remove reference or make a reference to a future sectionpremoved the x-ref wAgree{k) done 2007/12/1909/16/2007 21:41:08 EDTYesstion.d596g5006jClarify the use.vcThis clarifies PoA and PoS and provides Reference Points which provides context for the interfaces.wDisagree 2007/11/2609/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^General_15`56a5.3.2.2cFigure 13 is 16 pages away.d595g5007j8remove reference or make a reference to a future sectionpremoved the x-ref wAgree{k) done 2007/11/2609/16/2007 21:41:08 EDTMarkedYesch provides context for the interfaces.wDisagree 2007/11/1809/16/2007 21:41:08 EDTMarkedYeseral Interest^General_19`1a5.4.207/11/1209/16/2007 21:41:08 EDTvercWhy does the mobile node need to know the IP address of the PoA? Should this be the IP address of the PoS? I can understand why the IP address of the PoS is useful--it's the peer entity of the MIHF in the MN.d87g5515jChange to IP address of PoS.pAThis is a PoA container. PoA does not necessarily has any PoS, not to mention hosting a LIST of PoSs. Therefore, simply change "PoA IP address" to "PoS IP address" will only create more confusion. If the concern is that the PoA IP address is not very useful, suggest to remove it.wAgree{e) editor disagrees 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2c6.5.5.2c/2809/11/2007 17:46:47 EDTMarkedYesEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2ation IE are not defined within the 802.21 specification.d90g5512j$Remove the IE or add the definition. 2007/11/12g4525 2007/09/17W)cthingW0WWWWcer^ Technical_292`47a6.2.1c{A description of the available options for which transport protocol an MIH node would use to discover MIH peers is missing.d483g4470jAuIntroduce a brief description of the L2 transport protocol and the L3 IP-based trasnport protocol options. For example, "MIH node can acquire list of MIH peers either locally or remotely. Locally can mean a pre-configured list. Remote acquisition can mean making use of the following MIH transport options, X, Y, Z". Could consider to move test in page 33 lines 6-14 here ?u 2007/09/1709/16/2007 07:13:12 EDTNoߣERudolf, MarianF DisapproveGProducer^ Technical_292`47options, X, Y, Z". Could consider to move test in page 33 lines 6-14 here ?u 2007/09/1709/16/2007 07:13:12 EDTNoߣERudolf, MarianF DisapproveGProducer^ Technical_292`47d482g4471 2007/09/1709/16/2007 07:13:12 EDT^technical  #$%.256789:;<=>?@ABCDIJKLMNTUVWXYZ[\_`dmnopqrsuwxy〃ぃゃッ㄃ㅃ㈃㉃㊃㋃㌃㍃㒃㓃㗃㙃㛃㞃㤃㥃㧃㨃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃу҃ӃԃՃփ׃كڃۃ܃݃ ink of the handover". 2007/09/1709/16/2007 03:42:16 EDTYes2tifies the current link" to "This identifies the source link of the handover". 2007/09/1709/16/2007 03:42:16 EDTYes2d458g3846 2007/09/17Dp8.6 has been updated, still work to do in Annex C. - Instead of adding the additional row. Add the following description before Table C2. "TLV type value 110-127 is reserved for experimental TLVs."wAgree{k) done 2007/12/1909/16/2007 10:24:17 EDTNo7 EDTNooEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_143`8a8.1-07-0302-00-0000w Principle 2007/11/1809/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145`46a8.2.2.1cE"retransmitted MIH Response is received due to a lot MIH ACK;" "lot"?d567g5035j?"retransmitted MIH Response is received due to a lost MIH ACK;"wAgree 2007/11/1809/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_143`8a8.1proved readability and usage description of the messaged298g530409/16/2007 03:38:14 EDTYes jmoreWW W=WW@WQWWWmostW2WWWmoveW WWW"W#W*W+W9WWWWWWWWWWWWmove6.3.2contenttotheendorafter6.3.3discussionVVmoveallnormativereferencestosection2considermovingth Vmovefigure12to6.2.1*Vmovelinkeventsubscribeandunsubscribetosection6.3.3VmoveoraddthisinformationintotypeiecontainernetworkVVmovethelinenumbersleftbyafewmmVmovethistobeasubclauseof6.2"V#Vmovement%Wmoving W5WmuchWmultipleWWWmust&W5W7WWWmutualWmutually]WnWWn/8Wn2nWWWJWjWWWWW WKWWWnaiWname4WzW{WWWWyWWnames2WnativeWWnecessary=WW ^>cstandardizedWWWWstandardizes'WstandardizingWWWW#W$WWWstandardsWWWWWWWWWstartedWgWstartingWWstartingwithanotherpossibilitythetextdriftsawayfromVstartsWWWWWstateWWWWWWW'W7W?WvWWWWWWWWWWWWWWWWMWWWWWWWWWWWWteseWrWsWtWWWWWWWWWJWqWWWWWWWWWWWWstatesthatanmihusermustgeneratearesponsetotheinditVstatesthatitmayindicatethatthemnmayhavestartedahVstatesthatitpreparesresourceforhandoverthisisjustarVsVstaticWstating?WWstationWstationary%W>.vEEmmelmann, MarcF DisapproveGAcademic^ Editorial_12`64a5.1.4c missing commad34g5568jCinsert a comma after networks: ".... target networks, in order ..."{k) done 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_12`27a5.1.2cQsentence defines "service continuity" but the definition is not aligned with 3.43d33g5569j9Align definition or do not re-define it in this paragraphv Delete 3.43wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_12`15a5.1.115a5.1.115a5.1.1Qsentence defines "service continuity" but the definition is not aligned with 3.43d33g5569j9Align definition or do not re-define it in this paragraphv Delete 3.43wAgree{k) done 2007/11/1809/10/2007 07:08:58 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_12`15a5.1.1ycappliestoalltechnologyspecificreferencemodelsupto5.VapplyWW W'W1Wappreciated<WappropriateWWWWtWWappropriatelyWWWapproximatelyWapsWarbitraryW'WarchitecturalWWarchitecturallyWarchitectureWWWWWWWWparts of the primitive state that the link will be valid for Time Interval, while other parts imply that the link can go down anyB time within Time Interval. I pity the system that assumes that the link will be valid for Time Interval, only to have it yanked away earlyyWj5Wjitter?WjobWjustܯWWkܮWܰWWWW#Wk-1?Wk-2W?WkeptWknowbWdWeWknowingeWl-4>Wl1)Wl1/lapdm)Wl1/mac/rlc)Wl2WWWWW%WQWWl3WWW%WݘWWlaptopWlatest&W<,chowWWWWWW W WW7WJWeWiWtWWWWWWWWWW&W)W4W@WAWIWWWWWWWhowdoesanmihentitydetermineifapairingrequestfroma VhowdoesregistrationprovideauthorizationtoaccessservicVhowdoesthelinklayerknowthattheipaddressneedsrenewVhowdoesthemnknowthatitcannotobtainserviceiwouldaVhowpracticalfeasibleislinkpdutransmitstatusindicatio Vhow's%WhoweverWWWWWWWW%W7WFW]W^W_WgWkWlWmWtWwWWWWWWWWWWWW$W)WIW^W_W`WcWpWWWWWWWWWWWWWWW~WWWWWWWWWWWWWWWWWWW=cthesentencebeginningwithsincetheseemstostatethatprVthesentenceisambiguousVthesetoflinklayerparametersisnotspecifiedin7.3.3oVthesourcemihnodemayatmostmaketworetransmissionatte VthestatemachinesaccountforsendingandreceivingmessageVthestatemachinesdonocapturethecaseofunsolicitedmihVthestatedscopeandpurposeof802.21istodefineextensibVthetermsreferencepointreferenceconnectionandlinkareVthetextappearstoindicatethatalinkdetecteventisposbVthetextdoesnotstatethatthelinkgoingdownnotificatioVthetextinthestandardstatesthisstandardmaycontainVtitleisnotdescriptive-Vthetitleisnotdescriptivemoreoversomedescriptionshoul.VthetypeanddescriptionforthehandoverstatusdonotagreVtheirWWvWWthemrWsWWWWWthemselvesWfjsuccessfullyWvWsuchWW&W?WWWWWWWWstWWWWWsuggestrewritingthissectionVsuggesttomove8.2.2toanannexVVsuitableWsummarize7Wsummary,WWsuperset&Wsupplied7WsupportW&W8WWWWWsupportedWWWWWW&WVWWCWDWiWjWsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliWsupportingWsupportsWsupposedW7WGWswitchWswitchlocationofremotemihfandremotelowerlayersinfiVsymmetricalWsyntaxWsystemWUWt'WtableWWW=WXWWWWW3W8WPWQWWtablesWWWtagSWWtakeWwW}Wtakealookwhatother802standardsdoesanddefinethenorVtalking6WgNEWilliams, Michael GF DisapproveGProducer^ Technical_105a7.4.19cn MIH. e.g. - make some; if not all, of the QoS examples of Annex K and related material normative.vAQOS is an important aspect of MIH and thats why MIH provides useful tools in the form of primitives and events in order to make use of measurements available at layers 1 & 2. The value of the MIH is not in defining new measurements in other technologies but in facilitating the exchange of information available. While the tools provided by MIH are all normative, the measurements available in other specifications are informative. wDisagreeydeferred. Ref Cmt 590{l) none needed 2007/12/1409/16/2007 17:47:09 EDTNo EWilliams, Michael GF DisapproveGProducer^ Technical_105a7.4.19c7.4.19critical aspect of MIH, but there are very few normative requirements regarding the use of QoS measures and their uses.d588g5014Oc38-52W39-65W3gW3glinkW6WWW3gppWWW'W4W6W7W:WWWWWWWW3gpp-based'W7W3gpp/3gpp2W3gpp2WWWWWWW4WWW3WFWJWWtWW W4-55W40bW40000NW4068^WcW41W433W45RW47W5WtWWWW"W#W$W5.4.3W5.6.1>W52W6$WW6.0WW6.2.1W*W6.2.3W6.3.2W6.3.2shouldbemovedafter6.3.3discussionV6.3.3W6.5.5WW6W6.5.5.1=W6.7W64WXWRW65535W7WWWW7-45W7.0W7.3.10.1 W7.3.3W7.3.6W7.4.19qW7.4.23W7.4.23.2W7.4.5.2.2W7.4.5.2.2theparameterresponselinkeventlistinmihevenV8WWWWHWWWWW&EJeffree, Anthony AF DisapproveGGeneral Interest^ EditorialcIt would be useful if, when you generate the PDF, you were to use the ability of Frame Maker to generate "bookmarks" in the PDF so that the document can be navigated more easily.d248g5354j Add them.{i) to do 2007/12/1209/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveDisapprovet locally through the service primitives of the SAPs that define the interface of the MIHF "Delete ----with the lower layers.---" wDisagreeyDeferred 2007/11/1809/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ EditorialcIt would be useful if, when you generate the PDF, you were to use the ability of Frame Maker to generate "bookmarks" in the PDF so that the document can be navigated more easily.d248g5354j Add them.{i) to do 2007/11/1809/14/2007 08:30:59 EDTMarkedYesEJeffree, Anthony AF Disapprove_5`8a2c'{xENoens, Richard HF DisapproveGProducer^ Technical_31cMIH_NET_SAP defines the interface between an MIHF implementation and various local transport stacks on the same device. It imposes constraints to implementations without any clear benefits.d98g5504jRemove MIH_NET_SAPpduplicate with 105w Supercededy Ref Cmt 105{l) none needed 2007/12/1909/11/2007 17:47:21 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_192`51aB.2.7cAeI do not see a way for a mobile node to use MIIS to determine whether the network supports voice service. The table entry for NETWORK_CAPABILITIES indicates QoS. However, this is not specifying whether QoS is just over the access link--which is insufficient for voice or whether voice service is provided by the network--meaning end-to-end QoS is supported.ed97g5505jClarify the text.the text. Ref Cmt 105 2007/11/1409/11/2007 17:47:21 EDTYesEMyles, Andrew FF Disapproveg5502PECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_103`13a 7.4.17.2.2c9(Kenichi) LINK_ACTION_RSP should be LIST(LINK_ACTION_RSP)d446g5156j change it.wAgree{k) done 2007/12/1909/16/2007 03:35:02 EDTNo o al Interest^ Technical_103`13a 7.4.17.2.2c9(Kenichi) LINK_ACTION_RSP should be LIST(LINK_ACTION_RSP)d446g5156j change it.wAgree{k) done 2007/12/0709/16/2007 03:35:02 EDTMarkedNo description of "Target Link Identifier" to "Specifies the intendend target link of the handover).wAgree 2007/11/1809/16/2007 03:38:14 EDTMarkedYesOECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_111`48a 7.4.20.3.2c(Kenichi) IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address, and IP Address Informaiton Status should be list.d447g5155jXchange those datatype as LIST(datatype). 7.4.20.4.2, 7.4.21.3.2, and 7.4.21.4.2 as well.wAgree 2007/11/183}I ERudolf, MarianF DisapproveGProducer^ Technical_47`2a6.5.2ion" ? For example, in W-CDMA if such an indication is generated each and every time an RLC PDU is successfully delivered, there could several hundreds of these per sec ? Another issue I have is that 7.3.10.1 makes an unnecessary reference to "ARQ module" which is not true for all access technologies. With HSDPA, MAC-hs "(ARQ module) doesn't directly reside below the RLC for example, and not even in the same node network-wise (RLBC in RNC, MAC-hs in Node B). d515g5087jRemove the text about the ARQ mobile. Introduce a mechanism where LINK_PDU_Trasnmit_Status is issues following a certain number of PDU deiveries to reduce signalling load on the internal interfaces.v"Text will be updated appropriatelyw Principle 2007/12/0109/16/2007 13:36:45 EDTMarkedNo ERudolf, MarianF DisapproveGProducer^ Technical_47`2a6.5.2ÃupÃuÃuÃuÃvAndrew F9/176c"It is noteworthy however that there will be no direct communication between the 3GPP2 PHY and MAC layers with the MIHF." "However" is not necessary, but if present should be set off by commas.d553g5049jA"It is noteworthy that there will be no direct communication between the 3GPP2 PHY and MAC layers with the MIHF." or "It is noteworthy, however, that there will be no direct communication between the 3GPP2 PHY and MAC layers with the MIHF." I prefer the first.{k) done 2007/12/1909/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_22`1a5.4.3cThe terms "reference point", "reference connection", and "link" are all used to label or name the same idea in this paragraph. This is very confusing when trying to read it.d552g5050j+Pick a single term and use it consistently.v2Change "Reference Connection" to "Reference Point"w Principle{k) done 2007/12/1909/16/2007 15:56:25 EDTMarkedMarkedcsuggestalternatewordingforimprovedreadabilityandusageVVVVsuggestedWWsuiteWsumWsupportWWWW]WgWWWW2WWsupportedWWWWWWVW]WCWDWyWWWsupportedisqueryparametertypelistshouldnotbeoptionaDVsupportedtransportlistshouldnotbeoptionalCVsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliW1709/16/2007 03:38:14 EDTYes=ECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_111`48a 7.4.20.3.2c(Kenichi) IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address, and IP Address Informaiton Status should be list.d447g3857jXchange those datatype as LIST(datatype). 7.4.20.4.2, 7.4.21.3.2, and 7.4.21.4.2 as well. 2007/09/1709/16/2007 03:35:02 EDTNo>ECheng, Yuu HengF DisapproveGGeneral InterestT(gcprotocol'sBWprotocolsWWprovenWproventWprovideWWWWWWWWWWWWWWWW&W)W*WWWWWWWWprovidedWW7W]WW5WWWWWWprovider>WAWprovidesWWWWWW7WWWWWWprovidingWWWWWEWprovisionWWWpunctuationWpurportedlyWpurposeWWrWsWWW WWWWWWWpurposesWWputWmWqWqosWWW5WFWGW^WkWlWmWWqWWWqosisacriticalaspectofmihbutthereareveryfewnormaVVqoslistisnotalinkparametertypesinglevalueshavebeeGVqualifiersWWqualifies7Wqualify7WWqualityWqW16/2007 03:35:02 EDTNo%lEMeylemans, MarcFApproveGProducer^ Editorial_184`17a Table B-4c7Bad' and 'Poor' signal strength are the same in my mindd381g5221jqChange range 0-24 to 'Poor' and range 25-49 to 'Average', range 50-74 to 'Good' and range '75-100' to 'Excellent'{k) done 2007/12/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_144`3a8.2.1cETypo in 'The algorithm defined&may be used to guild the calculation&'d380g5222jkChange sentence to ' The algorithm defined&may be used to calculate the value of the retransmission timer.'wAgree{k) done 2007/12/1909/16/2007 02:47:09 EDTNo EMeylemans, MarcFApproveGProducer^ Technical_108`20a 7.4.19.4.2cThe 'Requested Resource Set' parameter should be Optional because the 'Query Resource Report Flag' in the request or indication can be True or Falsed379g5223379g5223379g522347:09 EDTMarkedNoEMeylemans, MarcFApproveGProducer EDT cAThe text states that the MIHF demands that the service management procedures of Clause 6 be performed prior to initiating any MIH protocol procedures. However, there are no conformance requirements in Clause 6 for these "service management procedures", I.e., no statement of exactly what procedures *shall* be implemented by a conformant device. Thus, the service management requirement is ambiguous.d15g5587jInclude a formal specification of the required service management procedures, either here or in Clause 6. Include a PICS proforma for these procedures, to ensure that all necessary functions are properly implemented.psuperceded by comment #10v0w Supercededy Ref Cmt 10.{l) none needed 2007/12/1409/03/2007 16:49:33 EDTYes al_143`16a8.1cuffer.d598g4355j correct it 2007/09/1709/16/2007 21:41:08 EDTYes0598g4355j correct it 2007/09/1709/16/2007 21:41:08 EDTYes0d597g4356 2007/09/17W$W*s j=jADelete cases 1, 2, and 3. On page 51, replace "The Length field may be interpreted as follows" by "The 2 LSB of the Type field are used to indicate the number of octets for the size of the Length field." On page 51 Table 9, make the necessary adjustments to reflect that the 2 LSB are not used for IE type/ID. Note: LSB is used to allow more efficient computing to allow the masked LSB to be used as desired numeric value withouth shifting. Subsequently, Annex A Table A-1 needs adjustment of tBhe IE ID values.wDisagree{l) none needed 2007/12/1909/16/2007 06:10:15 EDTYessRDF Data List, Info Response RDF Schema URL and Info Response RDF Schema List) Page 137, Line 19 (i.e., Info Response Binary Data List, Info Response RDF Data List, Info Response RDF Schema URL and Info Response RDF Schema List)IwAgree 2007/11/1809/16/2007 06:10:15 EDTMarkedYes=ELach, Hong-YonF DisapproveGProducer^ Technical_52`1c pcAThe text states that the link up notification is delivered when a layer 2 connection is established on the specified link interface. However, the primitive includes the MAC addresses of the access router, IPRenewal flag and Mobility Management Support. The latter two parameters are clearly above L2 and the L2 link up may not even know about them. The term access router is not defined, but if it is the default gateway (router), then the L2 link up indication would not know about it either.d91g5511jDefine the link up primitive such that it is a L2 primitive that only includes L2 parameters or as an L3 primitive with L3 parameters (ie., provide layer separation).vaThese two parameters are optional and links which dont support these parameters can ignore these.wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYes s EMyles, Andrew FF DisapproveGProducer^ Technical_67`17a7.3.4c$vwillWW WaWWWAWwillingWwireless/W3WWwithWWWWWWWWWWWWWWWW4W5WwWWWWWWW'W@WAW}WWWWWWWWWWWW W Wwithin&W'W^WWWWWWWWWWWWwithinlinkparamtypepg180line10changeqoslistto^VwithoutWAWwordWWwordsWwork WwWworksWwouldWWW&W'WWW)WWWWWWxWyouWzeroW Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145`46a8.2.2.1cE"retransmitted MIH Response is received due to a lot MIH ACK;" "lot"?d567g5035j?"retransmitted MIH Response is received due to a lost MIH ACK;"p servicevPick lower case.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes E Bajko, GaborF DisapproveGProducer^ Editorial_210`57aB.2.7cVValues 65 to 127 are not valid values for IPv6 prefix. Should that be noted somewhere?d126g5476p+changed to "0 - 64, 66-127 for IPv6 subnet"{k) done 2007/12/1909/12/2007 17:25:38 EDTNo E Bajko, GaborF DisapproveGProducer^General_210`43aB.2.7cType name IP_CONFIG_STATUS carries values which are temporary failures, not intended to persist (ie to be solved asap). How would an IS carry up-to-date information of these temporary statuses? If the information is outdated, that may cause trouble.d125g5477it.H jAAttach an explicit statement to line 29 that "When more than one Access Network Container is provided in this IE, they shall be prioritized in the order of preference from the information server's perspective with first Access Network Container as the top priority and with decreasing prority going down the list. This would enable the receiving entity to untilize this information in the same order as provided in this list for network selection or handover decisions."vAAttach an explicit statement to line 29 that "When more than one Access Network Container is provided in this IE, they should be prioritized in the order of preference from the information server's perspective with first Access Network Container as the top priority and with decreasing prority going down the list. This would enable the receiving entity to untilize this information in the same way as provided in this list for network selection or handover decisions."w Principle{k) doneg4994sjnetwork-sideWnetworksWW)WWnewWW W%W3WGWeWWWMWWWnitsBWnmsWWWWW W#WWWnoWWW WW9W]WaWvWWWQWWWWnooctetisencodedforthisdatatypethisdatatypeisuseVnodeWWW+WWWWWnodesW7WnoneWWnormalizedWnormallyWnormativeWWWW WW%W.W9WWWWWWWWWWWWWW WnormativereferencesshouldbeconsideredsuchasthebasesVVnornative9Wsponses). What if more that one remote MIH User exists, which one is responsiB#ble for responding to this request?). What if more that one remote MIH User exists, which one is responsiB#ble for responding to this request?08:31 EDTmcmihprotocolentitiesisnotdefinedandnotappropriateherVmihprotocolheaderisoffixedlengthasindicatedinfig2VVVmihprotocolheaderisoffixedlengthasindicatedinfigurVVmihprotocoltransactionstatediagramsonlyhavesignificanVmihprotocoltransactionstatediagramsonlyhavesomesigniVmihregistrationisstatedtoprovideforauthenticationand)VmihservicesinmobilenodesfacilitateseamlesshandoversbVmih-capableWmih-link-sapWmihfWWWWWWWWWWWWWWWW W"W#W$W?W@WJW]WfWtWwWxWyW~WWWWWWWWWWWWWWWWW W WWW#W$WZW\WWWWWWWWWWWWWWWonlyasourcemihfidanddestinationmihfidtheVF DisapproveGGeneral Interest^ Technical_284`4aKcAThe media dependant native definitions for the MIH common terms and parameters must be normative. Without standardized means to translate parameters from one media to another, the meaning of the MIH terms and parameters will not be understood in a common way.d629g4973jMake the Annex normativepChanged to (normative)vTo make this mapping normative, the 802.11 spec also needs to make this normative in their spec. Just saying that this is normative from 802.21 perspective does not really make sense.wAgree{k) done 2007/12/1909/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^Generalceneralc007 23:32:08 EDTYesEKwak, Joseph AF DisapproveGGeneral Interest^ Technical_284`4aKcoach to use analog parameters to characterize a link.wDeferred 2007/11/0609/16/2007 23:32:08 EDTMarkedYesEKwak, Joseph AF DisapproveJjitisnotclearwhattheintentwasforthischangeperhapsGVitisnoteworthythattherewillbenodirectcommunicationVitsoundsasiftheresponsecontainstheacceptancerathervVitemsWWWitsWWWiWWWW^WcWWWWitselfWWjWW.WWWWj1Wj5WjitterQWjWkWjob WjustWWBWWkWWWW%W5Wk-1QWWk-2WQWWkeptWkindsWknowtWvWwWknowingwWlWl-4PWl1;Wl1/lapdm;Wl1/mac/rlc;Wl2W&W+W-W0W7WcWWWWl3W&W+W7WWWWWWlabelWlanguageWlaptop&Wlatest8WsoallowtheoptionofrequestingVV2nhocommitshouldalsoallowtheoptionofrequestingVVp+cdone7WWdontWdoubleWdownWWWvWW_WWWWdraftW!W&W<W=WWWW%W&W^WcWmWWdrawings WdriftsWdstwWdualWdueWWWW(WduplicateWW WduplicatesWduplicationWduringWWdynamicWdynamicallyWeWWW9W[W]WgWkWlWmWuWwWxWyW~WWWWWWW(W/W3WWWWWWWWWWWWWWWWe-2WeachWWWWWWWWWW WfWWWW}WWWWeachbitofabitmapnvalueVVWelementWWWelementsWWWelemetsWeliminateWeliminatesWelseWWemergencyWemphasise@WemsWenableWW73K#cin[WbWfWgWiWkWlWmWpWvWwWxWyW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWW#W$W%W&W'W/W0W2W5W6WBWEWW#W#W"W#W#W#W#W#W"W#W#W#W#W#WWWWW"W#W#W#WWWWW"W#W#W#WWWWW"W#W#W#WWWWW"W#W#W#W#W#W#W#WWW"W#W#WW#W#W#W#W"W#W#W#W#W#W#W#W#W#W#W#W#W#W8WߕWߝW߬WzvtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWW&W'W,W/W0W1W2W5W6W<W@WDWOWVWWW\W^WaWeWfWiWkWlmtWuWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW W'W(W+W,W0W@WAWEWGW 16:19:39 EDTNoE Golmie, NadaF DisapproveDisapproveby Ref 20, where target PoA is not Link_Tuple_ID. However don't know what's the relation with Link_Detected.wAgree{c) instructions unclear 2007/12/0109/04/2007 16:19:39 EDTMarkedNoE Golmie, NadaF DisapproveTechnical_118PvononceWoneWWWW2WOWWWWonlyWWWWWW&W'WOWuWwWxWyW}WWWWWWWAWWWWWonlyoneofthefollowingparametersshallbespecifiedVonwardsWoperationWoperatorWWWoptimization(Woption8WWoptionalWWfWnWoWJWWorWWWW<W^WkWmWWWWWW WW'WWWWWWWW WorderWWWWWlWmWordering WoriginalWWoriginallykWoriginateWoriginatedWoriginatesWorigination<W6vA"The configuration process is outside the scope of the standard."wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^ Technical_148`12a8.2.2.4cJWhen a time out occurs in RECEIVED state, we should not generate an error.d291g5311j2From line 12 delete text "and generates an error."pWWWWWWWWWWWWWWWWWWWWWess. Alternatively, this information could be removed from Mn_HO_Candidate_Query. 2007/09/1709/16/2007 03:08:31 EDTYesVERajkumar, AjayF GProducer^ Technical_103a7.4.18cWGWXWgWkWlWmWwWxWyWWWWWWWWWWWWWWWWWWWWWWWWWW'W8WNWtWWWWWWWWWWWWWWWWW WstentwithwhattimeintervalmeansVbearerWbecause9WWbecomes%Wjtable10WtablesWWWWtablesk-1andk-2andthecorrespondingtextinannex-kshoVtagSWWtakeWwW}Wtakealookwhatother802standardsdoesanddefinethenorVnts indicated by LINK_PARAM_TYPE for a specific access technology. One example, if LINK_PARAM_TYPE indicates LINK_PARAM_UMTS for use, let's say with RSCP or CPICH_Ec/Io, the 802.21 THRESHOLD sets a value in the range of 0...65535. However, CPICH_RSCP in W-CDMA would be a reported and measured value in the range -120 to -25 dBm (TS 25.133 LINK_PARAM_TYPE indicates LINK_PARAM_UMTS for use, let's say with RSCP or CPICH_Ec/Io, the 802.21 THRESHOLD sets a value in the range of 0...65535. However, CPICH_RSCP in W-CDMA would be a reported and measured value in the range -120 to -25 dBm (TS 25.133d512g4441 2007/09/1709/16/2007 12:18:13 EDTWW W#W$W%W*W+W-W4W5W7W9W:W;W<W@WHWIWJWLWTW/ jlinkWWWW0W?WCWDWEWJWKWLWMWNW^WbWcWeWhWkWlWmWtWvWwWzW{W|W}WWWWWWWWW%W+W,W2W7W8WLWQWXWZW\WhWnWoWsWvWWWWWWWWWWWWWWW WlinksacnlinkscanVlink-idWV^Vr^V^V^V^V^V^V^V^Vter^V^V^V^V^VeWcontrolIWcorrectWLWMWcorrespondingly'Wcos Wcosisnotincludedinlistofabbreviations VcouldQWcount Wcounter Wcounterpart,Wcounters Wcritical7W9Wcuriously WcurrentWcurrently/WdataWW WWWW.WBWCWRWdatatypeWdatatype1CWdatatype2CWdcdWdecides,WdecisionWW&Ws.pbeWbecause^WWWWWWbeenW(WW WWbeforeWbehavioursWbetterWWbetweenAWbeyondWbibliography9Wbit2WbitmapWbody/WbogusWbothWbreak WbroadcastWbrokenWWWWWWauthenticated state. This has been discussed extensively in the group over a long period of time. it is up to deployment to decide how much information they make available in the un-authenticated state.5wDisagree 2007/11/2609/14/2007 16:50:16 EDTMarkedYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_26`26a5.5.3cSThe 802.11 architecture is missing the 802.1X Authenticator port control component.d274g5328jUpdate the Diagram and description to include the 802.11 Authenticator in consideration. The MIH_NET_SAP should go this interface.a6.5.2c46 EDTYesgJEWilliams, Michael GF DisapproveGProducer^ Technical_77c}Link_Scan.response specifies MAC_ADDRESS (in Scan Response Set) Scan can be performed for network types without MAC_ADDrESSESd586g5016j"change from MAC_ADRESS to LINK_ID.pSChanged in Link_Action. Need to change the LINK_SCAN_RSP data type content. Annex 1v'change from MAC_ADDRESS to LINK_ADDRESSw Principle{k) done 2007/12/1909/16/2007 16:08:43 EDTourceeportFlag is NOT a list. OK to keep itwDisagree{l) none needed 2007/12/0709/16/2007 16:08:43 EDTMarkedYes EWilliams, Michael GF DisapproveGProducer^ Technical_77c}Link_Scan.response specifies MAC_ADDRESS (in Scan Response Set) Scan can be performed for network types without MAC_ADDrESSESd586g5016j"change from MAC_ADRESS to LINK_ID.pSChanged in Link_Action. Need to change the LINK_SCAN_RSP data type content. Annex 1v'change from MAC_ADDRESS to LINK_ADDRESSw Principle{k) done 2007/12/0709/16/2007 16:08:43 EDTbE Cypher, DavidF DisapproveGGeneral Interest^ Technical_83`29a74222cAThe text include "local MIHF", however the registration is between a local and remote MIHF. How then can it be the local MIHF? There seems to be some confusion on whether the local and remote MIHFs are paired or whether the MIHF user is registered with its local or remote MIHF.d137g5465jClarify the function of the Register feature (i.e., does it pair local and remote MIHFs or does it pair MIHF Users with local or remote MIHFs?)The text include "local MIHF", however the registration is between a local and remote MIHF. How then can it be the local MIHF? There seems to be some confusion on whether the local and remote MIHFs are paired or whether the MIHF user is registered with its local or remote MIHF.d137g5465jClarify the function of the Register feature (i.e., does it pair local and remote MIHFs or does it pair MIHF Users with local or remote MIHFs?)13/2007 13:56:26 EDTWcBThere's a period missing at the end of "...on the specified link".d67g5535j%Change to "...on the specified link."wAgree{k) done 2007/12/1909/11/2007 11:56:53 EDTNo o ng of link parametersd282g5320jReplace line 8 by text "This primitive is used by the MIHF to configure thresholds and/or specify the time interval between periodic reports for the Link_Parameters_Report indication."wAgree 2007/12/0109/14/2007 18:36:55 EDTMarkedNoE Julka, VibhorF DisapproveGProducer^ Technical_65`49a 7.3.2.2.2cs_Report indication."wAgree 2007/11/1809/14/2007 18:36:55 EDTMarkedNoE Julka, VibhorF DisapproveGProducer^ Technical_65`49a 7.3.2.2.2c or a MIH Responsed286g5316jaOn line 34 replace text "&for an MIH ACK message" with "&for an MIH ACK or MIH Response message." 2007/10/0709/14/2007 18:36:55 EDTYeslka, VibhorF DisapproveGProducer^ Technical_144`15jdiscoverWWWWCWDWdiscoveredbWdiscoveryWWWWWWWWWdiscriptor2Wdiscuss᪃WWWWWdiscussandadopt21-07-0317-00-0000-sinformationieVdiscusscontribution21-07-0315-00-0000-dinformationsupporVdiscusscontribution21-07-0316-00-0000-mcapabilitydiscoveVdiscussspecificsolutionaspectsforbothforsingleradio/Vdiscussion<WhWWWWWdistinguish/Wdistinguishbetweenbasicw-cdmafeaturesbutremoveanyref/VdoW W&W8W?WiWWWWdocW2W6WdocumentWW&WiWxWWWWdoesn't&W]WwWWdoing(Wdone)WdownWW2WaWWdowngrade&WdraftW W'WWWWWWWMWdrawinggWdrivenwWdstwWdueW%WduplicateWduringbWWbcofWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWW%W&W'W*W+W.W2W5W6W7W<W=W?WFWGWIWKWLWMWNWRWZW[W\W^WfWiWkWlWmWnWoWuWvWwW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWW@EEmmelmann, MarcF DisapproveGAcademic^ Editorial_60`58a7.2.2.1c4Rows should be grouped / sorted by service category.d54g5548jRe-order rows of Table 10wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTMarkedIH_NET_SAP ?d55g5547jA\If a mapping of 802.21 service primitives to a specific technology is provided, it should be complete. Either delete all references to a specific technology until a complete mapping is done by the corresponding group (and then add a corresponding annex as an amandment to 802.21) or indicate that there is no mapping for certain service primitives.\v&The MIH_NET_SAP is not media dependentw Principle{l) none needed 2007/12/0709/10/2007 07:08:58 EDTMarkedYes EEmmelmann, MarcF DisapproveGAcademic^ Editorial_60`58a7.2.2.1c4Rows should be grouped / sorted by service category.d54g5548jRe-order rows of Table 10wAgree{k) done 2007/12/0709/10/2007 07:08:58 EDTMarkedWBcexamplequeryshouldbeforbinarydatainsteadoftlvZVwWwWwWwWwWwWWWW"W#W&W.W9W;WvWwWwWwWwWwWwWWvWwWwWwWwWwWWWW"W#W&W.W9W;WvWwWwWwWwWwWwWwWvWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWemihfidanddestinationmihfidthe6VmihftransactionacombinationofanmihfrequestorindicatyVmihfsgWWWWWmiisVW4W:WIWrW$W-W/W5WmikiWmillisecondsYWmimeߍWWWWmimo/ofdmߦWminWWWmincardinalityWmindWminimal?WminimiseߴWminimizesXWminimumߝW߮WBWpjchange27to29and26to28uVchangeatoan|VchangeairinterfacewithmediumVchangeapstoessorbssVchangecurrentlinktosourcelinkforboththenameanddeszV{VchangecurrenttoeithersourceortargetforbotthenameaVVchangedescriptionofsourcelinkidentifiertospecifiesthKVLVMVNVneeded to map the server addresses to the IP configuration methods since not all will be present)jO WvthisWWW WW W&W(W+W,W8W@WAWctness, either a Link_Down or Link_Event_Rollback.indication can be received prior to time expiry.d283g5319j]Replace sentence "If Link_Down is NOT&." with " If Link_Down or Link_Event_Rollback is NOT&." 2007/11/1309/14/2007 18:36:55 EDTNoE Julka, Vibhormessage by the destination MIHF. If the MIH protocol message or the acknowledgement to that message (either MIH ACK message or the MIH prBBotocol response message with ACK-Rsp bit set) is lost, the ACK..."0 2007/11/1309/14/2007 18:36:55 EDTYesE Julka, VibhorF DisapproveGProducer^ Technical_69`26a7.3.6.3ckFor correctness, either a Link_Down or Link_Event_Rollback.indication can be received prior to time expiry.d283g5319j]Replace sentence "If Link_Down is NOT&." with " If Link_Down or Link_Event_Rollback is NOT&." 2007/11/1309/14/2007 18:36:55 EDTNoE Julka, VibhorjprovideagenericcontainerthatwillallowaccesstechnologVprovidearequirementthattheprotocolbeimplementedtogetVWWWWWWWWWWWWWWWWWWW!WWWWWW!WWWWWWWWWWWWWWWWWWWWWWWW!WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWc_Ã$ LM⊃Ã$0JK≃⏃Ã$@ۃÃ$PÃ$Ã$⿃Ã$~Ã%ፃÃ% eWeWeWveeWeWveeWeWthebestwaystinvoked WinvokesWinvolveeWeWߝWWWWW W.Wip-basedߞWߢWipaddressinformationWWipconfigurationmethoWis W(W)W8W:WBWCWDWEWFWIWNW\WaWcWkWwW߁W߂W߃W߇W߉WߊWߍWߏWߒWߝWߞWߟWߠWߧW߮WߴW߶W߹W߾WWWWWWWWWWWWWWWWW WWWWW'W;W>WCWEWHWIWJWKWMWNWOWPWTWUW[W\W]W^W`WiWjWkWlWWWWWWWWWWWWWW)W*W5W;W?WNWQW_WWofERajkumar, AjayF GProducer^ Technical_80`5051cAIf the intent is for two MIHFs to mutually discover each others capabilities then shouldn't the request include the same data that is in the response? Missing LinkMACs and MbbHandoverSupport. Also, why is event and command not optional on the response yet it is optional on the request. With all of the optional parameters, asymmetric request/response, and allowing MIH User(s) to specify MIHF capabilities it is unclear as to this primitives usefullness.d424g5178discover each others capabilities then shouldn't the request include the same data that is in the response? Missing LinkMACs and MbbHandoverSupport. Also, why is event and command not optional on the response yet it is optional on the request. With all of the optional parameters, asymmetric request/response, and allowing MIH User(s) to specify MIHF capabilities it is unclear as to this primitives usefullness.d424g5178rkedYesqccurrentlinkidentifieWcurrentlyWWWTWVWcwgWd5WNWdangerWVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVjVhViVjVjVjVjVjVjVjVjVjVjVjVjVjVpcstatedW)WWWWstatefulWstatelessWstatementpWWWWWW WWstatementsWWWstateseWrWsWtWWWWWWWWWJWqWWWWWWWWWWWWWWWWstatesthatanmihusermustgeneratearesponsetotheinditVstatesthatitmayindicatethatthemnmayhavestartedahVstatesthatitpreparesresourceforhandoverthisisjustarVsVstaticWstating?WWstationWstationary%Wng with respect to the description of page 30 and 31.d506g4447jI suggest to replace the 802.3&3GPP2 boxes in Figure 11 by these SAPs. Consider to move text describing mapping of LINK_SAP to access-specific SAPs from Section 7.1 page 59 here. 2007/09/1709/16/2007 12:18:13 EDTNoߌEFamolari, DavidFApprove4448 2007/09/1709/16/2007 10:24:17 EDTBjreadWrealization'Wrealized(WreasonWreceiptWWreceiveWreceivedWW~WWWWWWWWreceiverIWreceivingWWWjWtWreceiving/sendingWrecipientWWWWrecommend&W5WWWWrecommendre-writingclause5muchlikethatwrittenforieeV.WconceptsWconcernedWconcerningWWconcurrently:WconditionskW'WWconfidence%WconfigWconfigurable߅WconfigurationWWWWWWWaWconfigurationofthemihfisnotspecifiedinthisstandardaVconfigurations߅WconfiguremWconfigured,WconfiguringWconfirmߌWconfirmationWconflicting/overlappWconfusedWconfusing]WmWnWߛWWWWWW*W-WWWconjunction߮WconnectߧWconnected)W:WconnectingW3g5333jRecommend re-writing Clause 5 much like that written for IEEE 802.11. This Clause should be very precise in its scope, and should be the "executive summary" of functions defined in this standardwDisagreey deferred.{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYes she 802.21-PAR: "This standard defines extensible 802 media access independent mechanisms that enable the optimization of handover between heterogeneous 802 systems and may facilitate handovBer between 802 systems and cellular systems". Link switch that takes place between PoAs in the same access network is thus out-of-scope. The definition of handover (definition 3.3) is based on this definition of link switch.d75g5527j;Change the definition to be consistent with the 802.21 PAR.v57a3chus the text is confusing and misleading--the reader cannot determine what 802.21 is really trying to accomplish.Vs really trying to accomplish.V'cmishopWmisleadWWWmissingWW&W+W-WYWfWWWWmissingbracketinunsignedint2VmisusedWmlmeWWWmlmesapc-sapmih3glinksaplsapcssaparenotshowninfVmnWWWWWWW&W0WJWKWLWMWNWdWeWiWuWvWwW}W~WWWWWWmobileWWWWmobility7WWmodelWmodelsWmodule WmoreWWWWWW&W=W]WgWnWoWmoreoverWWmostWW WmostlyWmoveW WWmovereferencesbibliographytosection2normativereferenc Vmoved*WWmovementWmpduWmpdusWms/WmsduWmuchWWWmultipleWW[WmustWWWWWWWWWW&W'W5W7WkWlWmWtWvWWU cnotnotably7WnoteWWWWWWW/WWnoteforanetworkentitycomprisingofmultipleinterfacesVnotethisreferstopageiiiline35michaelhoghooghishoulVnotedWnoteworthyWnothingW0W6Wnotification`WWWWnotifiedWWnotionW5Wnoun{WnowWFW^WWWWnsapWnumberWWWkWlWmWWqWuW W WWWnumberedWWnumbersWWWWWuWWnumerousWWnwWobjectivesWobjectsWobtainWWWWobtainableWWobtainedWWobtainingWobvious&WoccurWFWoccurredWWoccurrenceWoccursWWWoctectW~WWoctectstring~VVoctetWWWW WoctetsW=WuWWWWWWWWW;a7.3.5.237.3.67.3.6.27.3.6.37.3.8ᭃ7.3.97.3.9.17.3.9.27.4.1]7.4.1.1.2ރ߃7.4.1.1.37.4.1.3.1CD7.4.12.1.2◃17.4.17Q4.17QQ17QQ4.17QQ17QQ7.4.17QQn can be requested at the recipient of MIH_N2N_HO_Commit. 2007/09/1709/12/2007 02:37:36 EDTYes to move 8.2.2 to an annex 2007/09/1709/12/2007 02:37:36 EDTNoEEastwood, Lester FF DisapproveGProducer^ Technicala7.4.24cMIH_N2N_HO_Commit does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d115g4838jcadd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit. 2007/09/1709/12/2007 02:37:36 EDTYesO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit. 2007/09/1709/12/2007 02:37:36 EDTYesd114g4839 2007/09/17jnsapWnumberWWW W=WkWlWmW W Wnumbertheentitiesinfigure2accordingtotheliststartiVnumberedWnumbersWWWWoccurrencesWoctetWWWoctetsW=WHWWofWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW"W#W$W&W'W(W+W,W0W3W4W5W6W7W;W<W=W>W?WBWCWIWKWLWMWNWXW]W^W`WbWdWiWkWlWmWvWwW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW9lproduceruser⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃ out the link actions then how does the MIH User get the status so that it can create the appropriate response.Md410g3894jAThat the MIH User upon receiving the Net_HO_Commit.indication, issues the appropriate primitives to carry out the actions specified in the request (i.e. issues MIH_Link_Action primitive). Upon completion, the MIH User constructs the appropriate response and issues a Net_HO_Commit.response. Note: somehow the MIHF needs to know that the actions are in response to a handover request otherwise, it would not know to issue the handover imminent/complete events.otherwise, it would not know to issue the handover imminent/complete events.{rcbesides[WWbestWWbetter$WWWBWWWbetterwordingisrecommenedforasimilarmechanismmaybeVbetweenWWWWWWWWWWWWW>WAWBWIWJWWWWWWWWWW W WWWWWW#W$W(WaWWWWWVYVYVYVYVYVYVYVerestofthe=V?VWVXVYVYVYVconsistencytotherestofthe=V?VWVXVYVYVYVYVYVYVYVYVYVYVYVYVW}W~W܀W܁W܄W܅W܈WܕWܗWܘWܚWܜWܞWܤWܨWܬWܭWܮWܰWܴWܸWWWWWWWWWWWWWWWWW"W*W8W9W:W;W<WSWYWZW[W_WW݇WݎWݐWݓWes݉WpE Sood, KapilF DisapproveGGeneral Interest^ Technical_13`39a5.1.7cA3"MIH events, commands and information service message exchanges between an MN (Mobile Node) and a network PoA (Point of Attachment) cannot be secured until the MN has a secure connection with the network PoA." - this sentence sounds self-filfulling. Yes - you need security before something can be secured. 3d271g5331jThis sentence be re-written to better specify what security properties need to be addressed. If none have been specified, then delete this 5.1.7 clause, and be added by future security work.psuperceded by 300, 471vby 471. Sub Clause deleted.w Principley Ref Cmt 471{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYes s rceded by 300, 471vby 471. Sub Clause deleted.w Principley Ref Cmt 471{l) none needed 2007/11/2609/14/2007 16:50:16 EDTMarkedYes if it is only a "desirable goal".wDisagree 2007/11/18 2007/11/14Yes[caadescriptionoftheavailableoptionsforwhichtransportp+Vageneralcommentrelatedtoevent-subscriptionlink-detectVaone-octetselectorfieldfollowedbyavariablelengthvalVapointofattachmentpoabeingevaluatedforswitchingtheVarequest-responsemechanismwillnotscaletoaccommodatelVWaboutWWWWWW<WgWvWaboveWFWJWabritrary1Wabsence6Wabsenceofamedia-dependentsapforgsm/egprsthereisonly6VabsoluteWabstractWabstractionsWacWaccessWWWW W WWWW&W1W5W6WOWWWWaccessibleuWaccommodateWaccordingWWW"W#WKWLWMWNWaccordingtotableb-2page176networkerrorisindicatedbVaccount~WWackWWWWackfailureisnotrelatedtoplrackfailureisatransmitV/cthereWWWWWWWWWWWWWW W W W WWWWW'W/W6W8WJW[W\W_WaWiWkWlWmWrWsWWWWWWWWWWWWWWWW%W'W(W+W,W5W8WKWLWWWXWYWZW\WbWeWfWmWoWpWsWWWWWWWWWWWWWWWWWWWWWWW WWthereareanumberofsapprimitivedefinitionsinthespeciVsapsiemihlinksapandmihVtherearetwoplaceswherethemihlinkupisusedneitheroZV\Vthereareveryfew8shallsinsection6.0mihfservicesandVthereisabitofadichotomyinthedefinitionofthisprimVthereisalackofapositivepredictivelinkeventlinkgoi,VWinternal3WcdecisionsWWWWWWW'WWdecoding=WdecreasingWWWdedicatedWdeduced WdefaultW:W;WWdefineWWWWWWWWttheyVdefinedWWWWWWWWWWWWWWWWWW1W6WFWUWVWiWWWWWWWWWWWdefined&mayWdefinesWWWWWdefiningWWdefinitionWWWWW W?WWWWWWWdefinitionfornetworksecurityismissingVdefinitionoflinkacresultcodedoesnothaveavalidrangVdefinition/specifica<WdefinitionsWWWWWWdefintion"W#WdegreesWdelayWdelaysWdeleteWWWWWWdeleteannexfasitisredundantandnotrequiredinthespVWV^cisWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWWWW!W"W$W%W(W)W+W,W-W.W0W5W8W:W;W<W=W@WAWBWDWFWIWJWKWLWNWPWWWXWYWZW\W^W_W`WaWbWcWdWeWfWmWoWpWqWrWsWuWwWyWzW{WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWprespondWresponseWOWgWmW WWresponse/confirmnWoWresponsesWresrouces WrestrictWresultWWWreveredWreview WWrevisionAWrevisionsWrfc4066WroamingWWroundWWrouter WOWrowWrspWWsamenWoW{W|WWWWW WtWWWWWWWsameas221Vsameascmt109Vsameascmt351 VVVsameascmt44VVVsapWscanWRWWschema-W4WscopeWWWsectionW#W,W2WQWWWIWOWWsectonRWSWsectonwasdeletedRVSVsecuritymWseeWWWW4Wsee339VVseemWseems(Wselected WsendW WsendingAWWsentWto end of text on line 41 2007/10/0709/14/2007 18:36:55 EDTNo-cmihnethocandidatatequeryrequestshouldcontainonlyqueVmihnetsapandmihlinksapbothspecifyabstractmedia-depVmihnetsapdefinestheinterfacebetweenanmihfimplementaV$VVVmihnetsapisusedtointerfacebetweenthemihfimplementa VmihnetsapspecifiestheinterfacebetweenanmihfimplemenVmihnetsaptriestoprovidedetailsofspecificimplementatVmihnmssapdefinestheinterfacebetweenanmihfimplementaV#VVVmihnmssapisusedtointerfacebetweenanmihfandalocal VmihnmssapspecifiestheinterfacebetweenanmihfimplemenVmihnmssaptriestoprovidedetailsofspecificimplementatVmoreWWWWWWmoreoverWmostWWmoveWmpduWmpdusWmsduWmuchWmultipleWWmustWWWWWWWWWWmutualW jaone-octetselectorfieldfollowedbyavariablelengthvalVa-1=Waaa7WableWabout W6WWWaboveWW&W]WWWWacceptableWacceptancevWaccessWWW WW&W'W0W1W7WbWkWlWmWWWWaccess-specificWaccordingW%WWaccordinglyWaccounteWaccuraciesWachieveWackWWWWWack-rspWW 2007/09/1709/16/2007 03:08:31 EDTYesj messages.d404g3900jIChange "Current Link" to "Source Link" for both the name and description. 2007/09/1709/16/2007 03:08:31 EDTYesiERajkumar, AjayF GProducer^ Technical_121`35cOThe "Current Link Identifier" is inconsistent with the other handover messages.d403g3901jIChange "Current Link" to "Source Link" for both the name and description. 2007/09/1709/16/2007 03:08:31 EDTYesjYesjg3902)QyduplicateWWWWduplicatedWWWWWWWyW!W"W,WWWWWWWWWWWWWW WW#W$Wref238Vrefcmt105VV$Vrefcmt106VV V#Vrefcmt114Vrefcmt35Vrefcmt363Vrefcmt471Vrefcmt497Vrefcmt556VsameWW Wsameas105 Vsee8W{€markedᆃᇃቃኃዃῃ㑃㒃㓃€noƒ %()*+,-./1349:;OPQRST[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⦃⧃⬃⮃ⱃⴃ529`‚Xԃ',JKah‚Y᳃OTⵃÃ㡃㹃㺃㻃㼃‚Z᱃≃Jv‚aكY`nɃ߃‚b57Xl‚c⁃W‚dᕃӃރI|‚e᪃᫃ L׃_u‚f3y‚gể0:‚hE⊃ԃD㐃Âicփ2‚jᦃ^>K㮃݃‚qH\⭃CV㋃㙃‚rᘃj‚sӃ‚tᶃ;‚u[bi⋃㲃‚v_⅃‚nÃ"0qÄ57pÄCDaÄRS`ÄUWeÄVtmÄXYdÄabfÄhvlÄstooo\jintroduce W&W+W3W6W+W,Wintroduceabriefdescriptionofthel2transportprotocola+Vintroducealinkgoinguptypepositivepredictiveevent,Vintroduceamihlinkgoinguptypepositivepredictiveevent+VedandhowtobestimpVinvestigateifthiscapabilityisneededandthebestwaystVinvokedWinvokesjWipW W&WgWkWlWmWip-based'W+WisWWWWWWWWWWWWWWWWW W W WWWWWWW&W'W(W)W0W7W=W?WBWGW]W`WbWfWhWvWwWxWyW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWisn'tWissuetWwWWlatest8W1EEmmelmann, MarcF DisapproveGAcademic^ Technical_49`17a6.5.3c&Emphasize that this is only an exampled51g5551j;Start paragraph with: "As an example, Figure 19 shows ...."wAgree{k) done technology is very beneficial but should be included in a (possible normative) Annex. Second, such a mapping should be structured by "technology" and not by the name of the SAPs.wd52g5550jDelete items a) through e) and move their contents to a (normative) Annex. There should be one Annex per technology containing any technology-specific information which is reqired to make 802.21 work with / adapt to the specific technology.v>Move items [a] through [e] to Annex-L. Make Annex-L normative.wAgree 2007/12/0109/10/2007 07:08:58 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_49`17a6.5.3c&Emphasize that this is only an exampled51g5551j;Start paragraph with: "As an example, Figure 19 shows ...."wAgree{k) done=W>W$u>ELach, Hong-YonF DisapproveGProducer^ Technical_29`22cSub-clause 5.6.1: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d464g5138e necessary adjustments to reflect that the 2 LSB are not used for IE type/ID. Note: LSB is used to allow more efficient computing to allow the masked LSB to be used as desired numeric value withouth shifting. Subsequently, Annex A Table A-1 needs adjustment of tBhe IE ID values.wDisagree 2007/11/2609/16/2007 06:10:15 EDTYes>ELach, Hong-YonF DisapproveGProducer^ Technical_29`22cSub-clause 5.6.1: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d464g5138 indicate the size of the "Length" field, representing 1-4 octets respectively for the size of the "Length" field. The encoding and decoding of such info"CwcpointWWWWW WWWWWpointsWWWpoliciesWpolicyWpoorWpoorlyWWpopulatedWWportWposWWWKWLWMWNWgWuWWWWWW@WUW]WdWWWpos-wlanZW\Wposition WpositionedWs EEastwood, Lester FF DisapproveGProducer^General_316cAnnex M.6 seems redundant and not adding any value, given that similar materials have been covered in the example call flows in Annex H and Information Service examples ind121g4832j remove M.6 2007/09/1709/12/2007 02:37:36 EDTYes EEastwood, Lester FF Disapproveany value, given that similar materials have been covered in the example call flows in Annex H and Information Service examples ind121g4832j remove M.6 2007/09/1709/12/2007 02:37:36 EDTYes EEastwood, Lester FF Disapprove3 2007/09/1709/12/2007 02:37:36 EDTR ctheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWWWWWW W#W$W%W&W'W(W)W*W-W.W/W0W1W2W4W6W:W;W<W@WAWEWFWGWHWIWJWMWNWOWQWTWUWVWYWZW\W^W_W`WcWdWgWiWjWkWlWmWvcwhatWWWWWWW WWW,W.W0W1W?WDWEW]WbWeWnWoWpWvW}WWWWWWWWWWW$W'WdW{WWWWWWWwhatdoescurrentlinkidentifierrefertothesourceortarDVEVwhatdoesitmeanbytransparentinter-workingwithlegacyeVwhatdoesn8ii12meanVwhatdoesthatmeanbymihcommandindication/responseinfiVwhatdoesthisprimitivemaytriggermihusertoinitiatethpVwhatifasourcenodecannotreceiveanyanswerevenitsenVwhatisastackVwhatisexistingandwhatisnewisrelativetothedevelopmVwhatisthedifferencebetweenlink-upandlink-handover-comVwhatisthedifferencebetweenmihposandmihposnetworkeVVwhattypeofauthenticationisreferencedherethereisnosVXcthe802.21specseemstodoagoodjobofdefiningamechaniVtheackmechanismisoptionaltouseandsincethestatediaVtheactualadaptationofthemihlinksapwaspreviouslystaVthearrowinfig23shouldshowthatuponreceiptofmihreqVthebroadcastingofthismessagecannotbeconsumedbyanyoMVthecontentsoftableb-13attemptstodefineaccesstechnolVthecurrentcommandserviceallowsforqueryingofavailable*VthecurrentlinkidentifierisinconsistentwiththeotherhzV{Vthedefaultmimetypevalueisincorrect:V;VthedefinitionofnmsnetworkmanagementsystemisnotdefinVthedescriptioncontainsthisidentifiesthecurrentlinkfoCVVVVthedescriptionofthesourcelinkidentifierandtargetlinKVLVMVNVthedescriptionsforinfoquerybinarydatalistinfoqueryVthedestinationofaneventisestablisheddynamicallydoesVsnotcV lcASince available resources are on a per candidate link basis there must be the same number of entries in the LIST(LINK_POA_LIST) as there are in LIST(QOS_LIST), i.e. there must be a one-to-one relationship. In fact, the IP configuration method and server addresses should also be on a per candidate basis thus they should be lists as well (however, care is needed to map the server addresses to the IP configuration methods since not all will be present)d418g5184jAAdd a statement requiring that the number of entries in each of the lists (LINK_POA_LIST and QOS_LIST) be the same; Combine Preferred Candidate Link List, Available Resource Set, IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address and IP Address Information Status into a single type and return a list of that type; Further, if resources on a candidate are dependent on a particular PoA then all of these parameters need to be on a link and PoA basis.p Done in 417.vB{lnoneneededV\8needednoneTresolution@-to€€noyes@E vmappingEWWWWWmappsWmapsWmarkedWmatchWmatchingWmaximumW'W WmayWWWWW2W<WkWuWwWWWWWWWWW'W(W{WW W WWmbbhandoversupportfWmean2WmeansAWWmeantWmeasurement5WWmeasurementsWW2W5WWmeasurementsavailableintherespectivetechnologiesareno5VmechanismWWWwWWWW}WWWWWWWmihfunctionsisusedinthepluralsenseofmihfunctionVmihnmssaphasbeendeletedVmihfW<W@WiWWWWWmimo/WmissingWmnW2WiWuWwWWW}WWWmnhocommitshouldbeusedonlyasalocalprimitiveandnowVmobileiWmobility<WWmodificationsWmodify/WwWneedWWWIfcbebeaconWWbecause*WRWWWWMWWbecomeWWWWWbecomesWWdWbeen WW,WGWbWuWWWWWWWbeforeW0WeWuWwWWWWW.W|WWWWbeginvWbeginningWWWWbehalfWWbehaviorWMWWbehindWbehooves&WbeingWW W7W[WWWWWWbelieveWWWWFWbelievedWbelongWbelow WbeneficialWWWbenefitWW#WWbenefitsWW$WWWWrecommenedforasimilarmechanismmaybeVbetweenWWWWWWWWWWWWW>WAWBWIWJWWWWWWWWWW W WWWWWW#W$W(WaWWWWWkadathurWWWWWWWWWkapilWWWWWWWWWWWWWkarlWWWWWWWWWkarockiWWkarockipiotrVVkevinWkiernanWkiernanbriangVkimWWWWWWWWWWWWWkimeunahVVVVkimyonghoVVVVVVVVVkoh&W'W(W)W*W+W,Wkohbenjamin&V'V(V)V*V+V,VkwakWWWWWWWWWWkwakjosephaVVVVVVVVVVlEWFWGWHWlach<W=W>W?W@WAWBWlachhong-yon<V=V>V?V@VAVBVleeuwenWWlesterWWWWWWWWWWWWWWWWWW &jCA2.11 crd in it, in order to claim 802.21 compliance, it must have XYZ. Could do this per access technology and 802.21 complaince overall is determined as a superset of the individual per access requirement. If this comment cannot be resolved, I would recommend to downgrade 802.21 to a Recommended Practice document only.vAA Protocol Implementation Conformance Statement (PICS) Proforma cannot contain any information that is not already present in normative text. Therefore including a PICS Proforma would be redundant. Duplication of information within a standard has a tendency to cause inconsistencies. A PICS Proforma covers only conformance, not interoperability. Clause 8 describes the formats of messages used to exchange information. The description of when these messages are used are defined in claB-use 7 since they are triggered by primitives.wDisagreeyRef Cmt 10. (superceded){l) none needed 2007/12/1909/16/2007 07:13:12 EDTYes ijmanualWmap5WWmappedWWmappingWWWWWtWWWmappingsW5WmapsWmarkWW>W?Wmarkipaddressinformationoptional>Vmarkipconfigurationmethoandipaddressinformationoptional?VmarkedWWWW!W"WWWmasked=WmatchWWWLWXWmaterialWWEWMWmaxWmaximumWWmaximumdataratein802.11termsisthehighestavailablebVlseWWWelsewhere܆WenableܟWܠWWWencodeݲWencodedܹWܺWܻWܼWencodingܺWWencrypt%Wend%WݢWWWWW"W+WގWendingWendoݽWenhancedWenhancementsWensureWWWWensuringWentire;WfWentirelyW'WentiresWWentitiesܫWWWWWW0WݟWދWt@@@@@@ial_153`14a8.6cIt is very difficult to cross-reference the sections where TLV items are defined from where they are specified in the protocol messages.d322g5280jxIn the tables that define protocol messages. Include a reference to a clause where the data type, list, etc. is defined. 2007/10/0709/14/2007 23:15:41 EDTYesbWWWWWWWWWWWWWWWWstatethatdiscoveryofmihposoverl3isoutofscopeofiVVVthatdiscoveryofmihposoverl3isoutofscopeofiVVVVVVVVVVVofiVVVVVstatedKWKWKWKWKWKWatedKWKWKWKWKWKWKWKWKWKWKWKWdKWKWKWKWKWKWKWKWKWKWKWKWKWKW5 EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_79`5a 7.4.1.1.2c%"List of supported MIIS query types."d559g5043j7"List of supported MIIS query types on the local MIHF."wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes s lin, Clint FF DisapproveGGeneral Interest^ Editorial_79`5a 7.4.1.1.2c%"List of supported MIIS query types."d559g5043j7"List of supported MIIS query types on the local MIHF."wAgree{k) done 2007/12/0709/16/2007 15:56:25 EDTMarkedYes iscovery of each other's capabilities."{k) done 2007/12/0109/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_79`8a 7.4.1.1.2c$"List of supported transport types."d560g5042j6"List of supported transport types on the local MIHF."{k) done 2007/12/0109/16/2007 15:56:25 EDTYesClint FF DisapproveGGeneral Interest^ Editorial_79`8a 7.4.1.1.21.1.2+  cAHow practical / feasible is "Link_PDU_Transmit_Status.indication" ? For example, in W-CDMA if such an indication is generated each and every time an RLC PDU is successfully delivered, there could several hundreds of these per sec ? Another issue I have is that 7.3.10.1 makes an unnecessary reference to "ARQ module" which is not true for all access technologies. With HSDPA, MAC-hs "(ARQ module) doesn't directly reside below the RLC for example, and not even in the same node network-wise (RLBC in RNC, MAC-hs in Node B). d515g5087jRemove the text about the ARQ mobile. Introduce a mechanism where LINK_PDU_Trasnmit_Status is issues following a certain number of PDU deiveries to reduce signalling load on the internal interfaces.p- removed mentioning of ARQ - emphasized that the user has full control over the amount of indications it receives. The indications are only generated with subscription.v"Text will be updated appropriatelyw Principle{k) done 2007/12/19VjcdefinelinksynchronouseventsratherthansayingwhattheyVdefinedWWWWWWWWWWWWWWWWWW1W6WFWUWVWiWWWWWWWWWWWWWW WWWTWVWpWWWWWWWWWWWWWWdefined&mayWdefinesWWWWW#W$WWWWWWWWdefiningWWWdefinitionWWWWW W?WWWWWWWWWWWqWWWWWWWWWalidrangVdefinition/specifica<WdefinitionsWWWWWWWmWdefintion"W#WdegreesWdelayWdelaysWdeleteWWWWWWdeleteannexfasitisredundantandnotrequiredinthespV{,creferencetowrongmessageVVsubscribertosetceVmihn2nhocommitdoesnotallowtheoptionofrequestingreVVcommitdoesnotallowtheoptionofrequestingre VVVcommitdoesnotallowtheoptionofrequestingre VVVmihn2nhocommitshouldalsoallowtheoptionofrequestingV2nhocommitshouldalsoallowtheoptionofrequestingVVV2nhocommitshouldalsoallowtheoptionofrequestingVVallowtheoptionofrequestingVV2nhocommitshouldalsoallowtheoptionofrequestingVV2nhocommitshouldalsoallowtheoptionofrequestingVV2nhocommitshouldalsoallowtheoptionofrequestingVVVV2nhocommitshouldalsoallowtheoptionofrequestingVV2nhocommitshouldalsoallowtheoptionofrequestingVV2nhocommitshouldalsoallowtheoptionofrequestingVVW.ctechnologyWWWWWrest^ Editorial_111`16a 7.4.20.3.2c6Font of parameters in list needs to be made consistentd526g4427ypes? If not, then maybe a linkType should be added along with COS_ID to clarify the class of service identifier explicitly for that link typed527g4426jClarify if COS-ID are consistently represented across all links or are they on a per link basis. If on a per link basis add, the linkType to COS_ID. 2007/09/1709/16/2007 13:58:33 EDTYeswE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_111`16a 7.4.20.3.2c6Font of parameters in list needs to be made consistentd526g4427s add, the linkType to COS_ID. 2007/09/1709/16/2007 13:58:33 EDTYeswE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_111`16a 7.4.20.3.2c6Font of parameters in list needs to be made consistentd526g4427 2007/09/1709/16/2007 13:58:33 EDTYesT5creliable@replacement@orequired@reserve@reserved@Cresponse@responses@eresult@routers@saps@se@seemstobeanextraneousline@,server@shall@shouldbemovedafter6.3.3discussion@signal@single@ethemobili@Oesareonapercandidatelinkbasisbasisavailableresourcesareonapercandidatelinkbasisctableb-8supportedlcpvalueswaspresentinversion6.0Vtableb-9shouldalsoincludepoalocationinformationsuchVtablek-2doesnotprovideaverycomprehensivemappingbetwVtablesWWWWtakeWWtakenWtakesWWtaleWtalkingWtalksWtargetWWWWDWEWJWKWLWMWNWpW|WWWWWWW WUWWWWWtargetpoaisalreadyincludedintargetlinkidentifierthiVVtargetpoaisdefinedaslinkidinnethocommitsappage1Vtargetpoaisredundantasitcouldbeincludedinthetarge|VtargetpoaWWtcp/ipW&W'Wtechnically7W@WtechnolgyWtechnologieWtechnologiesWW W WWW&W'W1W6W7WWWWWWtechnologyWW5WWWWWWWWWWWWXpgroup disagrees with commentwDisagree{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Editorial_60`30a7.2cThere are a number of SAP primitive definitions in the specification and it is difficult to find the details of a primitive definition in the spec given that it is over 300 pages. This applies to all of clause 7.d317g5285jAAdd a column which includes the reference to the clause where the primitive is defined and if possible, a reference to other pertinent normative information. An example of one of these tables is Table 12 on page 62. Include similar changes to clause 7.3 - 7.6pOalso re-ordered some primitive definitions in 7 to match the order in the table{k) done 2007/12/1909/14/2007 23:15:41 EDTYes s s will not scale to accommodate large numbers of MIH-capable mobile nodes.d324g5278 2007/09/1709/14/2007 23:15:41 EDTYes 1cAThe text states the definition of link switch as, "The process by which a mobile node changes the link that connects it to the network. Changing link implies changing the remote link endpoint and therefore the point of attachment of the mobile node." By definition, this is out-of-scope for 802.21; from the 802.21-PAR: "This standard defines extensible 802 media access independent mechanisms that enable the optimization of handover between heterogeneous 802 systems and may facilitate handovBer between 802 systems and cellular systems". Link switch that takes place between PoAs in the same access network is thus out-of-scope. The definition of handover (definition 3.3) is based on this definition of link switch.d75g5527j;Change the definition to be consistent with the 802.21 PAR.v57a3cGPP2 one line below 2007/09/1709/16/2007 07:13:12 EDTNo߲w 2007/09/1709/16/2007 07:13:12 EDTNo߲d467g4486 2007/09/1709/16/2007 07:13:12 EDT%Yes FF DisapproveGGeneral Interest^ Technical_174`26field. The Selector value determines the data type. If Selector==i, (i+1)-th data type in the list of data types DATATYPE1,DATATYPE2,[,&] is selected. The Value field is encoded using the encoding rule for the selected data type." What is the binary encoding of the selector octet? Order ov value? Increasing order or decreasing order?d578g5024jAj"A one-octet Selector field, followed by a variable length Value field. The Selector value determines the data type. If Selector==i, (i+1)-th data type in the list of data types DATATYPE1,DATATYPE2,[,&] is selected. The Selector field is encoded in increasing order of significance. The Value field is encoded using the encoding rule for the selected data type."jv# Plesae refer to 21-07-0396-01-0000w Principle 2007/12/0709/16/2007 15:56:25 EDTMarkedYes EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_174`26W07EOhba, YoshihiroF DisapproveGProducer^ Technical_178`51aB.2.4cHLINK_ID should be LINK_TUPLE_ID to allow connecting to a specific PoA? .d215g5387jMChange LINK_ID to LINK_TUPLE_ID (specifically for Link Action primitive only)wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes 8EOhba, YoshihiroF DisapproveGProducer^ Technical_178`29aB.2.4c=There is no action type to perform intra-technology handover.d214g5388jAdd the following LINK_ACTION_TYPE: "LINK_HANDOVER". Also, add the following entry to Table B-5: "LINIK_HANDOVER | Cause an intra-technology handover on the specified link. A target PoA may be specified as well."v+At the link layer this option is not valid.wDisagree{l) none needed 2007/12/1909/13/2007 16:03:47 EDTYes s s tion primitive only)wAgree{k) done 2007/11/2609/13/2007 16:03:47 EDTMarkedYesest^ Technical_297`8aM.1ical_297`8aM.1007 03:35:02 EDTdfjchangetoarrivefromthemac-wlan`VchangetoforvariousparametersVchangetofunctionalentitiesshalldiscardanyreceivedieVVchangetoifacontainerislistedVchangetointernetprotocolipVchangetoipaddressofposVchangetolayer3handoverVchangetolinkidvVchangetomichaelhoghooghiVchangetomihlinkconfigureparametersoVchangetomihlinkconfigurethresholdstomatchclause8.6.LVXVchangetomihmnhocommitindication[Vchangetomihn2nhoqueryresourcesKVchangetonetworkmanagementsystemVchangetoonthespecifiedlinkVchangetothefollowinghandoverflowrefersV7palltheoccurrenciesofmihinformationwaschangedasmihgOVallowWWalreadyWWWalreadydonein615Valso WRW{W|WWqWWWalsomadethesamechangeinindicationandthemessage{V|Valsore-orderedsomeprimitivedefinitionsin7tomatchtheVamount WanWWWWWW WAWWanmnanmihanhifarecorrectVanmnmayaccessinformationservicesfromanmihentityinVanoptionaltypeextensionfieldisaddedtotableb-12undeVandWWW(WOW^WmW{W|WWW WWWWW:24:47 EDTMarkedYes+E Koh, BenjaminF DisapproveGProducer^General_40a6.3.5cEThere is a lack of a positive predictive MIH event MIH_Link_Going_Up.d227g5375j?Introduce a "MIH_Link_Going_Up" type positive predictive event. 2007/11/1409/14/2007 02:24:47 EDTYes,E Koh, Benjamin0Rjchangen2nhocompletetomnhocompleteVVchangeoldtocurrentVVchangeoperator1tooperator2Vchangepostopos]VchangeprimitivesaretoprimitiveisVchangeqoslisttolinkparamqoslistaddlinkparamqosli^Vchangerange0-24topoorandrange25-49toaveragerange5Vmy mindd381g39232jChange "MIHF" to "MIHF User". 2007/09/1709/16/2007 03:08:31 EDTYesEMeylemans, MarcFApproveGProducer^ Editorial_184`17a Table B-4c7Bad' and 'Poor' signal strength are the same in my mindd381g3923chnical_132`7c:It is the MIH User (not MIHF) that processes this message.d382g3922jChange "MIHF" to "MIHF User". 2007/09/1709/16/2007 03:08:31 EDTYesEMeylemans, MarcFApproveGProducer^ Editorial_184`17a Table B-4c7Bad' and 'Poor' signal strength are the same in my mindd381g3923 2007/09/1709/16/2007 02:47:09 EDTNo jthethe3gpplowerlayersarel1macrlcandpdcpinthecaseof;Vtheannexoverallshouldcontainsomethinglike3parts1no%VtheannexshouldbemadenormativeandthespecificsuggesteVtheframeworkpresentsmedia-independenthandovermihrefereVtheieee802.21standardspecifiesamihfunctionthatcouldVthemihfunctionsinmnandnetworkentitiescommunicatewitVtheorderoftheannexshouldcomply/Vtheparameterforthelinkgetparametersshouldcontainlin2VthequeryinformationshouldincludeataminimuminformatioVthesquareshouldbe100mx100mwiththemninthecenteraNVtheeWtheirWWWWWWthemW]WWWWWforcommunicationbetweenthemihfonaVthoseOWthough0WthresholdWthroughWW'W(W,W7WthroughoutWthroughputWFWtile$WtimeWWtimerWtitleZWtlvWccommunicationsWcompatabilityWW$WWcompileWcomplementWcompleteWKWLWMWNW_WeWwWTWUWcompletedvWWWcompletelyAWWcompletiondWW[WcomponentWWcomponents7Wcomprehension<WcomprehensiveWcomprisingWcomputer-basedWconceptWWWconceptsWconcernedWconcerningWWconcurrentlyWconditionsWW%WconfidenceWconfig[WconfigurableWconfigurationOWgWkWlWmWnWoWWconfigurationofthemihfisnotspecifiedinthisstandardVconfigurationsWconfigureWconfiguredWconfiguring[WconfirmWconfirmation^Wconflicting/overlapp[Wconfused6WconfusingWWW$WKWLWMWNWwWWW!W"Wconjunction7Wconnect0WconnectedWWconnecting7WochaveWWWWWWW W W,WGWgWnWoWvWwWWWWWWWWWWIWdWWWmust be a one-to-one relationship. In fact, the IP configuration method and server addresses should also be on a per candidate basis thus they should be lists as well (however, care is needed to map the server addresses to the IP configuration methods since not all will be present)S E Julka, VibhorF DisapproveGProducer^ Technical_69`26a7.3.6.3ckFor correctness, either a Link_Down or Link_Event_Rollback.indication can be received prior to time expiry.d283g5319j]Replace sentence "If Link_Down is NOT&." with " If Link_Down or Link_Event_Rollback is NOT&."wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^ Technical_66`8a 7.3.3.1.1cFor added clarity, add text that states that this message can be used for also specifying the time interval between periodic reporting of link parametersd282g5320jReplace line 8 by text "This primitive is used by the MIHF to configure thresholds and/or specify the time interval between periodic reports for the Link_Parameters_Report indication."wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^ Technical_65`49a 7.3.2.2.2cfined. What do these mean?d263g53399 EDTnyjaWWWWWWWWWWWWWWW W W W W - UMTS is wrong. For example, there is no MIMO/OFDM in Rel-7. Then, any MS can be Rel-5 compliant without implementing HSDPA. Similar for Rel-6.d479g4474jxDistinguish between basic W-CDMA features, but remove any reference to releases. 0 - R99 only. 1-HSDPA. 2-HSUPA. 3-MBMS& 2007/09/1709/16/2007 07:13:12 EDTNoߧERudolf, MarianF DisapproveGProducer^ Technical_184`56c. 0 - R99 only. 1-HSDPA. 2-HSUPA. 3-MBMS& 2007/09/1709/16/2007 07:13:12 EDTNoߧERudolf, MarianF DisapproveGProducer^ Technical_184`56cd478g4475 2007/09/1709/16/2007 07:13:12 EDTWWWWWWWWWWWWWWWmontemurromichaelݲVݳVݴVݵVݶVݷVݸVݹVݺVݻVݼVݽVݾVݿVVVnameunatarajanWWWWWWWWW!sreemanthulaWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWsreemanthulasrinviasVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVsrinviasWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWstephenWWWWWWWWP that uses it if MIHF requests to send over layer 2.d133g4820 2007/09/17 'stack' 2007/09/1709/16/2007 02:47:09 EDTNo݈EMeylemans, MarcFApproveGProducer^ Editoriald372g3932 2007/09/1709/16/2007 02:47:09 EDTEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_174`26aB.1.1c"Each character is encoded in order of appearance where each bit of each character is encoded in order of significance." Increasing or decreasing order of significance?d577g5025j"Each character is encoded in order of appearance where each bit of each character is encoded in increasing order of significance."v# Plesae refer to 21-07-0396-01-0000w Principle{k) done 2007/12/1909/16/2007 15:56:25 EDTEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_174`26aB.1.1c"Each character is encoded in order of appearance where each bit of each character is encoded in order of significance." Increasing or decreasing order of significance?d577g5025j"Each character is encoded in order of appearance where each bit of each character is encoded in increasing order of significance."v# Plesae refer to 21-07-0396-01-0000w Principle{k) done 2007/12/1209/16/2007 15:56:25 EDT194PinterestWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWOWPWQWRWSWTWUWVWWWXWYWZWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW-W.W/W0W1W2W3W4W5W6WEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWUclinkparamumtsissortofwrongandneedstobecorrected2Vlinkpowerupambiguouswithegprs/w-cdmawithegprsforexa0VlinksacnlinkscanVlinkscanresponsespecifiesmacaddressinscanresponseseVlinkupindicationcontainsmacaddressesofoldandnewacc Vlink--whichWlink-commandsW3938jJList all normative references or if there are none, then indicate as such. 2007/09/1709/16/2007 02:47:09 EDTNoݏcFApproveGProducer^ Editorial_5`1a2c#No normative references are listed.d366g3938jJList all normative references or if there are none, then indicate as such. 2007/09/1709/16/2007 02:47:09 EDTNoݏ9/1709/16/2007 02:47:09 EDTNoݎEMeylemans, MarcFApproveGProducer^ Editorial_5`1a2c#No normative references are listed.d366g3938jJList all normative references or if there are none, then indicate as such. 2007/09/1709/16/2007 02:47:09 EDTNoݏd365g3939 2007/09/17DcwithinWWWWWWWWWWWWWWWWWWwithoutWWWWWW/WWWWWwlan_W`WWWwlansWWWwmmWWWWWworkWW7WWWWW@Wworking'W7Wworks7WworstWwouldWWWWWWWW WW+W0W7W=WgWxWyW~WWWWWWWWW#W$WWWWWWWwouldn'tWWwouldn'titbeusefultoreferencepreviouslydefineddefiniVwrapWwrongW/W2W:WWW WwwanWxNWxmlW<WxmldoesnotcompileVxvWxxx WxxxxWxyzWyankedWyes1WWyetWWWfWyet-to-be-definedWyieldWyouWWWWWWzeroWHpchangedtexttoVchangedtoVchangedto06466-127foripv6subnetVchangedtocosandalsoupdatedthedescriptionqVchangedtonormativeVchangesWWWWchangesmadeper0374-02VchannelWchannelrangeclarificationandexampleaddedtob-12Vcheck_WWWcheckedWchoiceW^WWchoices WclarificationWWclarificationmadeonthepacketidVVVanguagetoremovetheconfusionVVclearer*WcmtWWW[WWWWWW WWWWWWcmt30deletedthedefinitionVcodeWcommentWWWWWWWW#WnWoWWWWWWWWWWWWWWWW'W>WMWWWWWWWWWW Wcommentnolongerapplicableduetoresolutionofcomment11VVVVjremovepacketidentifierVremoveperiodVremoveperiodbetweenreportandindicationaVremovereferenceormakeareferencetoafuturesectionVremovereferencetotableb-10line3p208Vremovereferencetotableb-10line36p208VeHVremovesection7.4.18andalsorelatedsectiondatatypemihRVremovetagandthecontentsSVremovethechangebars!VremovethesentenceVremovethestackmarkedasremoteentityandremovetextlocVVremovethestackmarkedasremoteentityandremovethetext!V"VremovethestackmarkedasremoteentityremovetextlocaleVVremovethetextaboutthearqmobileintroduceamechanismw VremovethewholesectionVremovethissectionseepage178lines23-43fordiscussionhVremovedWgWremovingWrenameWrenamer1r5asj1j5throughoutthedocumentVreperesent3Wrepetitive<W 2007/09/1709/13/2007 13:56:26 EDTcoptionalWWWfWWWWWWWW>W?WCWDWIWJWWoptions'W+WWWorWWWWWWWWWWWWWWWWWWWWWWWWW W W WW&W'W,W1W7WDWEWYWeWgWnWoWwW}WWWWWWWWWWWWWWWWWWWWWW#W0W6WNWRWSWYWZW\WlWqWvWxWzWWWWWWWWWWWWWWWWWWWWWWWWW WWWWoriginalWWW^WcWosiWotherWWWWWWWWWW?WzW{WWWWWWWW4W>W?W}Wother'sW|j802.16W W(WWW802.16-20004/d/e8W802.1abW802.21WW WW&W'W6W7W8WWWWWWWW=WWWWWWWWworkingassumptionsregarding V802.21'sWW802.37W802.3&3gpp2W9=WhWWaWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW"W#W%W&W'W)W+W,W2W5W6W7W8W=W@WBWGWIW^W_W`WeWhWiWkWlWmWtWwWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW&W+W,W8WEWJW|WWWWWWWW=3E Jeffree, TonyF DisapproveGProducer^General_350`0cAThe draft pays lip service to security, yet a large part of the discussion within 802.11 and ongoing as part of P802.1af is concerned with optimizing the number of exchanges involved and rapidly obtaining the necessary information to re-establish prior security associations/and or make use of previously distributed keys. The separation of handoff/handover/roaming/discovery concerns from those of security is unrealistic and calls into question issues that range from the architecturalpidly obtaining the necessary information to re-establish prior security associations/and or make use of previously distributed keys. The separation of handoff/handover/roaming/discovery concerns from those of security is unrealistic and calls into question issues that range from the architecturalturalwhich the action is a part is mandatory for a claim of conformance. There is at least one "shall" statement that media specific p}vbulletsWWbutWW]WeWWWWWbyWWWWWWWWWWWW WW&W'W,W/W2W5W8W@WAWiWWWWWWWWWÃc@ÃcPÃc`ÃcÃcÃdÃd@ÃdÃePÃg@ÃhpÃhÃhÃi0Ãi`ÃiÃq Ãq0ÃqÃrÃr ÃrPÃr`ÃsPÃsÃsÃtÃt ÃtPÃtpÃuÃv dDTÃqÃrÃr Ãr0Ãr@ÃrPÃr`ÃrpÃrÃrÃrÃsÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0Ãt@ÃtPÃt`ÃtpÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃuÃuÃv dDTDT]$cifatleastonequeryisrequiredthereshouldbesomeminimVifit'sreferringtoanotherpoainthecurrentnetworkthenVifmlme-sapmessagesarepermittedinstate1theywouldalsViftheintentisfortwomihfstomutuallydiscovereachothfVifthemihgetinformationprimitivemustcontainatleastoVifthereisnoreferencespleasechangeclausetexttothereViiiWillustrateWillustratedWWillustrativeWimminentWW_WwWWimpactWimplementWWimplementationWWWWWWW W W#W$WWWWWWWZW[WbWeWfWgWsWtW|W݃W݉WݚWݣWݲWݴWݵWݶWݷWݸWݺWݼWݽWݾWݿWWWWWWWWWWWWWWWWWWWWW&W3W8WjWqWwWކWޏWޠWޡWެWjthenW&W7W]WkWlWmWvW}WWWWWW^WcWqWWWWWWWtheory)WthereWWW2W]WvWWWWWWWWWWWtheremightbehigerlayerswhichdonotusethemihfunctioVthereneedstobesomeformofensuringthatthemnisauthoVthereforeWWW)W-W0W7W@WCWGW`WbWgWhWjWnWoWvWwWWWWWWWWWWWWWthisappearstoberelatedtotheissueofwhichmihusersVthismessageisusedforcommunicationbetweenthemihfonaVthoseOWthough0WthresholdW`WaWthresholdsWthroughWW'W(W,W7WthroughoutWWthroughputWFWthus]Wtile$WtimeWWWtimerW`WWtitleZWtlvWWWWvcwhatistherelationshipbetweenthisandwhatisalready/isVwhatisthevalueaddedofannexjideallythissectionshou.VwhattypeofauthenticationisreferencedherethereisnosVwhat's Wct and requires to be re-drawn. Comment forwarded by IEEE 802.11u chair on behalf of IEEE 802.11u Ad Hoc Meeting, 30th August 2007!d358g3946jAs described in Comment 2007/09/1709/16/2007 01:46:33 EDTYesݗE Xie, QiaobingF DisapproveGUser^General_316dered to be the mobility manager for IEEE 802.11, as opposed to the MLME or the LLC, it appears that Figure 7 is in-correct and requires to be re-drawn. Comment forwarded by IEEE 802.11u chair on behalf of IEEE 802.11u Ad Hoc Meeting, 30th August 2007!d358g3946jAs described in Comment 2007/09/1709/16/2007 01:46:33 EDTYesݗE Xie, QiaobingF DisapproveGUser^General_316d357g3947 2007/09/1709/15/2007 22:08:13 EDTkERajkumar, AjayF GProducer^ Technical_128`13c[The description contains "This identifies the current link" for the source link identifier.d391g5211j_Change "This identifies the current link" to "This identifies the source link of the handover".pduplicate w/ 394wAgree{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNo o , AjayF GProducer^ Technical_128`13c[The description contains "This identifies the current link" for the source link identifier.d391g5211j_Change "This identifies the current link" to "This identifies the source link of the handover".pduplicate w/ 394wAgree{l) none needed 2007/12/0709/16/2007 03:08:31 EDTMarkedNo DTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_124`35a7.4.24.1.2 and othersg4981j correct it 2007/10/0709/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_118Wj vpoamWWWWGWWWWWpoalocationisessentialtodeterminingtheavailabiilityoVpointWWWGWpointsWWWWWpolicy<WposWWWWuWWpower0W2WWWpracticeWpredictionWpredictiveWpreferenceWWpreferredcandidatelilWmWpresent&W'WAWWWWWWWWWAWiWkWwWWWprimitivesWWW@WfWwWWWWWprimitiviesWprinciple]WwW WWpriorAWprioritizedWWpriorityWW(WproceduresWprocessW WproformaWWproperlyWpropoganda6WproposedWprorityWWprotocolW<WWWW'WAW}WWWWW W WprovideW/WWWWWprovidewaysofsimplificationV07 cAMIH deployment model which specifies the location of MIHF PoS and the interactions with the existing system elements on the specific access network like WiMAX, 3GPP are missing. Even though this may be deployment specific according to the operator's preference, it is helpful for the IEEE 802.21 specification reader to utilize the MIHF by recognizing how an MIHF can be deployed by seeing the most general and representative deployment models on the particular networks.d244g5358jCPlease add the following section as H.10. H.10 MIH deployment modelwDisagree{l) none needed 2007/12/1909/14/2007 03:23:37 EDTNo o rity?d252g5350jShow the relationship.vSection 5.1.7 has been deletedw Principle 2007/10/0709/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_15`16a5.1.5ceSounds like you are attempting to re-define mechanisms that already exist in IEEE Std 802.1AB - LLDP.d251c<jAllow the discussion of applicability of MIH ONLY in the Section 5 and informative annexes. The other sections shall only DEFINE and SPECIFY MIH, without any repetitive examples of applicability in mobility management, etc.vAPage 41, Line 57 (e.g., MIHF to MAC, or MIHF to PHY) Page 42, Line 2 (e.g., from upper layer mobility protocol to MIHF, or from policy engine to MIHF) Page 72, Line 65 (e.g., transport) Page 73, Line 2 (e.g., cellular, IEEE 802.16e) Page 73, Line 55 (e.g., cellular, IEEE 802.16e Page 74, Line 19 (e.g., transport) Page 98, Line 36 (e.g., L3 Handovers) Page 95, Line 1 For example, a mobility management entity locally or remotely located from the event origination link may take these egination link may take these enition/specification less focused. d466g5136W<WWWWWWWpoasWpoorWposaWWpositiveAWpossibilityߊWWWpossiblecWߊW߹WpossiblyߥWWWMEMccann, StephenF DisapproveGProducer^ TechnicalcA!Since the IEEE 802.11 SME can be considered to be the mobility manager for IEEE 802.11, as opposed to the MLME or the LLC, it appears that Figure 7 is in-correct and requires to be re-drawn. Comment forwarded by IEEE 802.11u chair on behalf of IEEE 802.11u Ad Hoc Meeting, 30th August 2007!d358g5244jAs described in CommentvXUse TGu MIH contribution (11-2604 rev2) to update the reference diagram and description.w Supercededydeferred{l) none needed 2007/12/1909/16/2007 01:46:33 EDTYes d358g5244jAs described in CommentvXUse TGu MIH contribution (11-2604 rev2) to update the reference diagram and description.w Supercededydeferred{l) none needed 2007/12/0809/16/2007 01:46:33 EDTYes s s lVtrajkumarajaymrajkumarajaynstrajkumarajayo_E Cypher, DavidF DisapproveGGeneral Interest^ Technical_122`30a742322cAOld link actions uses the LINK_ACTIONS type (which does not exist). Perhaps just deleting the "S" it is the LINK_ACTION type. If so, it does not include a link identifier, so which is the old link? There are only current link and target link identifiers in the primitive as parameters.d142g5460jChange old to currentwAgreeyRef 141 (duplicate){l) none needed 2007/12/1909/13/2007 13:56:26 EDTYes E Cypher, DavidF DisapproveGGeneral Interest^ Technical_121`44a742312ca742312crrentwAgreeyRef 141 (duplicate){l) none needed 2007/12/0709/13/2007 13:56:26 EDTMarkedYes E Cypher, DavidF DisapproveGGeneral Interest^ Technical_121`44a742312cree{l) none needed 2007/12/0109/13/2007 13:56:26 EDTYesstomacwlanhoweverthecorrNVthemaymakesitsoundoptionalsVtVs }generalWWWWWWWWWWW-W.W/W0W1W2W3W4W5W6WEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWthe state diagram discussion to an annex.Gd352g3952j!suggest to move 8.2.2 to an annex 2007/09/1709/15/2007 22:08:13 EDTNoݝE Xie, QiaobingF DisapproveGUser^ Technicala7.4.24d351g3953 2007/09/1709/15/2007 22:08:13 EDT4EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_39`17a6.3.4.1c"For example, the occurrence of a handover of a mobile node, from one access network to another will result in the reestablishment of a link layer connection to the target access network." Extraneous comma.d555g5047e is a high confidence level in the time interval. A time interval of 0 is specified if there is low-confidence in the computation of time interval. Additional reason codes for Link_GOING_Down may B8be added. This needs to be done throughout the document&wAgree 2007/11/1809/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_39`17a6.3.4.1c"For example, the occurrence of a handover of a mobile node, from one access network to another will result in the reestablishment of a link layer connection to the target access network." Extraneous comma.d555g5047Wemphasise߷WemsWenableTWWW7cfinalWWWWfinallayoutbyieeeeditorialteamwillresultintablestoVfinalizeWfind%WWWfiniteWfirstWWWwWWWW/WWWWWW W WWwWfollowingJW_WtWfontWfontofparametersinlistneedstobemadeconsistentVforWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW%W'W+W/W0W4W6W7W:W=WBWCWGWJWKWLWMWNWYWZW[W\W]W^W_WcWeWfWqWrWsWxWyW~WWWWWWWWWWWWWWWWWWWr ? 2007/12/1909/10/2007 07:08:58 EDTYess.3c&Emphasize that this is only an exampled51g5551j;Start paragraph with: "As an example, Figure 19 shows ...."wAgree 2007/11/26hnology is very beneficial but should be included in a (possible normative) Annex. Second, such a mapping should be structured by "technology" and not by the name of the SAPs.wd52g5550jDelete items a) through e) and move their contents to a (normative) Annex. There should be one Annex per technology containing any technology-specific information which is reqired to make 802.21 work with / adapt to the specific technology.v>Move items [a] through [e] to Annex-L. Make Annex-L normative.wAgree 2007/11/1809/10/2007 07:08:58 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_49`17a6.5.3c&Emphasize that this is only an exampled51g5551j;Start paragraph with: "As an example, Figure 19 shows ...."wAgree 2007/11/18YesLcforcommunicationbetweentworemotemihfsthepropagationfVforcorrectnesseitheralinkdownorlinkeventrollbackinVforexampletheoccurrenceofahandoverofamobilenodefrVforimprovedreadabilityhandlingofare-transmittedmihreVforinter-techhandover802.21needstodefineifthehandovVfornetworkassistedhandoversnethocommitmaynotknowabVformWWformallyWformatW5W Wformats3WWformerWforthWforumWforwardmWforwardedWWfound&WW W WfractionWfragmentationWframeWWWWW WframesWWframeworkWWfrequency1WWuuuuuuuuuuuuuuuuuuuuuuuuuuu'MjdecisionsWWdecreasingWWdefaultWdefineWWWWWWWWW&W0W1W4W<WUWVWeWWWWWWWWWWWWWdefineaseparateregistrationidthatisusedforthelifetVdefineaccessrouterVdefineanactualrelationshipbetweenchannelidandoperati1Vdefinearfcnbsicgsmvsw-cdmabandbyreferencesto3gpps4VdefinedevicestatesresponselistasVdefinesupportedlcpVVdefinesystemparametersUVUVWdefinitionsW%WdefintionsWdegreesWdeiveries WdeleteWWWWWWWWWWW W1WdeleteallreferencestomihnetsapfromthespecdeletereVdeleteallreferencestomihnmssapfromthespecdeletereVdeleteannexfVdeleteannexjVdeletecurrentlinkidentifiefromallmihhandoverprimitivesVnbE Cypher, DavidF DisapproveGGeneral Interest^ Technical_108`23a741942c|The type and description for the Handover status do not agree. There are no reasons given in the HANDOVER_STATUS on page 202d138g5464j>Align text with TYPE or change type to align with description.pJMaybe there should be more declined reason in HANDOVER_STATUS in page 202.vLChange text to "Indicates the MN accepted or declined the handover request."wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTE Cypher, DavidF DisapproveGGeneral Interest^ Technical_108`23a741942c|The type and description for the Handover status do not agree. There are no reasons given in the HANDOVER_STATUS on page 202d138g5464j>Align text with TYPE or change type to align with description.pJMaybe there should be more declined reason in HANDOVER_STATUS in page 202.vLChange text to "Indicates the MN accepted or declined the handover request."wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTeeW> cchoices'WchosenWchronologicallyWcitedWcivicWclaimWclarification=Wclarificationonparsingdatatypesisneeded=VclarifyWWWWWWW%WclarityWclassWclassesqWclassificationWclassifyingWclauseWWWWWWWWWmWWWWWWWWWclause5issupposedtobegeneral802.21architecturedescrVclauseincludesmedia-speficmappingsbutshouldnotdososVclausesWclearWWW7WWWW@WWWW WclearlyWWWWcloseWco-existanceWco-workerWcodeWWcodingxWcoherentWWWWWWWWtnerWWWWWtnerWWWWWicularWWWWzW|WpartnerWWWposW3WaWWWWW09/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_284`61aKcAThroughput is a commonly used communications term and it is seldom used the way it is defined here. In this paragraph, Link Throughput is defined as Maximum Link Rate. Using througput in this unusual way is not the best means to promote understanding of MIH common terms.d630g4972jUUse Max Link Rate instead of throughput for definition 1 and elsewhere in this annex.nNada provided the amendment. "Link Throughout: the number of bits successfully received divided by the time it took to transmit them over the medium." vThroughput is defined as the instantaneous bit rate i.e. number of bits transmitted over a certain time interface. It is not intended to characterize the links speed. Text in the draft will be clarified to reflect that by Nadaw Principle{k) done 2007/12/1909/16/2007 23:32:08 EDTMarkedMarked EKwak, Joseph A3UlcofWWWWWWW W#W&W'W(W*W+W,W/W1W9W<WBWGWHWMWNWOWQWZW\WiWjWkWlWmWqWuWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWW noun, not a verb, so what is "to guild"?d147g4806jChange guild to guide 2007/09/1709/13/2007 13:56:26 EDTYes13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_144`3a821c3guild is a noun, not a verb, so what is "to guild"?d147g4806jChange guild to guide 2007/09/1709/13/2007 13:56:26 EDTYesg4807: g^_`abcd€€€€€4d6cA8d7cB=d<cCcBFdEcAIdH jN ERQEYcA\d[a^EbGihcAmdl cn"cp$du'jy+E~}.d1j4F7cAd9j- Optional parameters added to Net_HO_Candidate_Query.responsew Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNoiguration or address).ad423g5179information about resource requirements than the corresponding Net_HO_Candidate_Query.response. In both cases, the network PoS would query the candidates to see if it could support the requested resources (however, in the network initiated handover case, it may have less information, e.g. no IP configuration or address).ad423g5179 the optional parameters, asymmetric request/response, and allowing MIH User(s) to specify MIHF capabilities it is unclear as to this primitives usefullness.d424g5178ghoF DisapproveGProducer^ Technical_46 cAOld link actions uses the LINK_ACTIONS type (which does not exist). Perhaps just deleting the "S" it is the LINK_ACTION type. If so, it does not include a link identifier, so which is the old link? There are only current link and target link identifiers in the primitive as parameters.d141g5461jChange old to currentpHChange to old to source. Since the "source" was used instead of current.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s 407g5195jbreak or break before make. Also, we are still left with the problem of knowing when to issue the Link HO Complete event (e.g. after upper layer handover processing, MIP).vvk Actions) the MIHF doesn't know when to issue a Link HO Imminent. In the combined case MIHF is in control and can issue the Link HO Imminent just before is executes the Link Actions. The problem with this is that the MN_HO_Commit command does not have any associated Link Actions.d407W disapproveݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟݟ7vresoponsefWresourceWWlWmWWresourceretentionreqWresourceretentionstaWresourcesWkWlWmW W WWWrespect WrespectiveW5WWrespondW WresponseWW<WEWuWwWWWJWresponse/confirmWresulteWvWretentionWretractedWretransmission'W{W Wretransmissions'W Wretransmit'W Wretransmitted WreturnWWreturns^Wrev2WrevisionW/WAWne think t MIH_NET_SAP includes a parameter to select whether L2 or L3 are chosen as transport method. If MIH_NET_SAP is used for L3 only, then there is no need for this parameter. If there is a need for the parameter then the text of this clause 6.7 needs to be changed to reflect the meaning of this parameter. Or could one think tect the meaning of this parameter. Or could one think tE Jee, JunghoonF DisapproveGProducer^ Technical_143`1a8cbMIH Handover Protocol behavior is missing from the section 8. Media Independent Handover Protocol.d243g5359ssing. Even though this may be deployment specific according to the operator's preference, it is helpful for the IEEE 802.21 specification reader to utilize the MIHF by recognizing how an MIHF can be deployed by seeing the most general and representative deployment models on the particular networks.d244g5358jCPlease add the following section as H.10. H.10 MIH deployment modelwDisagree 2007/11/3009/14/2007 03:23:37 EDTMarkedNoE Jee, JunghoonF DisapproveGProducer^ Technical_143`1a8cbMIH Handover Protocol behavior is missing from the section 8. Media Independent Handover Protocol.d243g5359 the line numbers left by a few mm 2007/10/0709/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ Editorial26 EDTYes01ceachbitofabitmapnvaluen8ii12isencodedasannVeachcharacterisencodedinorderofappearancewhereeachVeachothertousing}Veap7WWeapolWearlier WearlyWease-of-usablityWeasilyWWeastWec/ioWeditorialWeffectuWeffective=Wefficient=Weffort=WegWWegprs0Wegprs/w-cdma0WeitherWWwWWWWWW6WWWelementWWWpWWWelementsWWWW6WWelemetsWeliminateWeliminatesWelseWWWWembedded WemergencyWemphasise@WemphasizeWemphasizethatthisisonlyanexampleVemsWenableWWWnschangeVthereseemstobearbitrarydecisionsmaderegardingthemihVthereseemstobelimitedusefulnessofthelinktransmissioV<candparameterextractioncommandsmissinghyphenVcal_215`34c]Value of TYPE_IE_POA_MAC_ADDRESS is 10000302 here, while it is 10000200 in Table A-1 page 173d151g4802jConsistently use one value 2007/09/1709/13/2007 13:56:26 EDTYesalue of TYPE_IE_POA_MAC_ADDRESS is 10000302 here, while it is 10000200 in Table A-1 page 173d151g4802jConsistently use one value 2007/09/1709/13/2007 13:56:26 EDTYesher, DavidF DisapproveGGeneral Interest^ Technical_215`34c]Value of TYPE_IE_POA_MAC_ADDRESS is 10000302 here, while it is 10000200 in Table A-1 page 173d151g4802jConsistently use one value 2007/09/1709/13/2007 13:56:26 EDTYesavidF DisapproveGGeneral Interest^ Technical_215`34c]Value of TYPE_IE_POA_MAC_ADDRESS is 10000302 here, while it is 10000200 in Table A-1 page 173d151g4802jConsistently use one value 2007/09/1709/13/2007 13:56:26 EDTYesd150g4803 2007/09/1709/13/2007 13:56:26 EDTjAchange the "stack" to "node", and "remote stack" to "remote node"p1but no change made to the phrase "protocol stack"vChange "stack" in all places. w Principle{k) done 2007/12/1909/16/2007 08:19:02 EDTYesE Cheng, HongF DisapproveGProducer^General_5`1a2cMIH is about handover between different access technologies. Yet, there is not even one normative reference. Is the MIH really built from scratch that does not rely on any prior defined technolgy?d497g5105jVTake a look what other 802 standards does, and define the normative reference for MIH.pNormative references added. v+Qiaobing to fx this and provide explanationwAgreey deferred.{k) done 2007/12/1909/16/2007 08:19:02 EDTYes 17 EDTMarkedNoE Cheng, HongF DisapproveGProducer^General_15`62a5heng, HongF DisapproveGProducer^General_15`62a5represented in the transaction state machines aboveL 2007/10/07 EDTWimsi;Wjidentifiers1W3WDWEWJWidentifiesCWWWWieWW=WWWWWWWWWieeeWW(WWWWWWWWWWW=WFWWWWiesWifWWWWWW WWW&W'W-W.W4W7W]WkWlWmWvWWWWWWWWWWWWWWWWWWW:W;WJW^WcWqWWWWWWWWWWifamappingof802.21serviceprimitivestoaspecifictechVifannexaisnormativemakeitaclauseinthebodyoftheVifannexbisnormativemakeitaclauseinthebodyoftheVifannexcisnormativemakeitaclauseinthebodyoftheVifannexdisnormativemakeitaclauseinthebodyoftheVifbothareneededthenclearlyincludebothinallrelevantVictherearetwodefinitionfforthesamethingahigherlayersVtherearetwomedia-dependentsapsiemihlinksapandmihVtherearetwoplaceswherethemihlinkupisusedneitheroZV\Vthereareveryfew8shallsinsection6.0mihfservicesandVthereisabitofadichotomyinthedefinitionofthisprimVthereisalackofapositivepredictivelinkeventlinkgoi,Vthe selector octet? Order ov value? Increasing order or decreasing order?d578g4375j the list of data types DATATYPE1,DATATYPE2,[,&] is selected. The Value field is encoded using the encoding rule for the selected data type." What is the binary encoding of the selector octet? Order ov value? Increasing order or decreasing order?d578g4375j 2007/09/1709/16/2007 15:56:25 EDTYes@links@listofsupportedmiisquerytypesonthelocalmihf@fllc@Qlong@makerequestedresourcesetparameteroptionalinbothther@kCcisWWWWWWWWWWWWWWWWWWWWW W WWW classification scheme starting on line 21 of this page. You might alsoi want to number the entities according to the table starting at line 8ce, but not a link.d551g4402j)"Communication connection reference type" 2007/09/1709/16/2007 15:56:25 EDTYes_EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_20`8a5.4.2cIn Figure 2, you have numbered the communication links according to the classification scheme starting on line 21 of this page. You might alsoi want to number the entities according to the table starting at line 8plin, Clint FF DisapproveGGeneral Interest^ Technical_20`8a5.4.2cIn Figure 2, you have numbered the communication links according to the classification scheme starting on line 21 of this page. You might alsoi want to number the entities according to the table starting at line 8 cin@[1FKincludes@indicates@^informative@interact@interfaces@Uinteroperability@is@^kCissue@it@itappearsthatcosvaluesfromthelinkparamtypeofgener@itisincorrecttosaythatthetransmissionstatuscanbev@xitself@+justwhenisalinkhandoverconsideredcompleteseepage98@9kenichibitmap64shouldnameasrevision@kenichiipconfigurationmethodsdhcpserveraddressfaaddr@label@layers@lines38-52thestatisticalparameterslistedontheselines@linkhlinkconfigparamallowsonetorequestthatareportbegen@[linkparamumtsissortofwrongandneedstobecorrected@link-detect@localmihuserspecifyinglocalmihfcapabilitiesaswellas@wmac-hs@makes@umanagement@akes@umanagement@gement@ jtheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWW W!W$W%W&W'W(W)W+W,W-W.W0W1W2W4W5W6W7W8W;W<W=W>W?W@WBWCWGWHWIWKWLWMWNWSWXWZW]W^W`WbWcWdWeWiWjWkWlWmWtWvWwWxWyWzW{W|W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW4paddedx-reftoallmessagesin8.6VaddingWadditionalWWWWaddressWW WOWWWadoptedWadoptedthereplacementsentencebutleftouttheadditionalVafterWagain_WWagreed/WAWagreedbutsincetextinthebodymaystillchangeandhence/ValgorithmWWaliceWall^WWOWOWOWM disapproveNL Nmontemurromichael M disapproveO*Pej(`P disapproveQO*Qjulkavibhor P disapproveR S% S disapproveTR Tzunigajuanc S disapproveUVV disapproveWUWjeffreeanthonya V disapproveXb[jY1PY disapproveZXjZcypherdavidK Y disapprove[ disapprove\Xb\cypherdavidl [ disapprove] disapprove^Ca^cypherdavidn ] disapprove_ disapprove`CJ`cypherdavido _ disapproveaKcthethreeitemsmakeanormativeassumtionorevenstandardi@*then@/there@itherearetwodefinitionfforthesamethingahigherlayers@thereisalackofapositivepredictivemiheventmihlink@thereisnowayforthiseventtoindicatethatitwasgener@ntherefore@thing@k layer technologies." 2007/09/17WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWW W!W#W%W&W)W*W+W,W-W2W3W4W7W8W=W@WAWIWKWLWOWYWZW[WbWdWhWiWjWoWpWsWtWyWW݁W݂W݇W݉WݘWݞWݠW^cstatisticalWstatisticsWstatusW W WWOWnWoWtWuWvWWW2W9WWWWstatustlvdatatypeshouldbestatusinsteadofenumerated9VstatusesWstdWstilWstill7WWstrengthWWstrictlyWstrictlyspeakingreferencestoieee802.21areself-referenVstring~WWstructuredWstyle/WPWWsubWsub-clause=W>W?W@WAWBWsub-clause3.40aprotocoldataunitpdureferstoapacketBVsub-clause3.44aserviceprimitivedescribesaninteractioAVWsuccessfully WsuchWWWW W WW=W?WsuffersWsufficientWsuggestedWsuiteWsumWsupportWWWWsupportedWWWWWWsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliWVVVVW2$E Cheng, HongF DisapproveGProducer^ Editorial_33`1a6cBoth the subclause 5.3 and 6 are simply named "MIHF Services". It is confusing. The group should come up with better titles to describe the contents.d490g5112j Change the tile of subclause 5.3p&5.3 changed to "MIHF service overview"{k) done 2007/12/1909/16/2007 08:19:02 EDTYes%ERudolf, MarianF DisapproveGProducer^ Editorial_173`1cA^Reorganize the Annexes. For example, I find Annex F and G and H valuable and good to keep. However, in order to improve readability of the Annex in general, which contains a wealth of information, may want to consider to collapse information. For example, all normative parts should all go together and then, all informative parts should go together.^d489g5113jse 5.3 2007/11/1809/16/2007 08:19:02 EDTMarkedYes007/11/1409/16/2007 08:19:02 EDTYes$E Cheng, HongF DisapproveGProducer^ Editorial_33`1a6<mjincorporating8Wincrease(Wincreasethedegreeofflexibilityforusageoftherelated(VndicateWW=WWWWWindicatethatthereversedirectionsareallowedVindicating_WdWWindicationW WeWtWWWWindicationsWindividual&WinfoWinfoquerybinarydataWinformationWWWWWW7W>WAWgWkWlWmWWWWWWWWWWWWinformational9Winformative%W<WinitWWinitiateWWinitiatingWinitiationWinlcude8Winlcudeasaminimumthelatest802.11roll-upandforexamp8VinsertW-W.WinsideWinsteadWWintWintegralWintegrateWintegratemihnetsapandmihlinksapintomihlowersapitVintendedWintendendKWLWMWNW2007/09/1709/14/2007 23:15:41 EDTdfjnumeric=WobtainWEWoccur%Woccurences W#W$WoccurrenceWoccurrencesWYWoctetWWW~WWWoctetstring~VVoctetsW=WHWWWWWWofWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW"W#W$W&W'W(W+W,W0W3W4W5W6W7W;W<W=W>W?WBWCWIWKWLWMWNWXW]W^W`WbWdWiWkWlWmWvWwW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW007 13:56:26 EDT[jiis7WimminentwWWimminent/completetWimplementWWWimplementation'WimplementedW&WWWimplementing Wimplementor W'WimpliesWimportant2WWimsiWinWWWWWWWWWWWWWWWWWWWWWWW WWWWWW%W&W'W)W+W0W1W4W7W;W<WJWXWiWkWlWmWtW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW%W'W.W0W5W=WCWDWEWFWHWNWgWiWjWWWWWWWWWWWWWWWWWW W&W7W9W\W^WcWgW߄W? 2007/12/1909/16/2007 21:41:08 EDTYes s _87`32a7.4.4cAMIH Event Subscription, as defined, has limited capability for practical uses. It should be possible for event subscription to set parameters for individual events that are being subscribed for. The parameters will be correspondingly be applicable only for that specific event. As an example, link-detect may result in inefficiency due to reporting of not so relevant networks. It should be possible to subscribe to see only specific network identifiers.d606g4996j Please see the contribution #305pSuperceed by 615.vby 615w Superceded{l) none needed 2007/12/0709/16/2007 21:41:08 EDTMarkedYes rkedYes &E|EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_164`14a8.6.3.12cZ"This message is used for communication between the MIHF on a MN and the MIHF on network."d575g5027j\"This message is used for communication between the MIHF on a MN and the MIHF on a network."wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_154`6a8.6.1.2c"When an MIH network entity broadcasts unsolicited MIH_Capability_Discover response to advertise its MIHF ID and capabilities, Destination ID shall be a broadcast MIHF ID."d574g5028574g5028ral Interest^ Editorial_154`6a8.6.1.2c"When an MIH network entity broadcasts unsolicited MIH_Capability_Discover response to advertise its MIHF ID and capabilities, Destination ID shall be a broadcast MIHF ID."d574g5028n top of change specified in comment 384 Plesae refer to 21-07-0396-01-0000w Principle 2007/11/1409/16/2007 15:56:25 EDTWw Mcthethe802.11architectureismissingthe802.1xauthenticatorVtheackmechanismisoptionaltouseandsincethestatediaVthearrowinfig23shouldshowthatuponreceiptofmihreqVthechangebaratleftsideshouldnotappearinthisdraft!VtheconceptandproceduresformihfdiscoveryarenotspecifVthecontentsoftableb-13attemptstodefineaccesstechnolVthecurrentlinkidentifierisinconsistentwiththeotherhzV{VthedefinitionofnmsnetworkmanagementsystemisnotdefinVthedescriptioncontainsthisidentifiesthecurrentlinkfoCVVVVthedescriptionofthesourcelinkidentifierandtargetlinKVLVMVNVthedescriptionsforinfoquerybinarydatalistinfoqueryVthedestinationofaneventisestablisheddynamicallydoesVthedraftisveryverboseandinsertstoomanyout-of-scope<VtheentireannexbispoorlyorganizedthegroupingisnotcV?AAELach, Hong-YonF DisapproveGProducer^ Technical_8`44cSub-clause 3.44: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d461g5141jKCorrect definition, by replacing "information transfer" with "interaction".ve. . ." to "The service primitives defined at this interface. . ."|vDelete "From that perspective, MIHF offers a unified interface to the MIH Users." Replace "The service primitives exposed by this unified interface. . ." to "The service primitives defined by this interface. . ."wAgree 2007/11/1809/16/2007 06:10:15 EDTMarkedYesAELach, Hong-YonF DisapproveGProducer^ Technical_8`44cSub-clause 3.44: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d461g5141jKCorrect definition, by replacing "information transfer" with "interaction".vWWWSctechnology-specificWtemporaryWtendWtentativeWtermWWWWWWWWWWterminateWterminatedgWterminologyWtermsWWWWWWWWWWWWtested WtestingWtextWWWWbWWWWWWWWWWWWWW<WWWWWWWWWWWWWWWWWWWWtextstatesthatmax2retransmissionsareallowedbutthesVVtext/conditionWtextswWVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVest-response mechanism will not scale to accommodate large numbers of MIH-capable mobile nodes.d324g3980 2007/09/1709/14/2007 23:15:41 EDTYesjPlease add the following section as 8.3. 8.3 MIH Protocol Steps 8.3.1 Information Query 8.3.2 Resource Availability Check 8.3.3 Resource Preparation 8.3.4 Target Decision and Handover execution 8.3.5 Resource ReleasevqAdd this in section 8.2. Replace bullet 5 with the proposed bullets and add some text to describe these bullets. w Principle{k) done 2007/12/1909/14/2007 03:22:03 EDTNo E Jee, JunghoonF DisapproveGProducer^ Technical_143`1a8cPlease clarify which protocol message is mandatory and which is optional under concerning inter-operability among different vendors developing the IEEE 802.21 compliant systems.d242g5360jPlease mark each protocol message as mandatory or optional. Alternative is to first categorize the functionalities IEEE 802.21's MIHF provides then specify mandatory or optional for each functionality.psuperceded by comment #10w Superceded{l) none needed 2007/12/1909/14/2007 03:21:12 EDTMarkedMarkedswcentryWWenumerated9WequalWWequationWequipmentWequivalentWWWerrorWWFWWWWWespecially6WessWWessentialWesssWestablish0WestablishedWuWWWestablishing0Wetc.W7WW(W]WWWethernet WethertypeW-WevaluatedWevaluationWevenWWWW WWWW6W7WWWWWW#WWWWWWWWeventWWWWWWWWWW\WbWfWWWWW+W,WtWWWWWWWevent-subscriptionWeventsWWWWW*W?WwWWWWW(WWWWevery WWWW%W/W0WYWZW]WWWWWWW'W(WWWWW&jthWthanWWWWvWWthatWWWWWWWWWW WWW&W'W)W0W5W7W=W@WbWkWlWmWtWvWxWyW}WWWWWWWWWWWWWWWWWWWWWWWW@WgWWWWWWWWWWWWWWW WthatthemihuseruponreceivingthenethocommitindicatiotVYesE Cypher, DavidF Disapprove Editorial_228`47c,Consistency with paragraph/bullet conventiond166g4787j!Add blank link between 9) and 10) 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF Disapprovesistency with paragraph/bullet conventiond166g4787j!Add blank link between 9) and 10) 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF Disapprove8 2007/09/1709/13/2007 13:56:26 EDTYesݾ7cfactorWWWWfailedWeWfailureWW_WWfailuretotransmitdataisnotsameasthelostdataVfailuresWfallWfalseWWWfarWWfdd3Wfeasible WfeaturesWfewWWWW7WWfieldWW=WW6W<WAWfigWWWWWWWWWfig11conflictswithfigures9and10for3gppand3gpp2fiVfig18localandremotestackarenotrepresentedsymmetricaVfigureWWWWWWWWWW*WnWoWWWWWWW!W"WNWWWWWWWWWWWWfigure1givesexamplesofupperlayersipetcandlowerlayVfigure12shouldbemovedtosection6.2.1becauseitshows*Vfigure12youmightwanttoindicatethatthemiheventsubsV 2007/09/1709/14/2007 23:15:41 EDTjdefinetheinterworkingorremoveitVdefinethelinkestablishmentaspdpcontextactivationint0Vdefinethelinkupprimitivesuchthatitisal2primitiveVdefinethemissingdefinitionVVdefinetheprioritiesoftheitemsindifferentcategoriesVdefinethetermsbeforetheyareusedifthesearedefinediVdefineunambiguousmappingsbetween802.21linkthresholdvaVdefinevaluesforthesetwonetworksVdefinedWW@WXWWWWWWWWWWWFWWWdefined&mayWdefinesWW.W=WWdefining WW W#W$W:W;WdefinitionsW%WWdefintionsWdegree(WdegreesWdeiveries WdeleteWWWWWWWWWWW W1W=W?W@WFWYWjWnWoWpWrWsW|WWWWWWWWWW<WjthisappearstoberelatedtotheissueofwhichmihusersVthismessageisusedforcommunicationbetweenthemihfonaVthissentencebere-writtentobetterspecifywhatsecurityVthoseOW@WWWthough0WthreeQWWthresholdW`WaWWthresholdsWWLWQWXWthroughWW'W(W,W7WWWWthroughoutWWW3WWWthroughputWFWthus]Wtile$WtimeWWWWtimerW`WWtitleZW-W.WtlvWWWW5WIWJWtlvsW#WconsistentlyvWconstraintsoWpW/W0WWWWconstructedߒWconsumedWcontact߁Wcontain:W?WTWߥWW?WWWWcontained=WWWcontainer(W)W*W=Wcontaining߾Wcontains߄WߜWߺWWWWWWWWWcontecttWMvchangestackinallplacesVchangetextasanexampleforieee802.11thisreferstotheVchangetexttoindicatesthemnacceptedordeclinedthehanVchangethecurrentlinkidentifietosourcelinkidentifierforVchangethedatatypetolinkaddressacvivekqiaobingpleas VchangethepoatlvtolinkidVchangethetitleofthisannextomediaspecificmappingforEVchangethetypetolinkaddressVchangethisinallplacesindraftcarefully VchangethissentenceasfollowsVchangethresholdcrossingdirectiontoenumeraedtypeaboveaVchangetolinktupleidVchangetolistdatatypeexceptforipconfigurationmethodsOVcorderWWW%WvWxWyWW/WtWWWWorderedWWorganizationWWorganizedWWoriginalWWW^WcWosiWotherWWWWWWWWWW?WzW{WWWWWWWW4W>W?W}WWWWWother'sWidontthinkthisisunambiguousVVmobilenodeto޴VidontthinkthisisunambiguousVVmobilenodeto޴VidontthinkthisisunambiguousVVmobilenodeto޴VidontthinkthisisunambiguousVVssifyinglinkeventsidontthinkthisisunambiguousVVice,W/Wid܎W܏WܓWܾWܿWWW7W8WeWfWgWjWqWzWݭWW%WdWyWހWWWWWideaW%WWideallyWidentified8W޾WEjeInclude the appropriate material in the stadnard. At a minimum explain how to obtain these documents.vDelete sections L1 and L2 from this Annex. Change the title of this Annex to "Media specific mapping for SAPs" Elsewhere in the draft it is mentioned that medi aspecific enhancements should be included in draft. Remove such statements (pg 23 line 52).w Principle{k) done 2007/12/1909/13/2007 15:42:30 EDTYes s )B cnetworkWh AF DisapproveGGeneral Interest^ Technical_287`3aKcc,CoS is not included in list of abbreviationsd633g4320j Add it there. 2007/09/1709/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_287`3aKcrvices at various QoS levels.d634g4319j=Use Available Admission Capacity for Supported number of CoS. 2007/09/1709/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_284`53aKc,CoS is not included in list of abbreviationsd633g4320j Add it there. 2007/09/1709/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_287`3aKc09/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_287`3aKcd632g4321 2007/09/1709/16/2007 23:32:08 EDTialܮWܰW3W;Wmax܆Wmaximum܄Wmaximumdataratein802.11termsisthehighestavailableb܄V)4ydeferredȃ⦃⧃⨃ÃWdeferredrefcmt331VVVVVVVVVVVcmt590Vdeferredsameas114Vdeferredseecmt4978VdefferredWdefferredrefcmt497VrefWWWWWWWWWWWWref238Vrefcmt105VVrefcmt106VVrefcmt114Vrefcmt363Vrefcmt556VsameWsee8W{€markedᆃᇃቃኃዃῃ㑃㒃㓃€noƒ %()*+,-./1349:;OPQRST[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⦃⧃⬃⮃ⱃⴃiERajkumar, AjayF GProducer^ Technical_166`16c]Target PoA is defined as LINK_ID in Net_HO_Commit SAP (Page 124, Line 35; but as PoA TLV hered386g5216j Change the PoA TLV to fixed typep: Table C-2 (page 207 line 24) maps the PoA TLV to LINK_ID.vChange the PoA TLV to LINK_IDw Principle{e) editor disagrees 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_179`27c=Definition of LINK_AC_RESULT_CODE does not have a valid ranged385anged385echnical_166`16c]Target PoA is defined as LINK_ID in Net_HO_Commit SAP (Page 124, Line 35; but as PoA TLV hered386g5216j Change the PoA TLV to fixed typep: Table C-2 (page 207 line 24) maps the PoA TLV to LINK_ID.vChange the PoA TLV to LINK_IDw Principle{e) editor disagrees 2007/12/0109/16/2007 03:08:31 EDTMarkedNoERajkumar, AjayF GProducer^ Technical_179`27c=Definition of LINK_AC_RESULT_CODE does not have a valid ranged385se?e'?ENoens, Richard HF DisapproveGProducer^General_36`20a6.3.1cFigure 13 is confusing.d100g5502jaRemove "Remote Entity" stack and remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1909/11/2007 17:47:21 EDTYes esENoens, Richard HF DisapproveGProducer^General_36`20a6.3.1cFigure 13 is confusing.d100g5502jaRemove "Remote Entity" stack and remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1409/11/2007 17:47:21 EDTYes :47:21 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_148`24a8.2.3.1cWWWWWWnatarajanWWWWWWWWWWW$jconcerned7Wconcise7WzWzWzWzWzWzWzWzWWzWzWzWzWzWzWzWzWzWzWzWzWWzWzWzWzWezWzWzWzWzWzWzWzWzWzWzWezWzWzWzWzWzWzWzWzWzWzWgezWzWzWzWl3!WPWW W*Wlabel_WlanguagezWzWzWzWzWzWl3!WPWW W*Wlabel_WlanguagezWzWguagezWzWagezWzWzWzWlatest߯W߯W߯WW߯W߯W߯W߯W߯W߯W߯W߯Wt߯W߯W߯W߯W߯W߯W߯W߯W߯WW߯WW߯W߯W߯W߯W߯W߯W*Wlabel_WlanguagezWlaptopߝWlatest߯W߯W߯W߯W߯W߯W߯W߯W4/2007 23:15:41 EDTK DcconsistencyaddressoraddressSVconsistencyfornatdoesnatstandfornetworkaddresstransRVconsistencyinnamingislackingrVconsistencyinthecapitalizationofservicethreebulletsaVconsistencyintheuseofmihlinkactionormihlinkactionlVconsistencylink-idorlinkidvVnsistencythemihgetlinkparametersresponsemessageconJVconsistencythemihn2nhoqueryresourcesrequestandthemIVconsistencythereisnomihconfigurelinkLVconsistencythereisnomihn2nhocandidatequeryKVconsistencywithparagraph/bulletconventionhVconsistentWWWWconsistentlyWconstraintsWWWW W#W$WconstructedWconsumedMWcontact WcontainWWW.W^WWWIWcontainedWIWuWcontainerWWWWcontainingGWcontains W%WCW^WgWuWWWW<WJWcontectWOESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_118`1a7.4.22cwFor network assisted handovers, Net HO Commit may not know about the PoA specifics. Should include network identifiers.d620g4982a genreal term, which is already defined.d617g4985j correct itp Done in 621vby 622w Superceded{l) none needed 2007/12/0709/16/2007 21:41:08 EDTMarkedYes C address" is used instead of a genric link id or address. MAC is a 802 term, should use a genreal term, which is already defined.d617g4985j correct itp Done in 621vby 622w Superceded{l) none needed 2007/12/0709/16/2007 21:41:08 EDTMarkedYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technicalgenric link id or address. MAC is a 802 term, should use a genreal term, which is already defined.d621g4981j correct it 2007/11/1209/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technicalstp`‚8ᣃᭃ4BU⍃6‚9r‚:ᲃ8ㅃ ‚AḃQу‚Bᧃ !]A‚Cᰃ+Cx∃9Hr㰃‚DDR✃⤃ڃ㌃̃‚Eឃ߃]w㈃փ‚F᥃){⃃‚Gᑃ7☃ccapabilitiesWW]WfWWcapabilityWWWWWWWcapableWWcapacityWcapitalizationWWcapitalizedWWcaptionWcaptureWcapturedWcardinalityTWcareW,WkWlWmWWWcarriedWcarriestWWcarryWtWWW WcaseWWWW W WWWKWLWMWNWgWwWWWWWW%WMWWWWW^ Technical_14`14a5.2.1cA(The text in the standard states: "This standard may contain recommendations to amend the existing access technology specific standards when modifications of the lower-layer interfaces may enable or enhance the MIHF". This is accomplished through liason relationships, not standards specification.(d302g4002jRemove the sentence. 2007/09/1709/14/2007 23:15:41 EDTYesd301g4003 2007/09/17tjsourceidentiferWspacesWspecWWWspecficWspecificWW7WWWWWWWWWspecificallyWWW7WWstandardWstartingWWstateWW W WstatementWWstates WstatisticsWstatus WsublayerWsubnetWsubparameter WsuchWWsuggestWsuggestrewritingthissectionVsupportWsupportedWWWWWsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliWsupportingWsupportsWsyntaxWsystemWtableWWWtargetWWtechnical WtechnologiesWW WtechnologyW WtermWterminateWtermsWWtextWWWWWW WthWthanWWWthatWWWWWWWWWW WI4jInclude a formal specification of the MIH protocol, either as a completely defined state machine (in the manner of IEEE 802.3), a reference code specification (in the manner of IEEE 802.1), or a formalized language (in the manner of IEEE 802.11).v)Please see contributon 21-07-0302-00-0000wAgree{k) done 2007/12/1909/03/2007 16:49:33 EDTYes E Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8c;No conformance requirements are provided for this protocol.d10g5592j(Include a PICS proforma for this clause.vE Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8c2007/12/1409/03/2007 16:49:33 EDTYes E Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8c43a8c143a8cr formally defined.d11g5591perability.,d12g5590jjDelete all "shall" statements and conformance requirements for this clause and all service specifications.wDeferred 2007/11/1407 16:49:33 EDTYesynwpqos^WqualityWqueryOWgW Wradius3WrangeWre-orderedWreadabilityWWWWWWWedWreadabilityWWabilityWWWaobing3Vre-orderedWreadabilityWWiaobing3Vre-orderedWreadabilityWWery indications from the link layers. d611g4991j"Remove the whole section. (7.3.10)v7/11/2909/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_71`54a7.3.10cA MIH is not the only way through which the higher layers and link layers interact with each other. User place functions don't need MIHF involvement. It is logical and perfectly possible for upper layer buffers to receive frame delivery indications from the link layers. d611g4991j"Remove the whole section. (7.3.10)v 21:41:08 EDTMarkedYesst^ Technical_72`54a7.3.11c 2007/10/07^technicalዃፃᎃᏃᐃᑃᒃᓃᔃᕃᖃᗃᘃᙃᝃឃៃ᠃ᡃᢃᣃᤃ᥃ᧃᨃᩃ᪃᫃ᬃᭃᯃᰃ᱃ᲃ᳃ᴃᵃᶃ᷃ḃṃἃῃÃăŃWɃ̃̓΃уՃփ׃ۃ܃  &',-/01245678=>?@ABCDEFGHIJKLMNOPQRSUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃Ⓝ┃⡃⢃⣃⤃⦃⧃⨃⫃⭃⯃ⲃ⸃⹃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃʃ˃̓΃σЃ҃ӃԃՃփ׃؃كۃ܃݃ރ߃l$ jandWWW W!W"W#W$W?WCWDWHWMWRWSWTWVWZW\WaWhWlWqWrWuWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWanditsrepresentationVorrect in name or in placement. MIH_Link_Up.indication is from MIHF to MIHF user, not MAC-WLAN to MIHF or PoA-WLAN to PoS-WLAN.d178g4775j@Expand the block to properly include the link and MIH primitives 2007/09/1709/13/2007 13:56:26 EDTYescThere are two places where the MIH_Link_Up is used. Neither of which are correct in name or in placement. MIH_Link_Up.indication is from MIHF to MIHF user, not MAC-WLAN to MIHF or PoA-WLAN to PoS-WLAN.d178g4775j@Expand the block to properly include the link and MIH primitives 2007/09/1709/13/2007 13:56:26 EDTYesxEMeylemans, MarcFApproveGProducer^ EditorialaN/AcThroughout whole document - need to be consistent in the use of 'Media-Independent...' or 'Media Independent...' wording throughout the whole specd369g5233jAbe consistent - recommend to use 'Media Independent&' (no hyphen)p use no hyphen{k) done 2007/12/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_13`10a5.1.4c3&and parameter extraction commands - missing hyphend368g5234j$add hyphen to 'parameter-extraction'{k) done 2007/12/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_6a3cPNo definition for Access Router but it is extensively used in all the primitivesd367g5235jDefine 'Access Router'p#added the definitions from RFC4066.{k) done 2007/12/1909/16/2007 02:47:09 EDTNooooEMeylemans, MarcFApproveGProducer^ Editorial_13`10a5.1.43EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_2`43a1.3c"The framework presents the media-independent handover (MIH) reference models for different link layer technologies." Seems somewhat awkwardd545g5057jq"The framework presents media-independent handover (MIH) reference models for different link layer technologies."{k) done 2007/12/1909/16/2007 15:56:25 EDTYesEColban, Erik AF DisapproveGUser^ Technical_5`1a2cNo references are provided despite the fact that this standard is referencing 802.1, 802.3, 802.11, 802.16, and unknown 3GPP and 3GPP2 specifications.d544g5058jComplete the reference list. Wherever the text references another document, add a reference to the corresponding entry in the reference section.psuperceded by 497v497w Supercededy Ref Cmt 497{l) none needed 2007/12/1909/16/2007 15:32:58 EDTYes EDTYesEColban, Erik AF DisapproveGUser^ Technical_31`456 clinkhWkWlWmWtWuWvWwWzW{W|W}WWWWWWWWWWWWWWWWWWWW%W(W+W,W2W7WBWJWLWWWZW\W_W`WaWlWnWoWsWvWzWWWWWWWWWWWWWWWWWWWWWWWWWWWW WsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWrWsWsWsWsWsWsWsWsWsWrWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWsWthenameaVVchangedescriptionofsourcelinkidentifiertospecifiesthVVVV AvA8Change as follows: "3.44 service primitive: Conceptual abstraction describing the interaction between an upper layer user and the present layer in the provisioning 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."8wAgree{k) done 2007/12/1909/16/2007 06:10:15 EDTYessF DisapproveGProducer^ Technical_8`27cSub-clause 3.40: A "protocol data unit" (PDU) refers to a packet produced by a protocol for exchange between the protocol's peer entities. The upper-layer user data exchanges between layers at a SAP is referred to as a "service data unit" (SDU).d460g5142jCorrect definition of "protocol data unit". A possible definition is: "Packet produced by a protocol for exchange between the protocol's peer entities."wAgree 2007/11/1409/16/2007 06:10:15 EDTYesCE Feder, PeretzF DisapproveGProducer^ Technical_127`32Lccollapse%WcollectingWcollectionGWcolumnWWW}WW}W}W}W}W}W}W}WWW}W}W}W}W}W}W}W}W}W}W}W}W}W}WWW}W}W}W}W}W}W}W}W}W}W}W}W}W}WWW>W@WWW}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?W@WAWBWGWTWYW_WgWiWkWtWxWWforexampleassumeanddescribeherewhatevermipshopwillpߞVforexampleinthespecificcaseof802.11statethatmihre߮Vforexampletheieee802.11lowerlayersarethemacsublayebVforexampletheoccurrenceofahandoverofamobilenodefrZVforexamplewirelessnetworkscouldbeenhancedforcarryingߠVformUWformalߞW߭Wmj!Updtae figure-7 and section 5.5.3vby TGu submissionw Superceded{l) none needed 2007/12/1909/16/2007 13:58:33 EDTMarkedE Gupta, VivekF DisapproveGGeneral Interest^ Technical_282aAnnex JcHDelete Annex J as it is redundant and not required in the specification.d519g5083jDelete Annex JwAgree{k) done 2007/12/0209/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_224aAnnex FcHDelete Annex F as it is redundant and not required in the specification.d518g5084jDelete Annex FwDisagree{l) none needed 2007/12/0209/16/2007 13:58:33 EDTYes E Gupta, VivekF DisapproveGGeneral Interest^ Technical_221aAnnex EczMove References (Bibliography) to section 2 Normative References. Why is this buried at the end instead of being in front.d517g5085juMove all normative references to section2. Consider moving this part to somewhere earlier in draft and delete Annex E148TjdifferentWWW WWWdirectW'WdirectionIWWdirectionsWdirectlyWWdiscardWWWWdiscoveredbWdiscoveryWWWWWWWWdiscuss᪃WWWWdiscussandadopt21-07-0317-00-0000-sinformationieVdiscusscontribution21-07-0315-00-0000-dinformationsupporVdiscusscontribution21-07-0316-00-0000-mcapabilitydiscoveVdiscussspecificsolutionaspectsforbothforsingleradio/Vdiscussion<WhWWWdistinguish/Wdistinguishbetweenbasicw-cdmafeaturesbutremoveanyref/VdoW W&W8W?WiWdocWdocumentWW&WiWdocumentsWdoesW4W7WwWdoesn't&W]WwWdoing(Wdone)WdownWW2WaWdowngrade&WdraftW W'WWWWWdrivenwWdstwWdueWduringbWW 'vAReplace "The source MIH node may at most make two retransmission attempts in addition to the first attempt for an MIH protocol message with the same Message-ID and the same Transaction-ID." With The source MIH node shall retransmit an MIH protocol message with ACK-Req bit set until it receives an acknowledgment or the number of retransmissions reaches its maximum value. The maximum number of retransmissions can be reconfigured depending on implementation. The default value of maximum B%number of retransmissions is two (2).w PrincipleyRef 2. (superceded){k) done 2007/12/1909/14/2007 02:24:47 EDTYes imes? Such variables are usually expressed in a MIB. What about the possibility of aggregated Ack messages?d231g5371jRestrict description of MIH Acknowledgement operation to the messages exchange. Implementation details should be left out or else in the Annexpsuperceded by comment #2v comment 2w Superceded{k) done 2007/11/30`202conmessagesmihmnhocommitrequestandmihmnhocommitinVoneWWWWWWWWW WWW.WKWLWMWNWRW[W]WeWnWoWWWWWWW5WWWWWWWWWone-octetWone-to-onekWlWmWone/twoWongoingWonlyWWWWWWWWWWWWWW,W6W<W[WcWeWuWWWWWWWWWWW'W5WNWWWWWWWWWWWWWWWWWWWWWWWWW'Wright"Wrlc)Wroll-up&WrollbackWrouterYWZW[WݍWrowWrrc"Wrscp WrspWruleܺWrulingWsnWsacnWsameܟWܠWPWSWYWZW[WWF.ERudolf, MarianF DisapproveGProducer^ Technical_32`44a5.7.2cAI always thought it is possible to use MiH signalling exchanges through data frames of Ethertype XYZ even in 802.11 State 3 and that the action frames to carry MIH signalling in State 1 are a specific tool to optimize MIH discovery a.k.a MIH IS before authentication and association.d507g5095jons contexts, deletes all existing registrations to peer MIH entities and so on." vMIH NMS SAP has been deletedw Superceded 2007/12/0109/16/2007 12:18:13 EDTMarkedNoERudolf, MarianF DisapproveGProducer^ Technical_32`44a5.7.2cAI always thought it is possible to use MiH signalling exchanges through data frames of Ethertype XYZ even in 802.11 State 3 and that the action frames to carry MIH signalling in State 1 are a specific tool to optimize MIH discovery a.k.a MIH IS before authentication and association.d507g5095j10/07 2007/10/07EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_55`3a6.5.6.3cI assume that the MIIS schema definition is normative. If so, it should not be included in an annex, which is generally intended for additional information.d316g5286 pages. This applies to all of clause 7.d317g5285jAAdd a column which includes the reference to the clause where the primitive is defined and if possible, a reference to other pertinent normative information. An example of one of these tables is Table 12 on page 62. Include similar changes to clause 7.3 - 7.6pOalso re-ordered some primitive definitions in 7 to match the order in the table{k) done 2007/12/0109/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_55`3a6.5.6.3cI assume that the MIIS schema definition is normative. If so, it should not be included in an annex, which is generally intended for additional information.d316g5286UE$EGiesberts, Pieter-PaulF DisapproveGProducer^ Technical_31cA6MIH_NET_SAP defines the interface between an MIHF implementation and various local transport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. In the contrary, it would impose needless constraints to the implementation.6d234g5368 implementation.\d235g5367j3remove definition and all occurences of MIH_NMS_SAPwAgreey Ref Cmt 106 2007/11/1809/14/2007 03:15:28 EDTMarkedYes$EGiesberts, Pieter-PaulF DisapproveGProducer^ Technical_31cA6MIH_NET_SAP defines the interface between an MIHF implementation and various local transport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. In the contrary, it would impose needless constraints to the implementation.6d234g536836`20umcmihheaderisafixedlength8bytesHVmihisabouthandoverbetweendifferentaccesstechnologiesVmihisnottheonlywaythroughwhichthehigherlayersandVmihlinkparametersreportindicationisnotamessagebetweaVmihn2nhocommitcurrentlydoesnotallowtheoptionofreqVmihn2nhocommitdoesnotallowtheoptionofrequestingreVVVmihn2nhocommitshouldalsoallowtheoptionofrequesting Vccurrences 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_273`24or TLV in the MIH_MN_HO_Candidate_Query Response message, so why is it there?d181g4772jDelete both occurrences 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_273`24F DisapproveGGeneral Interest^ Technical_273`24d180g4773 2007/09/1709/13/2007 13:56:26 EDT7 ccontents$WWWWWcontext0WWW<WcontinuallyWcontinueWWcontinuesWcontinuityWcontradictory?WcontraryWWWW#W$WWWcontributionWWWWcontrolWwWWWcontrolledWconventionhWconventionalWconventionsW WconveyedWcopy WcornerNWcorrectWWWSW0WZW\W^WcWuWWWWWWstofabbreviationsVcouldWW WeWgWqWwW|WWWWcountWcounterWcounterpartWcountersWcoverageWNWcoveredWcpichWcreatetWcreates[WcriticalWWcrossTWVWcross-referenceWcrossed[Wcrossing[WcsWWcuriouslyWcurrentWW=WCWDWEWaWzW{WWWWWWW*WMW܎VdisapproveăŃƃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ ogies or just to 802.11 ?d477g4476jDefine an actual relationship between Channel_ID and operating frequencies similar to ARFCN in GSM/W-CDMA. Or, delete it and re-use the existing access technology-specific identifiers like ARFCN. 2007/09/1709/16/2007 07:13:12 EDTNoߩERudolf, MarianF DisapproveGProducer^ Technical_181`19c;LINK_PARAM_UMTS is sort of wrong and needs to be corrected.d476g4477ss technology-specific identifiers like ARFCN. 2007/09/1709/16/2007 07:13:12 EDTNoߩERudolf, MarianF DisapproveGProducer^ Technical_181`19c;LINK_PARAM_UMTS is sort of wrong and needs to be corrected.d476g4477 2007/09/1709/16/2007 07:13:12 EDTYes|1j8.3.4targetdecisionandhandoverexecutionV8.3.5W8.3.5resourcereleaseV8.6WWW8.6.3.3LWXW8.6.4.2W802WW802.1W802.11WWWWW&W(W7W8WWWWWWW802.11-2007 Whe MIH_MN_HO_Complete message may be sent to the target POS as per page 228d185g4768jAdd R2 2007/09/1709/13/2007 13:56:26 EDTYessapproveGGeneral Interest^ Technical_281`6cLThe MIH_MN_HO_Complete message may be sent to the target POS as per page 228d185g4768jAdd R2 2007/09/1709/13/2007 13:56:26 EDTYes767jDelete R1 and R3 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_281`6cLThe MIH_MN_HO_Complete message may be sent to the target POS as per page 228d185g4768jAdd R2 2007/09/1709/13/2007 13:56:26 EDTYes09/13/2007 13:56:26 EDTYesd184g4769It cpleaseclarifytherelationshipbetweenthemihlinksapandVpleaseclarifywhichprimitiveismandatoryandwhichisoptVpleaseclarifywhichprotocolmessageismandatoryandwhichVplrWWpluralWWWWpoaWWWWWWWWWW WbWkWlWmW|WWWWWWWWW7WwWWWWWWWWWWWWWpoa-wlanZW\WpoasW88 line 13 change Table E-2 to K-2; line 40 remove transfer from CoS Packet Delay Jitter; 2007/09/17<JmichaelWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmurroWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmontemurromichaelVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVmylesWWWWWWWWWWWWWWWWWWWWWWWWWWmylesandrewfVVVVVVVVVVVVVVVVVVVVVVVVVVnadaWWWW;jtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWWW"W#W%W&W'W*W+W/W1W3W4W5W7W9W:W=W>W@WCWDWEWGWHWIWJWKWLWMWNWZW^W`WaWbWcWdWeWfWgWkWlWmWtWvWwWxWyWzW{W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWjentityWWWWWWWW WWWvWWWWW!W"WWWWWentitymihbasichttpwwwmihorg/2006/09/rdf-basiVentrieskWlWmWWWentryWW8Wenumerated^WenumerationaWequalwWequationWerroneousWerrorFWWWWWQWesW&WessWWessentialWestablishedW0W7WeventWWWWW]WbWwWWeventsWWW?WtWWWeventually5W7Weverywhere'WevidentWexampleWW WWW&W'W)W+W7W8WZWWWexamplesWWW<Wexcedes0WexcellentWexceptionW7WexchangeBWwWexchanged>Wexchanges WW7W>Wexchanging]Wexclusively7WexecutionWvWexistWWexistingWWW1W=qE Cypher, DavidF DisapproveGGeneral Interest^ Technical_186`36cvIs it the number of classes of service (COS) as the definition states or is it the number of quality of service (QOS)?d157g5445j9If former, then change QOS to COS and the same on line 27p0Changed to CoS and also updated the description.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes :56:26 EDTYes qE Cypher, DavidF DisapproveGGeneral Interest^ Technical_186`36cvIs it the number of classes of service (COS) as the definition states or is it the number of quality of service (QOS)?d157g5445j9If former, then change QOS to COS and the same on line 27p0Changed to CoS and also updated the description.wAgree{k) done 2007/12/1209/13/2007 13:56:26 EDTYes as the definition states or is it the number of quality of service (QOS)?d157g5445j9If former, then change QOS to COS and the same on line 27wAgree{i) to do 2007/12/07ee 2007/11/06csignalWWsignalingWsignallingW'W7WsignificanceWWWWWsignificantW Wsimilar WW/WWW%WWWsimilarly^WWsimpleWsimplificationWsimplifiedWsimplifyWsimplistic7WsimplyW$W7WeWWWWWsinceWWWWdWkWlWmWrWsWuWWWWWNWWWWWsinceavailableresourcesareonapercandidatelinkbasiskVlVmVsincenethocommitcontainsactionstoeffectthehandoveruVsincetheieee802.11smecanbeconsideredtobethemobiliVYes )ojDelete this parameter.ppbut kept the same param in N2N response/confirm as it is unclear whether the comment applies to that case or notvMake this optionalw Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNopERajkumar, AjayF GProducer^ Technical_113`2426cWhat does "This primitive may trigger MIH User to initiate the process to get IP address to be used in the target depending on the received candidate query response" mean? Seems to be an unrelated statement.d414g5188j Delete line.wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo qERajkumar, AjayF GProducer^ Technical_114`112cThese parameters are not available for network initiated handovers (see page 107, Section 7.4.19, Net_HO_Candidate_Query.request) but, they could be.d413g5189wOut of Scope/Unresolvable{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNo rERajkumar, AjayF GProducerGProducerGProducerGProducer/11/185cidWWWWWW1WIWJWwWxWyW|WWWWW7WvWWWWWWWideaW7WWideally.WidentifiedJWWidentifierWWWWWCWDWEWKWLWMWNWzW{WWWWWW1WWWWidentifiersWWW4WJWBWWWidentifiesCWWWWWWWWWWWWWWWWWW W WW'W.W1W]WfWgWnWoWrWsWtWuWvWiftheintentisfortwomihfstomutuallydiscovereachothfVimminentWW_WwWimplementationWWWWWimplementationsWimplementing/Wimplementor'W,W7WimplementsWimplicitlyW WimpliesWimplyWimportantWWWimposeWWimprove%WW:DGje@eitherchangecurrentlinkidentifiertosourcelinkidentif@/eitherremovethemihnethocandidatequerycommandorbett@entity@establishment@exists@expected@qfigure@Xfixthisbasicmisunderstanding@follows@forexampleassumeanddescribeherewhatevermipshopwillp@formalHformat@function@ g@handovers@hoghooghi@Cid@identifiers@ifformerthenchangeqostocosandthesameonline27@iis@inbothline38and37changedefaultvalueformime-typefro@[includeincludethingslikecontexttransferandbearerpathsetupa@incorporating@increasing@WTWWclearlydefinetheinfoquerybinarydataieorifitexistsad>Vclearlystateif802.16providesamechanismsimilartothe߃Vclears߉Wclever߅Wcode߫WWlWcodesWcoding;WcollapsedߜWcolumnHWlWoWWIycdeleteannexjasitisredundantandnotrequiredinthespVdeletingWWdelivered WWWWdeliveryWdeltaWdemandsWdemonstratesWdenoteWdependantWWdependentWWW7WdependingWW&WpWWW#WWWdependsW WdeployedWdeployment&WWdeployments WdeptWderivedWdesciptionWdesciptiononlinkhandoverimminentanditsmihcounterpartVdescribe$W7WwWWWdescribedW=WWWdescribesW>WAWwWWWdescribingWdescriptionWWWWW+W7WCWKWLWMWNWWWWWWWWWWW%W.WWWdescriptionsWWdescriptiveW-W.WWdetailedWdetailsWWWWdetectbWdetectedbWdetermine WdeterminesWQECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_102`30a7.4.17c9(Kenichi) LINK_ACTION_REQ should be LIST(LINK_ACTION_REQ)d445g5157j change it.p4Changed in section 7, Verified message in section 8.wAgree{k) done 2007/12/1909/16/2007 03:35:02 EDTNo RECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_103`33a7.4.18cK(Kenichi) MIH_Scan is not needed because it is one of the MIH_Link_Actions.d444g5158jKRemove Section 7.4.18 and also related section, datatype(MIH_COMMAND_LIST).p=removed MIH_scan (also fixed some inconsistencies in Table 5)wAgree{k) done 2007/12/1909/16/2007 03:35:02 EDTNo o o know which link is currently being used.d525g5077jDelete CurrentLinkIdentifier from all MIH Handover primitives. A SourceIdentifer may be included if required wherever appropriate. 2007/11/1409/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral InterestWW1jClarify the figure or the caption. If the caption is clarified, then a figure should be added which shows the mobility management architecture that 802.21 specification is based upon.v"Figure 1 shows the placement of the MIHF within the mobility management protocol stack of an MN or network entity." Remove Mobility Management from the above sentence.w Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ TechnicalaGeneralckI do not see a way for the network to command a mobile node to power up or down a specific radio interface.d73g5529jAdd this capability.vmThe MIH_Link_Actions (page 102, sub clause 7.4.17 ) primitive in the current draft provides this capability.wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ TechnicalaGeneralaGeneralaGeneral mobility management architecture that 802.21 specification is based upon.W&F DisapproveGProducer^ Technical_203`9c#NETWORK_SECURITY definition missingd262g5340jAdd definitionvHDelete NETWORK_SECURITY_IE Can be added later if definition is availablew Supercededy Ref Cmt 532{l) none needed 2007/12/1909/14/2007 14:42:22 EDTYes   disapproveJ$P disapproveJhendersongregorys  disapproveP 9 disapprove P kwakjosepha  disapprove @ 9 disapprove  @ kwakjosepha  disapproveQ disapproveQsreemanthulasrinvias  disapprovee disapproveecflagWWWWflexibilityW(WflexibleWfloatWflow*WWflowswWWWfmip&Wfna^WcWfnaisusedwhichiscorrectfortheoriginalrfc4068howev^VcVtobemadeconsistentVforWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW%W'W+W/W0W4W6W7W:W=WBWCWGWJWKWLWMWNWYWZW[W\W]W^W_WcWeWfWqWrWsWxWyW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWa3cIEEE 802.11u now supports a native GAS (Generic Advertisment Service) query mechanism, which may provide useful information to the MIHF IS. Comment forwarded by IEEE 802.11u chair on behalf of IEEE 802.11u Ad Hoc Meeting, 30th August 2007.d359g5243j[Please consider adding new entries to the MIHF IS, based on the updated IEEE 802.11u draft.pZ-HESSID has been added as an example -the other proposed IEs will be defered to next roundvNo list of IEs providedw Principleydeferred{k) done 2007/12/1909/16/2007 01:46:33 EDTNopcMIH_Configure_Link command is not defined. There a MIH_Link_Configure_Threshold specified both for SAP primitives (in section 7) and NIH messages in section 8.d280g5322jPReplace all occurrences of MIH_Configure_Link with MIH_Link_Configure_Threshold.v"Add MIH_Link_Action to the table 5wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTYesEZuniga, Juan CF DisapproveGProducer^ Editorial_288`14cReference to table E-2d279g5323jReplace reference by table K-2{k) done 2007/12/1909/14/2007 17:39:46 EDTNo EZuniga, Juan CF DisapproveGProducer^ Technical_288`20cZTable K-2 does not provide a very comprehensive mapping between 802.21 and 3GPP parametersd278g5324jReplace the column that provides the mapping between 802.21 and 3GPP technologies by a different table as defined in 21-07/321r01-07/321r01-07/321r0YesE Julka, VibhorF DisapproveGProducer^ Technical_44`19a 6.4.3.1.1E Julka, Vibhor8ca6.3.2ⴃ6.3.4.1ᶃ᷃ḃփ,6.3.5ᴃᵃ+6.46.4.1⚃ⳃ!㟃㩃6.4.26.4.3*6.4.3.1.16.4.3.26.5.16.5.2 Ճ6.5.3VW㾃㿃ۃ6.5.4ⱃԃ6.5.566.5.5.2᱃ᲃ᳃Ӄ㴃㵃㶃㷃㸃㹃㺃㻃㼃6.5.6.3҃4564311L6536552㊃677 7.1W7.27.2.2.1؃7.2.2.27.2.3.17.3.10᫃ᬃ (7.3.117.3.11.17.3.127.3.14.1.227.3.2.2.27.3.3.1.17.3.47.3.4.27.3.57.3.5.1ty at a different layer than the STA <=> MIIS, and as such, I do not see how the (future) securBity will work.d275g4029 2007/09/1709/14/2007 16:50:16 EDTYes- 7jCEections 5.5.2, 5.5.3, etc, should summarize it here in section 5.1.7.!psuperceded by 300vSection 5.1.7 has been deleted.w Principle{l) none needed 2007/12/1909/16/2007 07:13:12 EDTYes8ERudolf, MarianF DisapproveGProducer^ Technical_5`4a2c%Why is there no normative reference ?d470g5132jInlcude as a minimum the latest 802.11 roll-up and for example 802.11u as amendment incorporating 802.21 support. Do similar for 802.16-20004/d/e and the 3GPP air interface specifications.psuperceded by 497vby 497w Supercededy See Cmt 497{l) none needed 2007/12/1909/16/2007 07:13:12 EDTYes he LLC in the SGSN sitting on top of the RLC/MAC stack in the BSS. Does this still qualify as link layer ?d471g5131j7:13:12 EDTYes7ERudolf, MarianF DisapproveGProducer^ Technical_13`36a5.1.7ces, use the right name of the scrambling code identifier in the RRC specifications, cite it. 2007/10/07NB  cA'"If a newly arrived MIH protocol message is found to carry the same Transaction-ID of an earlier arrived message, the destination MIH node shall consider the new message as a retransmitted copy of the earlier arrived message. This couples a loose spec "is found to" with a normative requirement.'d3g5599jEither provide a normative requirement for the number of past messages that need to be recorded for the purposes of duplicate detection, or loosen the normative requirement.vAReplace "If a newly arrived MIH protocol message is found to carry the same Transaction-ID of an earlier arrived message, the destination MIH node shall consider the new message as a retransmitted copy of the earlier arrived message. In such a case, the destination MIH node shall respond with an acknowledgement message even though an acknowledgement message may have been sent earlier for the same MIH message. This is to safeguard against the cases wherein the first acknowledgement message *XcthediagramdoesnothaveanymihusersaretheupperlayersVthedraftisveryverboseandinsertstoomanyout-of-scope<VthedraftpayslipservicetosecurityyetalargepartoftVtheentireannexbispoorlyorganizedthegroupingisnotcVtheentireannexbispoorlyorganizedthegroupingisnotoV various layer management entities (LMEs), and similarly setting the value of layer-specific parameters." All MLME functions are genarated 802.11 SME, and as suchB invoking them from any other layar violates the 802.11 architecture. When the 802.21 plays in the context of the 802.11 SME, then it becomes reasonable for the 802.11 WG to architecturally define 802.11 specific interfaces for 802.21.cshouldbemovedafter6.3.3discussionVshouldnotreferencemnsincethisisan2nmessagedVshouldeWshouldn'tfWshowWWWWWshowingWWWW!W"WWWshownWWshowsWWW*WwWWNWWWWWsibWsideW!W}WsidesIWsigWWPE. 2007/09/1709/16/2007 03:38:14 EDTYes߿E Feder, PeretzF DisapproveGProducer^ Technical_150`60c'MIH header is a fixed length (8 bytes).d454g4499j5Remove reference to "variable octets" from the figure 2007/09/1709/16/2007 03:38:14 EDTYesE Feder, PeretzF DisapproveGProducer^ Technical_150`40 2007/09/1709/16/2007 03:38:14 EDTYesE Feder, PeretzF DisapproveGProducer^ Technical_150`40d453g4500 2007/09/1709/16/2007 03:38:14 EDTJ'EWilliams, Michael GF DisapproveGProducer^ Technical_121a7.4.23cWhy there is a separate MAC_ADDRESS field in MIH_MN_HO_Commit.request/indication primitives (and also in MIH_MN_HO_Commit request message)? Why are the Link and PoA differentiated?d584g5018jchange the type to LINK_IDvchange the type to LINK_ADDRESSw Principle 2007/11/1809/16/2007 16:08:43 EDTMarkedYesEWilliams, Michael GF Disapprove_121a7.4.23cWhy there is a separate MAC_ADDRESS field in MIH_MN_HO_Commit.request/indication primitives (and also in MIH_MN_HO_Commit request message)? Why are the Link and PoA differentiated?d584g5018jchange the type to LINK_IDvchange the type to LINK_ADDRESSw Principle 2007/11/1809/16/2007 16:08:43 EDTMarkedYesEWilliams, Michael GF Disapprovee to LINK_IDvchange the type to LINK_ADDRESSw Principle 2007/11/1809/16/2007 16:08:43 EDTMarkedYesEWilliams, Michael GF Disapprove14Wk cCI skipped over it ?d512g5090jADefine unambiguous mappings between 802.21 link threshold values and parameters (example: THRESHOLD) to the measurements configured through LINK_PARAM_TYPE. Specifically for 2G/3G cellular, please consider the following 2 cases: MN reported measurements for which precisely defined reporting ranges and accuracies exist (see 25.133 and alike) and network-side only measurements (a.k.a from BTS) where no standard defines anything, and mapping of reported measurements like UL TrCh BLER to valueBMs for a network-side MIH function may need to make some clever assumptions...;vr some subparameter of it do the job ? 2007/11/1409/16/2007 12:18:13 EDTNoERudolf, MarianF DisapproveGProducer^ Technicald / new IP address only ? For cellular, could allocated PDP contexts or some subparameter of it do the job ? 2007/11/1409/16/2007 12:18:13 EDTNoERudolf, MarianF DisapproveGProducer^ TechnicalgF DisapproveGGeneral Interest^ Technical_140`10cNMS is used for network management and is to be a stand-alone system. It means that having MIH_NMS_SAP for the interface with the NMS doesn't seem to be appropriate.d641g4961jDelete section 7.6v%This would apply to the entire draft.wAgreeyRef 106{l) none needed 2007/12/1909/16/2007 23:46:35 EDTYes s 0pstyle9WsubclauseW WWWWWsubnetWsubscriptionW WsubsetWsuchWWsuggestWsupercededWWWWWWWWW WWW(W+W7W8WWWWWWWW WWW#W'WMWWWWWWWsupercededby106VV V#VVsupercededby3007Vsupercededby300471Vsupercededby35Vsupercededby497VV8VVVVsupercededbychangefrom334 Vsupercededbychangefrom343+Vsupercededbychangefrom45VVsupercededbychangesfrom472Vsupercededbycomment10VVVsupercededbycomment11VVVVMVVVsupercededbycomment2'Vsupercededbycomment454VVsupercededbycomment59VsupercededtheconcernedtextisremovedbyanothertechcomVV`DTstephensWWW W W W WstephensadrianpVVV V V V VterryEWFWGWHWtonyWWulisesWvanWWvanleeuwenrichardmVVvibhorWWWWWWWWWWWWWWWWWWWWvivekWWWWWWWWWWWWW WwilliamsWWWWWWWWwilliamsmichaelgVVVVVVVVxieWWWWWWWWWWWWWWWWWxieqiaobingVVVVVVVVVVVVVVVVVyonghoWWWWWWWWWyoshihiro7W8W9W:W;W<W=W>W?W@WAWBWCWDWDWWzunigajuancVVVV"c8.6forextendibilityofmihthereisaneedtoallowdefiniV8.6.3.15W8.6.3.6WW802WWW W7WWWWW802.1WWW802.11WWWWWWWWWWWWWWW1WWWWWWWWWWWWWWWWW1-2007W802.11gW802.11uWWW802.15WWW802.16WWW WWW802.16eW802.1abW802.1xW802.21WWWWWWWW&W6W7WWWWWWWWWWWWWWWWWWWWEWWWWWWWWWWWWW802.21miissupportsstaticinformationparametershoweverfV802.21--yetW802.21-parW802.3WWWW9WW9.1W9.2W98eWjperiodicallyWpermittedWperspectiveWW@WpertinentWphyWWpickWzWpickasingletermanduseitconsistentlyVpickonemethodanduseconsistentlyzVpics%W&WWWpinWpkmWWW2WWpleaseclarifyandremoveoraddipsubnetprefixinformatioVpleaseconsideraddingnewentriestothemihfisbasedontVpleasedefinesomewheretheactionsthatanmihprotocolentVpleasesee309VVpleaseseethecontribution305Vpleaseseethecontribution306change1Vpleaseseethecontribution306change2Vpleaseseethecontribution307Vpleaseseethecontribution308VVpleasestateclearlyifmihsignallingexchangesusingdataVpoaWWbWkWlWmW|WWpoasbWpoorWposWWpositiveWpossibilityW]WfWpossibleWWBWpossibly.WWWmcimplementationsWWWWWimplementedWWWWimplementing/WWimplementor'W,W7WWimplementorsWimplementsWimplicationsW WimplicitW/1709/13/2007 16:03:47 EDTYesEOhba, YoshihiroF DisapproveGProducer^ Technical_80`60a 7.4.1.3.1c0Supported Transport List should not be optional.d203g4750entifiers in MIH_Register.request.d204g4749j/Adopt 21-07-0226-00-0000-MIH_Registartion_Nits. 2007/09/1709/13/2007 16:03:47 EDTYesEOhba, YoshihiroF DisapproveGProducer^ Technical_80`60a 7.4.1.3.1c0Supported Transport List should not be optional.d203g4750EOhba, YoshihiroF DisapproveGProducer^ Technical_80`60a 7.4.1.3.1c0Supported Transport List should not be optional.d203g4750 2007/09/1709/13/2007 16:03:47 EDTYes (vpagepage14line-36Vpage150secton8.3.1Vpage41line57<Vpage42line2<VparagraphWWWWparagraphisdeletedVparamW2W^WaWparameterWWWWWvWWparametersEW^WfWWWWWWWparameters/valuesWparenthesisWpartWWWWWWWWpartnerWWpartnersWWpassWpassedWpccpch2Wpdp0WpeersWpeopleWperWIWWWWWperformanceWperiodWperiodicaWperspectiveWWW@WpertainWpgWW^WEWWWpg134line6only1typeshouldbespecifiedVphy<WpickWpicklowercaseV jjcapableWWcapacityWcaptionWcarriedWcarryWtWcarrying)W/W/W/W/W/Wlysync/W/W/W/W/Wsync/W/W/Wsync/W/Wsynchronous-W-WfWfWfWfWfWfWfWfWcodingfWfWfWfWfWfWfWfWyjcorrespondingWgWWWWcosWWQWjWkWqWcos-idWcostWcouldW W&W)W+WgWwWWtWWcouldtheybeforeasyofmappingtVcouplewWcoverageWcpich2Wcrd&WcreateYWWWcrossWcross-referenceWcrosses`WcrossingaWcs&W;WWcurrentCWDWEWzW{WWWWWWWWWWWcurrentlinkidentifieWcurrently`Wd%WW4W5WdataWWWWWWW(WBWXWZWWW5W=W^WcWWWdatatypeOWRWdatatype1Wdatatype2Wday'Wde-emphasizeWWde-emphasizemihfdiscoveryasseparatemihservicemanagemeVVdecidingWdecisionWWWWWWWWWWWWWWWWWWWWWWzjunderlying W7WunderscorerWunified@WuniformWuniqueIWunitBWunitsWunrecognizableWWunsignedW1Wunsignedint2unsignedint21VunsolicitedWWWunsubscribeWWunsubscribedWunsubscriptionWuntilWuntilizeWWup W7WaWW+W,WWupdateWWWWW)W^WcWWupdatesectionwithtextonsecurity)VupdatethedefinitionoflinkidtoindicatethatthelinkaVupdatethediagramanddescriptiontoincludethe802.11autVupdatethenormativereferencelistVupdatethestatediagramtomatchthetextdescriptionVVupdatedWupdtaeWupdtaefigure-7andsection5.5.3VuponWtWWupperwWWurlWusage(WWusagesW23:32:08 EDT@E Cheng, HongF DisapproveGProducer^ Technical_13`57a5cIn the overview subclause 1.3, it is clearly stated that the handover is not limited to mobile case. Why there is a specific subclause 5.1.9 talking about movement caused handover? Is this going to be different from other type of handover?d495g5107j;Merge the text to subclause 5.1.1, or remove the subclause.v Delete 5.1.9wAgree{k) done 2007/12/1909/16/2007 08:19:02 EDTYes E Cheng, HongF DisapproveGProducer^ Technical_118`8a7cRThe MIH_xxx.request should nevery be used by the MIHF. It is used by the MIH user.d494g5108j Fix the textp'Probably should do a draft review also.v.Change this in all places in draft (carefully)wAgree{k) done 2007/12/1909/16/2007 08:19:02 EDTYes !E Cheng, HongF DisapproveGProducer^General_1`31a1cWAWWtransitionWWWWWWWtransitionsWtransitsWtranslateWWtranslationRWtranslatorRWtransmissionWW(WMWtransmitWWW WtransmittedW0WtransparentW00-d4W21-07-0316-00-0000-m3W21-07-0317-00-0000-s2W21-24W22MW228W23eW230WW231W24LW25߅W25.133߅W252W26rW߽W27iWrW$WWWWW28-31W2nddW2sAW3W߈WߊW߫W߬WߴWRW|WWW7WDW3.3:WW4eastwoodlesterfVVVVVtVntiexVaddperiodtVtVtiexVaddperiodtVtVaddr2CVethiscapabilityandanyassaddperiodtVaddr2CVCVaddthefollowinglinkactiontypelinkhandoveralsoaddth&Vsoaddth&V&Vhefollowinglinkactiontypelinkhandoveralsoaddth&V&Vhefollowinglinkactiontypelinkhandoveralsoaddth&V&Vhefollowinglinkactiontypelinkhandoveralsoaddth&V&Vypelinkhandoveralsoaddth&V&Vactiontypelinkhandoveralsoaddth&V&Vhefollowinglinkactiontypelinkhandoveralsoaddth&V&Vhefollowinglinkactiontypelinkhandoveralsoaddth&V&Viontypelinkhandoveralsoaddth&V&Vaddth&V&VݝVaddthemܬVVaddtosection8.2.3.5.1page149line42sincesendingorlVaddwwancellidtothelistofentriesonb-9ݳVaddedWjrestrictdescriptionofmihacknowledgementoperationtothe'VresultWWeWWWresultingWresultsWWretentionWretransmissionW007/09/1709/14/2007 14:42:22 EDTNoE Jette, AlanF DisapproveGProducer^ Editoriald (validated).d258g4046j$remove MIH_NET_SAP from the standard 2007/09/1709/14/2007 14:42:22 EDTYesE Jette, AlanF DisapproveGProducer^ Editorial_2`12c^Word "han-dovers" is split across 2 lines and the hyphenation appears to be in wrong position.d257g4047jCorrect 2007/09/1709/14/2007 14:42:22 EDTNoE Jette, AlanF DisapproveGProducer^ EditorialF DisapproveGProducer^ Editorial_2`12c^Word "han-dovers" is split across 2 lines and the hyphenation appears to be in wrong position.d257g4047jCorrect 2007/09/1709/14/2007 14:42:22 EDTNoE Jette, AlanF DisapproveGProducer^ Editoriald256g4048 2007/09/1709/14/2007 14:42:22 EDTvjdeletemihnmssapandnetworkmanagementsysteminfigure4Vdeletemihfmaydofurtherprocessingonlinklayertriggers?Vdeleteoneofthe2sentencesVdeleteorrewritethiserroneousequationVdeletepreparesresourcesrVsVdeleter1andr3TVVVdeleterefto802.11andcreateanannexassuggestedVdeletereferencceorcreatecontributionYVdeletesection5.6.2.6Vdeletesection5.6.3.2Vdeletesection7.6VdeletespacesintablesyntaxVdeletetable14andmovecontentstomediaspecficannexVdeletetargetpoaparameterandincludethepoamacaddress|Vdeletetextonlines19-47insectionb1.2VdeletethefirstlineVdeletethelinethemihuserreceivingthisprimitiveinvokejVdeletethepoalocationVdeletethepoamacaddressVdeletethesentence<VdeletethesentencesVetextthatanswerstothosequ@Vtrationbyc-nem-rspderegistrationV_padWaddWWW WAWWWWWaddtargetlinkactiontlvformnhocommitrequestVaddthefollowingdescriptioninthefunctionsubclauseVaddthefollowingparagraphattheendofthissubclauseVaddthefollowingsubclauseinmihnethocandidatequery Vaddthesourcelinkidentifierin7and8VaddthetargetnetworkinfotlvandlistoftargetnetworkiVaddedWW3WgWWWWWWW4WWaddedcountrycodeVaddedseeannexgforhowtoextendthebasicschema4VaddedtexttobeidentifiedandaddedfornowifinthefinaVaddedthedefinitionsfromrfc4066Vedefinitionsfromrfc4066VVVVVValVafterWagain_WWagreed/WAWagreedbutsincetextinthebodymaystillchangeandhence/ValgorithmWWaliceWYW2Wall^WWOWsponse periodically."d573EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_79`8a 7.4.1.1.2c$"List of supported transport types."d560g5042j6"List of supported transport types on the local MIHF."wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes s ual discovery of each other's capabilities."d561g5041j"In the case of remote discovery, this primitive may contain the SupportedMihEventList, SupportedMihCommandList, SupportedIsQueryTypeList, and SupportedTransportList parameters of the local MIHF to enable mutual discovery of each other's capabilities."{k) done 2007/12/0709/16/2007 15:56:25 EDTMarkedYes EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_79`8a 7.4.1.1.2c$"List of supported transport types."d560g5042j6"List of supported transport types on the local MIHF."wAgree{k) done 2007/12/0709/16/2007 15:56:25 EDTMarkedYes YesWWWzE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_161`37a8635c[Consistency throughout the document as to whether it is MIH_Link_Actions or MIH_Link_Actiond148g5454j$pick one method and use consistentlypuse "MIH_Link_Actions"wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes {E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_144`3a821c3guild is a noun, not a verb, so what is "to guild"?to guild"?j$pick one method and use consistentlypuse "MIH_Link_Actions"wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedYes {E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_144`3a821c3guild is a noun, not a verb, so what is "to guild"?nd use consistentlypuse "MIH_Link_Actions"wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedYes {E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_144`3a821c3guild is a noun, not a verb, so what is "to guild"?cfigure13is16pagesawayVfigure13isconfusingVfigure13isconfusingbyshowingtwounrelatedstacksV"VVfigure13isconfusingbyshowingtwounrelatedstacksshowiVfigure16isconfusingbyshowingtwounrelatedstacksV!VVfigure16isconfusingbyshowingtwounrelatedstacksshowiVfigure16isconfusingitshowstwounrelatedstacksVfigure19showsanexpandedviewofthesecondnetworkoperaVfigure22thestatediagraminfiguredoesnotmatchthedesVfigure24thestatediagraminfiguredoesnotmatchthedesVfigure26showsthemihprotocolheaderhasavariablelengtVfigure3alludesthatmihreferencepointsdonotexistaccrVfigurem-3showsamobilenodeatthecenterofacoverageaNVfigure-7WfiguresgWWfileW.WfilledWWWbVformWforthWfractionWframeWWWframesWframeworkW{jCorrect the text.pChanged to: "The MIHF is a logical entity, whose definition is independent of its deployment location which may be on the mobile node or in the network"{k) done 2007/12/1909/03/2007 16:49:33 EDTNoo14g5588jCorrect the text.{d) confer with resolution group 2007/11/2609/03/2007 16:49:33 EDTMarkedNo states that the definition of MIHF has no implications on the way the function is implemented. This is clearly not true; if it is, then the definition is irrelevant.d14g5588jCorrect the text.{d) confer with resolution group 2007/11/1809/03/2007 16:49:33 EDTMarkedNod prior to initiating any MIH protocol procedures. However, there are no conformance requirements in Clause 6 for these "service management procedures", I.e., no statement of exactly what procedures *shall* be implemented by a conformant device. Thus, the service management requirement is ambiguous.d15g5587e!producer㖃㗃㘃㙃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃ 3.9.2c^the set of link layer parameters is not specified in 7.3.3, only the primitive is listed thered374g4579EMeylemans, MarcFApproveGProducer^ Editorial_71`36a7.3.9.2c^the set of link layer parameters is not specified in 7.3.3, only the primitive is listed thered374g4579.4.12.1.2c!missing bracket in UNSIGNED_INT2)d375g4578j-add missing opening bracket - UNSIGNED_INT(2) 2007/09/1709/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_71`36a7.3.9.2c^the set of link layer parameters is not specified in 7.3.3, only the primitive is listed thered374g4579 2007/09/1709/16/2007 02:47:09 EDTNoWޜWstatefulހWstatelessހWjparamW^WparameterW W`WgWnWoW|WWWWW2WDWIWQWWparameter-extractionWW+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W%W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+W+WentioningofmihnetsappV0VremovealldefinitionandmentioningofmihnmssapoV/VremovealldefinitionsandavoidmentioningofmihnethocalVremoveannexeentirelybecauseithasnonornativeorinfor߰VremoveannexjandinsertsomereferenceslikerfcsifpossiߥVremoveannexjrequirementstosupport802.21byl3andabovhV!Vremovebits1112and13fromipconfigmethodstypename Vremoveciviclomethodline57p207 V+cas@asanexampletheieee802.11lowerlayersarethemacsubla@kassumptions@atdmpdu@awkward@2battery@ away@*away@***enticates@*ng@assumption@authenticates@*assuming@assumption@authenticates@*subla@)assumes@assumption@authenticates@*e@bits34and5arenotinthesamemeaningorderasforthe@boththesubclause5.3and6aresimplynamedmihfservices@by@c2@case@clarificationonparsingdatatypesisneeded@clause5issupposedtobegeneral802.21architecturedescr@&coherent@commands@commonly@)configurations@\consistencyfornatdoesnatstandfornetworkaddresstrans@constantly@contain@\contect@covered@"crossing@.default@defines@definitionfornetworksecurityismissing@describing@+descriptions@jincreasingWWWincumbent'WindependentWindicateWW=WWWWWWWWreversedirectionsareallowedVindicating_WdWWindicationW WeWtWWWW[WaWWindicationsWindividual&WinfoWinfoquerybinarydataWinformationWWWWWW7W>WAWgWkWlWmWWWWWWWWWWWW=WOWpWWWinformational9Winformative%W<WinitWWinitactionQWinitiateWWinitiatingWinitiationWinlcude8Winlcudeasaminimumthelatest802.11roll-upandforexamp8VinsertW-W.WinsideWinsteadWWintW1Wint21WintegralWintegrateWintegratemihnetsapandmihlinksapintomihlowersapitVintendedWintendendKWLWMWNWGcalreadyWWWWWbWnWoWWFWWalready/isWalsoWWWWW7W<W=W?WfWkWlWmWwWWWWWWW WWWWWWalsosubclause1.5secondparaandsubclause1.3lastparaoVghthisintroductionreferstoieee802.15itappearsValthoughthistextreferstoieee802.15itappearsthattheValwaysWWamWambiguity<Wambiguous0W;WWamendWamendmentWamendmentsWWWammendmentsWamongIWanWWWWWWWWWWWWW W WW&W'W+W.W0W1W>WAW]W^W_WjWpWtWvWwW~WWWWWWWWWWWWWWWWWWWWWWWWWW WNWOW]W^WW-jpleasemarkeachprotocolmessageasmandatoryoroptionalaVpleasesee309VVpleaseseecontribution21-07-304-00-0000-orsection6.5doc6Vpleaseseethecontribution305Vpleaseseethecontribution305306and307Vpleaseseethecontribution306change1Vpleaseseethecontribution306change2Vpleaseseethecontribution308VVpleasespecifytherelationshipbetweenthemihlinksapandVpleasestateclearlyifmihsignallingexchangesusingdataVplugfestWplus5Wpmipv6^WcWpoaWWbWkWlWmW|WWWWW8WGWHWWWWpoasbWWpointWpointsWpoliciesWpolicyWpoorWportionsWposWWW]WWpositiveW+W,WpossibilityW]WfWWWpossibleWWBWWWWWpossibly.WWW26 EDTYesIEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_15`34a5.3.1cThe paragraph mentions that MIH provides a mechanism for MIH Users to query for MIH handover information. The standard should not provent an MIH user from broadcasting information related to MIH handover candidates.d303g5299jAdd the following sentence or something similar to the paragraph: "An MIHUser may use information from the MIHF service to broadcast information on possible technology handover candidates."pThe proposed sentence is vagus and there seem to be no reason to clarify this since this standards does not restrict how an MIH User may use information it gets from MIH services (MIH User's behaviours are entirely out of scope of this std.)wAgree{e) editor disagrees 2007/12/1909/14/2007 23:15:41 EDTYessirely out of scope of this std.)wAgree{e) editor disagrees 2007/11/1809/14/2007 23:15:41 EDTMarkedYesate 3.d307g5295GjE Gupta, VivekF DisapproveGGeneral Interest^ Technical_33a6cMIH Handover primitives provide limited handover functionality. 802.21 should either provide complete handover functionality for inter-Tech handovers or delete the existing N2N primitives.d530g5072jInclude things like Context Transfer and bearer path setup as part of Handover primitives in N2N Handover functions and other MIH Handover primitives. Define a complete set of handover functionality or delete the existing N2N primitives.wDisagree{l) none needed 2007/12/1909/16/2007 13:58:33 EDTYesE Gupta, Vivekpta, Viveksting N2N primitives.d530g5072jInclude things like Context Transfer and bearer path setup as part of Handover primitives in N2N Handover functions and other MIH Handover primitives. Define a complete set of handover functionality or delete the existing N2N primitives.wDisagree{l) none needed 2007/11/3009/16/2007 13:58:33 EDTYesE Gupta, Vivekedx cA9This standard provides a useful set of tools to make MIH work; however it provides very few requirements on how these tools should be used. This will allow for flexible use of this standard; however I believe it allows for too much flexibility and needs to provide standardized methods for the use of these tools.9d589g5013jProvide required MIH procedures instead of just examples of MIH. This is not intended to limit the flexibility of the tools, just to allow the definition of agreed basic procedures.vThe MIH_SAP provides primitives and procedures as to how to use the MIH. If there are any specific aspects that need to be addressed please clarify.wDisagree{l) none needed 2007/12/1909/16/2007 17:58:08 EDTNoELevy, Joseph SF DisapproveGProducer^GeneralcQoS is a critical aspect of MIH, but there are very few normative requirements regarding the use of QoS measures and their uses.d588g501488g5014L  vBmay have been lost and not received by the source MIH node. However, the destination MIH node shall not process this duplicate retransmitted message if it has already done so. If a destination MIH node receives an MIH protocol message with no ACK-Req bit set then no action is taken with respect to the acknowledgement functionality. " WITH "The destination MIH node shall respond with an acknowledgement message for duplicate MIH messages (messages with same transaction-ID) that have thCe ACK-Req bit set. However, the destination MIH node shall not process these duplicate messages if it has already done so. If a destination MIH node receives an MIH protocol message with no ACK-Req bit set then no action is taken with respect to the acknowledgement functionality. w Principle{k) done 2007/12/1908/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_144`14a8.2.1ca8.2.1cDisapproveGProducer^ TechnicalQEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_34`58a6.3.4.1c_The sentence beginning with "Since the &" seems to state that predictive events are not useful.d312g5290jXIf that is true, either remove predictive events from the draft or remove this sentence.vZChange sentence as follows: In case predictive events are incorrect they may be retracted.w Principle{k) done 2007/12/1909/14/2007 23:15:41 EDTYes s41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_34`58a6.3.4.1c_The sentence beginning with "Since the &" seems to state that predictive events are not useful.d312g5290jXIf that is true, either remove predictive events from the draft or remove this sentence.vZChange sentence as follows: In case predictive events are incorrect they may be retracted.w Principle{k) done 2007/11/2609/14/2007 23:15:41 EDTMarkedYesally or from a remote peer. jcWWc-nem-rspWcalculateWcall&WcalledGWcanWWWW&W'W(W+W7WWW WWWWWcandidateWgWkWlWmWWWWW W WWWWcandidatesWWcannot&WcapabilitiesWW]WcapabilityWWWWWWWWCWDWMWWWWWWWWWWWWWWWWWWWWWWWW WWWWWW WWWWWW WWWWWWWWWWWWWWWWWWWWWWWdecision WWWWWWWWWW WWW WWWWWWWWW(&{p7also made the same change in indication and the messagewAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo|ERajkumar, AjayF GProducer^ Technical_121`37c_Target PoA is redundant, as it could be included in the Target Link (which is a LINK_TUPLE_ID).d402g5200jhDelete "Target PoA" parameter and include the PoA MAC address in the "Target Link Identifier" parameter.p7also made the same change in indication and the messagewAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo }ERajkumar, AjayF GProducer^ Technical_121`43cPUnclear what "old link actions" is referring to, the MN or Network side of link?d401g5201jClarify that the "old link actions refers to the destination MIHF ID side of the link (e.g. when destination MIHF ID is the Network then the old link action specifies what action the Network should take).p*It is clarified that it's local node only."Source Link" for both the name and description.121`55q!Xjsection2 W9Wsection6.56WsectionsWW7W<WWsecure7WsecuringWsecurityW7WWWWW)WseeWWWWWWWWWW%WXW[W\WhWWW2W4W6W WseecommentVseecommentforproposedresolutionVseepage66lines35-36andpage71lines32-33[Vseepage71line32-32\VselectWselectedWselectionWWselectorWselfWsendWsenderIWsendingWsendsxWyWsense0Wsent7WvWWWsent/receivedWsentenceWWWWWWWWWW4W:W;W<W=WWsentencesWWseparateWWWseparationWservergWkWlWmWcan be represented either in binary encoding or RDF encoding. Section 6.5.5 should introduce IE binary encoding and RDF encoding.=cPlease clarify which primitive is mandatory and which is optional under concerning inter-operability among different vendors developing the IEEE 802.21 compliant modules.d240g5362jPlease mark each primitive as mandatory or optional or specify that depending on the functionalities through IEEE 802.21's MIHF provides.vAA Protocol Implementation Conformance Statement (PICS) Proforma cannot contain any information that is not already present in normative text. Therefore including a PICS Proforma would be redundant. Duplication of information within a standard has a tendency to cause inconsistencies. A PICS Proforma covers only conformance, not interoperability. Clause 8 describes the formats of messages used to exchange information. The description of when these messages are used are defined in clauseB* 7 since they are triggered by primitives.wDisagreeySuperceeded by 488, 10.{l) none needed 2007/12/1909/14/2007 03:16:09 EDTNo o a8.4.1⭃㙃8.4.1.1σ@A 8.58.6Ƀ̃8.6.1.18.6.1.2Ѓ8.6.3.108.6.3.118.6.3.12σ?8.6.3.14>8.6.3.98.6.4.1ʃ˃8.6.4.281}821{|8632J8635zandWWWannexWWWW WWWWWannexdVannexe VannexfVannexhVannexiVannexjVannexkVannexlVVannexes/bWWWWWWWWUWXWW7W8W:W;W<W=WWWWWWWb1.1VVVVVb2.10.2:Vb2.17Vb2.47V8V8VjWkᑃᒃᓃᔃᕃᖃᗃᘃlWmYWZWm1YVZVn/a⛃othersWWWsubclausetableWWWWWWWtableb-12VVtableb-4Vtableb14VVtableb4VVVecdesignWWdesiredWdespiteWdestinationWWxWyW~WWWWWWWWW WdetailWdetailedWWdetailsWWWWWdetectbWdetectedbWWWdetection Wdetermine WWWWdeterminesWdeterminingWnizing how an MIHF can be deployed by seeing the most general and representative deployment models on the particular networks.a ctypes CIVIC_LO_METHOD and GEO_LO_METHOD do not have any added value for the STA. The only value for CIVIC_LO_METHOD (manual) virtually does not exist any more. Table B-10 duplicates what is already defined in IETF.d123g5479jRemove CIVIC_LO_METHOD (line 57, p207) Remove reference to table B-10, line 3 (p208) Remove GEO_LO_METHOD (line 9, p208) Remove reference to table B-10, line 36 (p208) Remove Table B-10.vLeave Table B-10w Principle{k) done 2007/12/1909/12/2007 17:02:42 EDTNo {i) to do 2007/12/1209/12/2007 17:02:42 EDTNo o d power Bit 7-255: reserved Similarly, the LINK_PARAM_GSM list does not represent the most important measuortant measurements for the MN. Before writing down a long list here, please have a look into 25.215 and use the measurement names used there&v3ERudolf, MarianF DisapproveGProducer^ Editorial_177`55, MarianF DisapproveGProducer^ Editorial_177`55lveraWolveraulisesVW;:E Sood, KapilF DisapproveGGeneral Interest^ Technical_6`7a3.1cq"A Point of Attachment (PoA) being evaluated for switching the link towards" - reads like an incomplete sentence.d266g5336jClarify or re-write.vChange: 3.1 candidate PoA: A Point of Attachment (PoA) being evaluated for switching the link towards. To 3.1 candidate PoA: A Point of Attachment (PoA) under evaluation to which the link may be switched.wAgree{k) done 2007/12/1909/14/2007 16:50:16 EDTYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_5`1a2cAre the no Normative References used by this standard? Eg: What about IEEE Standards Terms mentioned in Clause 3 introduction of definitions.d265g5337j#Update the Normative Reference listpsuperceded by 497vby 497w Supercededydeferred. Same as 497{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYes s s as 497 2007/11/1809/14/2007 16:50:16 EDTYes2EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_92a7.4.8c3See my comments about 7.3.6; the same applies here.d562g5040vADelete the statement: "The link connectivity is expected to be available at least for the time specified." Delete Confidence level from the parameter list. The Time-Interval specifies the time interval at which the link is expected to go down. A non-zero time interval is specified only if there is a high confidence level in the time interval. A time interval of 0 is specified if there is low-confidence in the computation of time interval. Additional reason codes for Link_GOING_Down may BHbe added. This needs to be done throughout the document (See Cmt 556 )6wAgreey Ref Cmt 556{k) done 2007/12/1909/16/2007 15:56:25 EDTYess eey Ref Cmt 556{k) done 2007/12/0709/16/2007 15:56:25 EDTMarkedYes he same priority?md563g503925 EDTYesh=ctimeWWWWW WWWWWWWWWtimeoutsWtimerW[W\WWWtimes'WtitleW-W.WWWtitledWtitles$WtlvWWW=WYWZWWWW6W9WIWYWtlvrepresentationforinformationelementscanbeconfused6VtlvsWWtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWW"W#W$WortWW%W<WsupportedWUWVWWWXWsupportedisquerytypeTWsupportedmihcommandlTWsupportedmiheventlisTWsupportedtransportliTWkU4ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_55`7a6.5.6.3czInformation on how to extend the RDF representation should be included. On the other hand, the Annex should be referenced.d218g5384jcAdd the following sentence to the end of the paragraph: See Annex D for extending RDF basic schema.p6added "See Annex G for how to extend the basic schema"{k) done 2007/12/1909/13/2007 16:42:41 EDTYes5ECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_55`3a6.5.6.3c-There is only one format provided in Annex D.d217g5385j[Have the TLV schema(Type assignment plus the value data type mappings) included in Annex D.wDisagree{l) none needed 2007/12/1909/13/2007 16:42:41 EDTYes 6ECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_51`27a6.5.5c6.5.5ca6.5.5c D.d217g5385j[Have the TLV schema(Type assignment plus the value data type mappings) included in Annex D.wDisagree 2007/11/18Y vthisEWFWGWJW}WWWWWWWWWWWWWWWWWWWWWWW WthiscanbedeterminedfromthepoalocationitisverydiffVthiscanbetakencareofby802.11tgupeopleaspartofupVthisclarifiespoaandposandprovidesreferencepointswhiVthisfieldallowsimplementationstorecognizedifferentverAVthisformulaisprovidedasawayforthesendertoinferthVthisisalreadyinthedraftVthisisjustanexampleVthisissupportedin802.16aswellbeforeauthentication VthisneedstobedonethroughoutthedocumentVthisseemsliketryingtomanageapriorityqueueandthisk(VthiswillbeaddressedbyathesecuritygroupVthiswillbehandledinthesecuritygroupVthiswouldapplytotheentiredraftVthoseuWthoughW WthresholdWaWthroughWWWW6 EinterestWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWkWkWkWkWkWkWickWkWkWickWkWkWkWkWriodickWkWodickWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWpmadeWWWW*W3W{W|WWWWmadechangetoallowhessidbecarriedintypeieaccessnetVmake*WWWtWmakeitthesameorderasmiheventlisttVmaking-Wmanual9Wmaps2WWmatchWWWmaterialWmayW^WWW W/WWWWWmaybeWmaybethereshouldbemoredeclinedreasoninhandoverstatuVmeans^Wmeant*WmechanismWmeesage WmentionWmentioning WmergedWmergedold6.2.3materialintosection8.2.3.5VmessageQW{W|W WAWmessagesWmihWWOWRWWWW WAWOWlWoWtWzWWmihfW$WWWWmiisW-WmiisdefinesaunifiedmechanismtothehigherlayerentitieVminorWminorrelationwithcmt563VVVW2W@WIWWWWWW 03:15:28 EDTu ctheSWYW[W\W]W^WaWbWeWfWgWkWlWmWnWoWpWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWted, MIME type "application/xml" is used." 2007/10/3009/13/2007 16:03:47 EDTNo;EOhba, Yoshihiroalue is incorrect.d212g5390jsChange the second sentence of Definition column to: "If MIME_TYPE is omitted, MIME type "application/xml" is used." 2007/10/3009/13/2007 16:03:47 EDTNo;EOhba, Yoshihiro.d213g5389jChange it to STATUS. 2007/10/3009/13/2007 16:03:47 EDTYes:EOhba, YoshihiroF DisapproveGProducer^ Technical_199`56aB.2.10.2c)The default MIME_TYPE value is incorrect.d212g5390jsChange the second sentence of Definition column to: "If MIME_TYPE is omitted, MIME type "application/xml" is used." 2007/10/3009/13/2007 16:03:47 EDTNo;EOhba, Yoshihiro;EOhba, Yoshihiro47 EDTp *jA,The annex should be made Normative and the specific suggested changes for each identified technology should be detailed in the Annex. Action should be taken by the 802.21 WG to get these amendments included in the respective technology standards, preferably before publication of the 802.21 standard.,w Superceded{k) done 2007/12/1909/10/2007 15:30:09 EDTNo EEmmelmann, MarcF DisapproveGAcademic^ Technical_280`3aAnnex IcWhy is this annex only informative. Doesn't the standard provide normative information which message can be exchanged via which reference point?qd61g5541jmake annex normativewAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTNo EEmmelmann, MarcF DisapproveGAcademic^ Technical_148`24a8.2.3.1cproveGProducer^General_292`24aAnnex Lc Brian GFApproveGProducer^General_292`24aAnnex Lcems.d70g5532 2007/09/1709/11/2007 12:01:48 EDTNocpotential@prioritized@(protocol's@!query@gr@zrdfQread@recognizing@referencetoethertypeismissing@{referencetowrongmessage@referenced@ avAEChange THRESHOLD_CROSSING_DIRECTION to enumeraed type (ABOVE_THRESHOLD, BELOW_THRESHOLD). Add REPORT_REASON enumerated type (PERIODIC, ABOVE_THRESHOLD_, BELOW_THRESHOLD) as well LINK_PARAM_REPORT will be a sequence of LINK_PARAM and REPORT_REASON. Delete on page 181, line 52 ".....when no threshold value has been crossed" Ew Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNooregular interval determined by a user configurable timer or when it crosses a configured threshold."wAgree{k) done 2007/12/0109/16/2007 03:08:31 EDTMarkedNoaERajkumar, AjayF GProducer^ Technical_71`3233czLINK_PARAM_REPORT can be generated at periodic intervals but there is no way to indicate this given the current parametersd429g5173jGChange THRESHOLD_CROSSING_DOWN to enumeration (up, down and no change).pAnnex 1 vMarkedNo^ Technical_71`4142c1Periodic notification is on a per parameter basisjor@outline@param@:parameters@periodically@#place@pleaseaddthefollowingsectionash10@-pleasemarkeachprotocolmessageasmandatoryoroptionala@>possiblypossiblyremovethereferencetoieee802.15asitisnotsp@Epredefined@ primitive@9protocol's@provideagenericcontainerthatwillallowaccesstechnolog@Zprovideadditionalnormativerequirementsrelatedtotheuse@r1@read@_recommendtomakeatleastk2andk3mandatoryeventually@Breliable@remote@^remotely@ removealldefinitionandmentioningofmihnethocandidate@Yremovedefinitionandalloccurencesofmihnethocandidate@removelines47-48andreplacebyareferenceorshortsumma@removepacketidentifier@removereferencetovariableoctetsfromthefigure@reordertableentires@S@S_sap@Zsection2@server's@z:E Sood, KapilF DisapproveGGeneral Interest^ Technical_3`36a1.3cIThe Diagram does not have any MIH Users - Are the Upper Layers the Users?d264g5338j:Include Upper Layers as the MIH Users (as defined in 3.23)vQChange "Upper Layers" to "MIH Users" Add ( "e.g." ) at the starting of next line.wAgree{k) done 2007/12/1909/14/2007 16:50:16 EDTYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_2`33a1.3c"The overall network may include pico cells such as IEEE 802.15, micro cells such as IEEE 802.11, and macro cells (such as 3GPP, 3GPP2, or IEEE 802.16) with overlapping coverage." - Where are the terms pico, micro, and macro defined. What do these mean?d263g5339jzDefine the terms before they are used. If these are defined in other specifications, then indicate appropriate references.v,These terms are defined in IEEE disctionary.wDisagree{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYesE Jette, AlanV?kE Cypher, DavidF DisapproveGGeneral Interest^General_208`1cDAnnex needs to be update for consistency to the rest of the documentd163g5439jRpage 214 line 2 change cos_packet_transfer_delay_jitter to cos_packet_delay_jitterwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes lE Cypher, DavidF DisapproveGGeneral Interest^General_204`51c=Consistency in the use of MIH_Link_Action or MIH_Link_Actionsd162g5440j Use one method and stay with it.al_208`1cDAnnex needs to be update for consistency to the rest of the documentd163g5439jRpage 214 line 2 change cos_packet_transfer_delay_jitter to cos_packet_delay_jitterwAgree{k) done 2007/12/1309/13/2007 13:56:26 EDTYes lE Cypher, DavidF DisapproveGGeneral Interest^General_204`51c=Consistency in the use of MIH_Link_Action or MIH_Link_Actionsd162g5440j Use one method and stay with it._Link_Actionsd162g5440j Use one method and stay with it..5438/06173 zjremovealldefinitionandmentioningofmihnethocandidateVVremovealldefinitionandmentioningofmihnetsapVVVremovealldefinitionandmentioningofmihnmssapVVVremovealldefinitionsandavoidmentioningofmihnethocaVremoveannexeentirelybecauseithasnonornativeorinfor9VremoveannexjVremoveannexjandinsertsomereferenceslikerfcsifpossi.Vremoveannexjrequirementstosupport802.21byl3andabovVVVremovebits1112and13fromipconfigmethodstypenameVremoveciviclomethodline57p207V to the implementation. In the contrary, it would impose needless constraints to the implementation.\d235g4069j3remove definition and all occurences of MIH_NMS_SAP 2007/09/1709/14/2007 03:15:28 EDTYesEGiesberts, Pieter-PaulF DisapproveGProducer^ Technicalcd234g4070 2007/09/1709/14/2007 03:15:28 EDT#vmihfWWW<W@WiWtWWWWWWWWWmihfidentifiermihfidisanidentifierthatisrequiredtoVmihf-idWmimo/WmissingWmnWWWWW2WEWiWuWwWxWyW}WWWW WW W}WWWWWWWmobileiWWmobility<WWmodificationWWWmodificationsWmodify/Wify/W/W/WJE Cypher, DavidF DisapproveGGeneral Interest^ Technical_160`49a8632cA%Consistency: The MIH_Get_link_Parameters response message contains the Device States Response List, while the MIH_Get_link_Parameters request message has the DeviceStatesRequest marked as optional. Why is it is required in the response message when it was not requested in the request message?%d196g5406$cthenumberofqoslevelsofserviceisnotdefinedfor2.11Vtheoverallnetworkmayincludepicocellssuchasieee802.Vthepagenumbersofthepdfdon'tlineupwiththepagenumbVtheparagraphmentionsthatmihprovidesamechanismformihVtheparametertargetpoadoesnothaveapropertypeintherVtheparametersintheprimitivescannotbefilledproperlyuVthepoachannelrangeisanimportantcharacteristicoftheVthepoacontainerdoesnotneedtocontainthepoamacaddreVnocapturethecaseofunsolicitedmihVthetermsreferencepointreferenceconnectionandlinkareVthetextappearstoindicatethatalinkdetecteventisposbVthetextstatesthattheanisresponsibleforprovidingasVthetextstatesthatthereshouldbeatleastonequeryVthetextsdescribesthisaseitheranmihusertomihuserewVtheirWWvWthemrWsWWitmustbelinkactionVDTS cA"It is important to note that, with certain access networks an MN should be able to obtain IEEE 802.21 related information elements before the MN is authenticated with the PoA." - Since this clause mentions security (authentication), it is very important to decide if such a functionality is even needed. If so, then how can be actually make this happen in a secure network. I see STA <=> PoA security at a different layer than the STA <=> MIIS, and as such, I do not see how the (future) securBity will work.d275g5327jGroup to discuss the requirements and usages of such functions. If these functions do remain in the draft, then securing these may be a very hard problem - the high cost of security may limit such operations.vhe STA <=> MIIS, and as such, I do not see how the (future) securBity will work.d275g5327E Sood, KapilF DisapproveGGeneral Interest^ Technical_46`60a6.5.2cWWWWisn'tWissueWWW WcthisWWWWWWWW W W WWW.5ccBWhat is the difference between Link-Up and Link-Handover-Complete?d602g4351jClarify 2007/09/1709/16/2007 21:41:08 EDTYes,ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_41`3a6.3.5cs network.d603g4350jClarify or remove 2007/09/1709/16/2007 21:41:08 EDTYes+ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_41`11a6.3.5cBWhat is the difference between Link-Up and Link-Handover-Complete?d602g4351jClarify 2007/09/1709/16/2007 21:41:08 EDTYes,ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_41`3a6.3.5croveGGeneral Interest^ Technical_41`3a6.3.5cd601g4352 2007/09/1709/16/2007 21:41:08 EDT jremoteWWW WWW&W+WxWyWWWWWWW!W"WJWWWWWWWWWWWWWWWWWWW WWWW!W'W,W-W.W/W6W9WDWEWHWRWSWhWWWWWWWWWWWWWWWW W W W W!W"W#W$WCWDWFWIWMWQWaWjWmxWremovealldefinitionandmentioningofmihnethocandidateVremovealldefinitionandmentioningofmihnetsapVVremovealldefinitionandmentioningofmihnmssapVVremovealldefinitionsandavoidmentioningofmihnethocaVremoveannexeentirelybecauseithasnonornativeorinfor9Vremoveannexjandinsertsomereferenceslikerfcsifpossi.Vremoveannexjrequirementstosupport802.21byl3andabovVVcaretherereallynonormativereferencesforthisstandardVareaNWaroundWarq WarreWarrived WarrowWarticlesWsWWWWtesWWWWsWWWWmitesWWWWWWWWmitesWWWWWWsWWWW_W_We_W_W_WW_W_W_W_W_WWsameW_W_W_WW_W_WameW_W_WW_W_WW_W_W_W_W_W_W_W_W_W_W_W_W_W_WW_W_W_W_W_W_WW_W_W_W_W_W_W_W_W_W_W_W_WW_W_WW_W_W_WnWWsamePWSWYWZW[WW_W_WWW_W_W_W_WW_W_W_W_W_W67cspecificationsWbeforbinarydatainsteadoftlvVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW;W޴WWthing݈WWWWWWWW;W޴WWthing݈WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW NE Feder, PeretzF DisapproveGProducer^ Technical_130`12cA The description of the "Source Link Identifier" and "Target Link Identifier is confusing. For the case where the MN_HO_Complete message is sent to the new target PoS then source and target link identifier are one and the same (At least according to the description). d448g5154jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p;Remove the "intended", since this is HO_Complete primitive.wAgreee and the same (At least according to the description). d448g5154jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p;Remove the "intended", since this is HO_Complete primitive.wAgree33cvales WvalidWWWWWWvalidated Wvaluable%WvalueWWWWWWWW.WGW[W^WWWW:W;WwWWWWWWvalueoftypeiepoamacaddressis10000302herewhileitiwVvaluesWWWWWWFWGW^WWWWvalues65to127arenotvalidvaluesforipv6prefixshouldVvariableWWW'WvariousWWWWW$WWWWWvaryWW#WWvendorWWvendorsWWWverb{Wverbose<WverifiedWversionWAWversionfieldisnotusefulunlessthespecificationcompletAVversionsWvertical/horizontalgWveryWWWWWW<W[WWWWWWMWWviaWcWWWviabilityWviewWviewedWviolatesWvirtualW/17[_‚ᩃ_‚^‚‚]‚݃ރ߃‚fCD‚B‚‚ᧃᰃ‚‚‚‚\‚2‚◃1‚e‚Ã![Ã!0QÃ!@PRhÃ!`Ã╃ⲃ Ã!p㞃Ã!Ã!ⓃÃ!giÃ"jÃ" OmoÃ"0lÃ"@knpIÃ"PqsÃ"`rÃ"ឃᢃŃ Ã"tÃ#uvÃ# ᝃᤃƃɃwxy{|}ぃÃ#0ᣃz~ Ã#@⁃Ã#P᥃⃃⯃ 㔃Ã#`Ã#CÃ#E℃⅃ↃÃ#DÃ$N9/1709/16/2007 03:08:31 EDT0\jchangethetexttoclearlyspecifyhowthedestainationofeVchangethetexttostatethatthemihmlme-sapmessagearepVchangethetileofsubclause5.3$VchangethetitletoexamplequeryforbinarydataZVchangethetypetolinkidVchangethetypestolistforactionrequestandresponseincVchangethemtolink-idconsistentlyVchangethisidentifiesthecurrentlinktothisidentifiestCVVVVchangethisnotificationisgeneratedeitheratapredefined`Vchangethistabletotablel-4PVchangethosedatatypeaslistdatatype7.4.20.4.27.4.21.3.2OVchangethresholdcrossingdowntoenumerationupdownandnoaVchangeto3rdgenerationpartnershipprojectsimilarfor3gp:VchangetoaccessnetworkauxidVchangetoarrivefromthemac-wimax_Vstomatchclause8.6.LVXVchangetomihmnhocommitindication[Vchangetomihn2nhoqueryresourcesKVWcharacterizeWQwAgree{k) done 2007/12/1909/14/2007 16:50:16 EDTYessF DisapproveGGeneral Interest^General_7`5a3.16c@"MIH protocol entities" is not defined and not appropriate here.d593g5009j"MIH Network entities"vChange: 3.16 MIH discovery protocol A protocol for discovering MIH protocol entities. To 3.16 MIH discovery protocol A protocol for discovering MIH entities.w Principle 2007/11/1409/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^General_5`7a2c#Where are the normative references?d592g5010j Add them.vby 497w SupercededyDefferred. Ref Cmt 497 2007/11/1409/16/2007 21:41:08 EDTYesELevy, Joseph SF DisapproveGProducer^ Technical_33`1cThere are very few (8) "shalls" in section 6.0 MIHF Services and the "shalls" that are present tend to limit the use of the specification instead of specifying required specified performance.d591g5011e6(jofW WWW W#W$W'W(W*W/W4W:W;W=WJWtWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WE Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`20a64311che expanded view contains Operator_1d130g4823jChange Operator_1 to Operator_2 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`20a64311c). However the expanded view contains Operator_1d130g4823jChange Operator_1 to Operator_2 2007/09/1709/13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`20a64311cnterest^ Technical_44`20a64311cd129g4824 2007/09/1709/13/2007 13:56:26 EDTi(ERudolf, MarianF DisapproveGProducer^ Editorial_32`44a5.7.2cChange sentenced486g5116e realization for IP-based external transport interfaces. Alternatively, describe a means to transport at least a limited set of MIH messages through GMM or GTP messages, like Direct Transfer etc., even if any formal specification would be incumbent to 3GPP one day. needa t least to describe or at least outline the principle of 2-3 technical approaches to guide an implementor. The only other alternBative is to entirely remove 3GPP from the list of access technologies that 802.21 can operate with (everywhere in the 802.21 draft specification).vby comment 488w Superceded 2007/11/2609/16/2007 07:13:12 EDTMarkedYes(ERudolf, MarianF DisapproveGProducer^ Editorial_32`44a5.7.2cChange sentenced486g5116 least a limited set of choices available ?d487g5115j8WLWQWqWuWwWisn'tWissuebWeWnWAcdeviceWWWWWWW W#W$WJWWWWWWWdevicestatesrequestJWWdhcpOWdiagramWWWWWWWdiagramsWWWWMWWdichotomyWdictionaryFWdifferenceWWdWWWWWWWWWWWWWWWWWWWWWpproveGGeneral Interest^ Editorial_173`1aAnnexescnal description: The remaining text in this section defines the RDF vocabularies for MIIS. 2007/09/1709/13/2007 16:42:41 EDTYesECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_173`1aAnnexescerest^ Editorial_173`1aAnnexescd223g4081 2007/09/1709/13/2007 16:42:41 EDT~8jmakerequestedresourcesetparameteroptionalinboththerVVmaketheannexnormativeVmaketheparameterstableformatconsistentthroughoutsecti3Vmakethisnumberapropertyofthelinktype VmaketransitiontoinitinallstateswhenthetransactiontVmakes0Wmaking+W]WWmakingtheseparametersoptionaldoesn'tsolveanyproblemi]VmanagementWWWWW(W<WWWiWjWxWWWWWWmandatory5WWWWmannerWWWtWWWmappingsW5WmapsWmarkWW>W?Wmarkipaddressinformationoptional>Vmarkipconfigurationmethoandipaddressinformationoptional?VmarkedWWWW!W"WWWmasked=WmatchWWWLWXWmaterialWWEWMWmaxWmaximumWmaximumdataratein802.11termsisthehighestavailablebVLvpluralWpoaWWWWWWOWkWlWGWWWWWpoalocationisessentialtodeterminingtheavailabiilityoVpointWWWGWpointsWWWWWpolicy<WposWWWWuWWpower0W2WWWpracticeWpredictionWpredictiveWpreferenceWWpreferredcandidatelimWpresentAWWprimarilyWprimitiveWWWAWiWwWWWprimitivesWW@WfWwWWWWWprimitiviesWprinciple]WwW WWpriorAWprioritizedWWpriorityWW(WproceduresWprocessW WproformaWproperlyWpropoganda6WproposedWprorityWWprotocolW<WWWWAW}WWWW W WprovideW/WWWWWprovidewaysofsimplificationV cAWhen a time out occurs in COMPLETED state, we should not report an error. When the source enter this state, it starts a timer in case a re-transmitted MIH response is received due to a lost MIH ack sent by the source node. If no re-transmitted MIH response is received then the destination has successfully received the ACK and the transaction should end. In this case no error has occurred and therefore should not be reported.d287g5315j-From line 49 delete text "and reports error."pW?WDWEWFWIWJWOWRWSW[W]W^WaWkWlWmWtWvWzW{W|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWeneral Interest^ Technical_95`58a 7.3.14.1.2d220g4084 2007/09/1709/13/2007 16:42:41 EDTpE Gupta, VivekF DisapproveGGeneral Interest^ Technical_19a5.4.2csRename reference points R1..R5, as J1..J5 (or something else), since they overlap with those defined in WiMAX Forumd521g5081j0Rename R1..R5, as J1..J5 throughout the documentp#change made throughout the documentvChange it to RP1, RP2....w Principle{k) done 2007/12/1909/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_26a5.5.3cIn case of 802.11, SME makes intra-technology handover decisions. Clarify the role of SME w.r.t MIH and update figure-7 appropriatelyd520g5082520g5082roughout the documentvChange it to RP1, RP2....w Principle{k) done 2007/12/0109/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_26a5.5.3cIn case of 802.11, SME makes intra-technology handover decisions. Clarify the role of SME w.r.t MIH and update figure-7 appropriatelyd520g5082General InterestEDTj>jbeenWWWbefore W2W7WwWWWWWbeginingWbeginningwWbehave WbehaviorsWbelieveWbelow:WWbestWWWbetterWWbetweenWWWW/W1W7W>WBWIWWWWWaWhWrWbibliographyWbinaryWZWbitWWWWW@WnWsWbitmapWXWWbitsWWblankhWblerWblockZW\Wblocks&WdWgWbodyWWWWbtsWbut WW&W/WeWwWbyWWWWWWW,W4W7W=W>W@WAWBW`WcWwWWWcWcalculateWcalledGWcanWWWW&W'W(W+W7WWcandidateWgWkWlWmWWcannot&WcapabilitiesWW]WcapabilityWWWWWWWWG,canWWW W WW^Generalal_33`1cThere are very few (8) "shalls" in section 6.0 MIHF Services and the "shalls" that are present tend to limit the use of the specification instead of specifying required specified performance.d591g4362j@Provide additional requirements which will define MIHF Services. 2007/09/1709/16/2007 18:16:08 EDTYes7ELevy, Joseph SF DisapproveGProducer^Generalerformance.d591g4362j@Provide additional requirements which will define MIHF Services. 2007/09/1709/16/2007 18:16:08 EDTYes7ELevy, Joseph SF DisapproveGProducer^General required specified performance.d591g4362j@Provide additional requirements which will define MIHF Services. 2007/09/1709/16/2007 18:16:08 EDTYes7ELevy, Joseph SF DisapproveGProducer^Generald590g4363 2007/09/1709/16/2007 17:59:40 EDTgPE Sood, KapilF DisapproveGGeneral Interest^ Technical_13`1a5.1.4ccA3"MIH events, commands and information service message exchanges between an MN (Mobile Node) and a network PoA (Point of Attachment) cannot be secured until the MN has a secure connection with the network PoA." - this sentence sounds self-filfulling. Yes - you need security before something can be secured. 3d271g5331jThis sentence be re-written to better specify what security properties need to be addressed. If none have been specified, then delete this 5.1.7 clause, and be added by future security work.vby 471. Sub Clause deleted.w Principley Ref Cmt 471 2007/11/2609/14/2007 16:50:16 EDTMarkedYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_13`1a5.1.4cpproveGGeneral Interest^ Technical_13`1a5.1.4cand hence, be useful.vIThere is no point in doing the standard if it is only a "desirable goal".wDisagree 2007/10/07 2007/10/07Xjexpected WexpiresWWexplainWEWexplaintypeofauthenticationisreferencedinthisparagraVexplicitWWWexplicitlyvWexposed@Wextend-Wextending4WextentWexternal'WfW%WfakWlWmWfailedeWfailureeWWfar7WfastWfdd3Wfdd/tdd;WfeatureWWfeatures,W/WfewWfieldW=WWAWfigWWWeWWWWW*WHWWWWQWWWWWWWfigure-7WfirstWWWW&WbWWWWWfirstintroducesomethinglikeapicssomewhereintheannex&VfixWWWW WWWfixthefontthisisthereisseveralotherplacesindraftVfixthemodellingsothatthestandarddoesn'tplayfastandVfixthepdfand/orthetextsothepagenumberscorrespondVfixthetext VV bcA.The PoA Container does not need to contain the PoA MAC address (at least for 802.11 networks). This is easily obtained using WLAN primitives given the mobile node knows the desired network. Since it is not needed, it is just extra information to get out of sync between the access network and the MIIS..d86g5516jDelete the PoA MAC address.vThe idea was to obtain this information before making the radio connection. Once the radio connection has been made this information can be esaily obtained.wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYess809/11/2007 17:46:47 EDTMarkedYesync between the access network and the MIIS..d86g5516jDelete the PoA MAC address.vThe idea was to obtain this information before making the radio connection. Once the radio connection has been made this information can be esaily obtained.wDisagree 2007/11/2809/11/2007 17:46:47 EDTMarkedYes7Nu tcmihWWWWWWWWWWWWWWW W WWWlementation and a local Network Management System stack. Depending on the nature of the device, this local NMS stack may vary or may not even exist. Standardizing this interface brings no benefit to the implementation.To the contrary, it would impose needless constraints to the implementation.[d534g4419j3remove all definition and mentioning of MIH_NMS_SAP 2007/09/1709/16/2007 15:23:06 EDTYespENatarajan, Kadathur SF DisapproveGProducer^ Technicalc3remove all definition and mentioning of MIH_NMS_SAP 2007/09/1709/16/2007 15:23:06 EDTYespENatarajan, Kadathur SF DisapproveGProducer^ Technicalcd533g4420 2007/09/1709/16/2007 15:23:06 EDTd@j$ejof@\jgjh@ ikjAZl@cAxvAm@GjAncAco@ jr^)s@tjA ucAvcAwcAIgvAPxvz@;{@(pE}v&~@@c@yj@@@@vAi@g@%@"jl@@@@type in this specification contains information needed for determining the end of data." 2007/10/0709/13/2007 16:03:47 EDTYes>ded.d209g5393jAdd the following sentence in Annex B: "This Annex defines data types used in the IEEE 802.21 standard. Any variable-length data type in this specification contains information needed for determining the end of data." 2007/10/0709/13/2007 16:03:47 EDTYes>EDTvcmakesWW W<WwWWWWWWmakingWWWmanagedWWsiblyssiblyssiblypossiblyssiblypossiblyssiblyssiblyssiblyssiblyssiblyssiblyposW.Wpossibility}Wpossible)WpossiblyssiblyssiblyssiblypossiblyssiblyssiblyitiveWWpossibility}Wpossible)WpossiblyssiblyitiveWWpossibility}Wpossible)WpossiblyssiblyssiblypossiblyssiblypossiblyssiblyssiblyssiblyssiblyssiblyssiblyssiblyssiblyWWWWWWWWWWWWWWWWible߹WHWVWW)WpossiblyߥWWWWWWWWWWW)WpossiblyߥWWWWWW)WpossiblyߥWWWWWW)WpossiblyߥWWWW)WpossiblyߥWWWW)WpossiblyߥWWWWWߥWWWWW3/2007 16:03:47 EDTYes3jdeletethethreeitemsorpreferablymovethemtoaninformaVdeletetheuirbitoraddmoretextthatanswerstothosequ@Vfaces, the notion of MIH PoS is associated with the network entity itself and not with just one of its interfaces."d548g4405j"Note that for a network entity comprising of multiple interfaces, the notion of MIH PoS is associated with the network entity itself and not with just one of its interfaces." 2007/09/1709/16/2007 15:56:25 EDTYesbEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_6`64a3.15he network entity itself and not with just one of its interfaces." 2007/09/1709/16/2007 15:56:25 EDTYesbEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_6`64a3.15e of its interfaces." 2007/09/1709/16/2007 15:56:25 EDTYesbEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_6`64a3.15d547g4406 2007/09/1709/16/2007 15:56:25 EDT(clocalmihuserspecifyinglocalmihfcapabilitiesaswellas]VlocallywW~WWlocatedWWlocationWWWWWlocationsWWWWlog10WlogicW0WlogicalWWWlongeWWlongestWlongitudeWWWlongitudeshouldbenormalizedtowithin180degreespositivVlookedWlooksWWloose WlosingWlostWWWlotWlowerWWWWWWWlower-layerWlowestWWlsapWWWWmWWNWWWm-3NWmacWWWWWWWWWWWWWWW W7WWWWW_W`WwWWWW$W&W*W;WsWtWuWvWvWvWvWvWvWWWWWW.W4W5W6W:W>WEWIWJWKWNWPWlWrWuWW+citisincorrecttosaythatthetransmissionstatuscanbevVitisnotclearwhetherthereissomelimitonthenumberof VitisnoteworthyhoweverthattherewillbenodirectcommunVitisthemihusernotmihfthatprocessesthismessageVitisverydifficulttocross-referencethesectionswheretVitisverydifficulttorelatetheprimitivestotheprotocoVitmaysoundtrivialbutinitializeuponreceiptofthemihVitsays802.21allowsanmntodiscoverheterogeneousnetworVitshouldbemadeclearthatinthecasethattheoperationVitwouldbeusefulifwhenyougeneratethepdfyouweretoVit'sWWitemxWitemsWWWWWWWWitemsathroughecontainamappingofthemihlinksaptomViteselfWitsWWWWWW WWWWWWWWWWmacaddressesofpoaisinsufficientfornetwVV!LcaddressingWaddsWW<WW WadjoiningWadmissionWadmitWadmitted WadoptedWadvantageWadvertiseWadvertismentWaffectWafraidWaftereWuWWWWWagainstWW,WWaggregated'Wagree7WEWyWWairWairlinkWairplaneWalgorithmWalignedWallWWW W%W1WIWfWkWlWmWvWWWWWWWW2WMWWWWallocated0WrWsWallowWWWWWWW W7WWWWWallowableWallowedWWWallowingfWWallowsW[WW*WWalludesWalmostWWaloneWalongW 2007/09/1709/13/2007 16:03:47 EDTYes+jDelete the sentence. 2007/09/1709/13/2007 16:03:47 EDTYes+d209g4095 2007/09/17Fctransport-solution.WtransportedWtrchWtriesWWtriggerpW~WWtriggers?WtrivialWtroubleWtrueWW W7WWWWtrust@WtryWtryingW WWWWWtsWtsapWtuple|W7WWtwiceWWtwoWWWWWWfWwWWWW!W"WZW\WdWWWWWWWWWWWWW WWtwoblockshavethesamehandovercompletionandcandidatepdVtwo-wayWtypeWWWWWWWWWWW/W3W=WFWGWWW[W]W^WWWWW1W2W6W8W9W:W;W<WDWpWwWyWWWWWWWWWWWWWWWWWWVtypesWWWWW4WFWGWW=WWWKcreferencetoethertypeismissing-Vreferencetotablee-2VnobitforlinkactioncommandVVhandoverVthereisnobitforlinkactioncommandVVemihmnhocaVthereisnoinformationaboutaccessnetworkidentifierwhicVthereisnoinformationelementdefinedhoweveritmaybeaVthereisnolinkactionsdatatypeitmustbelinkactionVthereisnomihconfiguremessagewiththisnameVthereisnomihlinkactionsmessagecorrespondingtoclausVthereisnominmncommitrequestVVVthereisnotransactionstatediagramforbroadcastmihcapa3VthereisnowayforthiseventtoindicatethatitwasgenerVthereisonlyoneformatprovidedinannexdVthereneedstoclarifyhow'swirelesslinkconditionschangeVthereseemstobearbitrarydecisionsmaderegardingthemihVthereseemstobelimitedusefulnessofthelinktransmissioVumntoifmimet(V)V:jagreed@}an@analog@landandthismessageistransmittedovercontrolplaneusingal@$apply@asdescribedincomment@~attableb-121replacebitmap64withrevisionintherawo@available@Mbeconsistentrecommendtousemediaindependentnohyphen@jbeen@nbot@c@Dcapability capable@&case@change27to29and26to28@Xchangedescriptiontoabitmapnwherenmustbeamultiple@changen2nhocompletetomnhocomplete@changerequestisreceivedtorequestmessageisreceived@0changethetexttoclearlyspecifyhowthedestainationofe@dchangetoarrivefromthemac-wlan@changetothelinkdetectedeventisgeneratedonthemnwhe@fE pAchanged text to: "Only an MIHF capable network entity shall respond with a MIH_Capability_Discover response to the received MIH_Capability_Discover request with a broadcast MIHF ID, or send unsolicited MIH_Capability_Discover responses periodically."@Af  33I  33K  33c @ 33k  33fwAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_153`37a8.6.1.1c"and this message is transmitted over control plane using L2 management frame, such as 802.11 management action frame and 802.16 MIH MAC management message."d572g5030j"and this message is transmitted over control plane using a L2 management frame, such as a 802.11 management action frame or a 802.16 MIH MAC management message."wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes EChaplin, Clint Fn, Clint Fn, Clint FWjasdescribedincommentVassuchitismoreappropriateforthefunctionalarchitectuVaspectWaspectsWWWassignedWassignment5WassociateWassociatedW WMWassume'Wassumptions WWatWWW'W5W6W7W@WXW`WwWWWWWWWEWNWWWWWated stacks.d237g4716jsremove the stack marked as "Remote Entity" and remove the text "Local Entity" from the stack on the left-hand side. 2007/09/1709/14/2007 03:15:28 EDTYesPaulF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d237g4716jsremove the stack marked as "Remote Entity" and remove the text "Local Entity" from the stack on the left-hand side. 2007/09/1709/14/2007 03:15:28 EDTYes 2007/09/1709/14/2007 03:15:28 EDTYesd236g4717 2007/09/1709/14/2007 03:15:28 EDTcdefinitionfornetworksecurityismissingVdefinitionoflinkacresultcodedoesnothaveavalidrangVdefinition/specifica<WdefinitionfWdefinitionsWWWWWWWmWdefintion"W#WdegreesWdelayWWdelaysWdeleteWWWWWWdeleteannexfasitisredundantandnotrequiredinthespVn. Or, choose a subset of 4-5 QoS parameters that must map from A to B, and leave the rest FYI only. 2007/09/1709/16/2007 07:13:12 EDTYes߭ERudolf, MarianF DisapproveGProducer^ Technical_31`1a5.6.2cAbsence of a media-dependent SAP for GSM/EGPRS. There is only a MIH_3GLINK_SAP, but nothing is defined for GSM/EGPRS cellular, even though both seem to be in scope for 802.21 as part of 3GPP access technologies.d472g448121 as part of 3GPP access technologies.d472g4481 2007/09/1709/16/2007 07:13:12 EDTYesN jtakenWtalking6WProducer^ Technical_13`57a5cIn the overview subclause 1.3, it is clearly stated that the handover is not limited to mobile case. Why there is a specific subclause 5.1.9 talking about movement caused handover? Is this going to be different from other type of handover?d495g4458j;Merge the text to subclause 5.1.1, or remove the subclause. 2007/09/1709/16/2007 08:19:02 EDTYesߗproveGProducer^ Technical_13`57a5cIn the overview subclause 1.3, it is clearly stated that the handover is not limited to mobile case. Why there is a specific subclause 5.1.9 talking about movement caused handover? Is this going to be different from other type of handover?d495g4458j;Merge the text to subclause 5.1.1, or remove the subclause. 2007/09/1709/16/2007 08:19:02 EDTYesߗe of handover?d495g4458j;Merge the text to subclause 5.1.1, or remove the subclause. 2007/09/1709/16/2007 08:19:02 EDTYesߗd494g4459 cALines 7-45: The concept of Counters is misused on this page. 802.11 MIB counters are simple incrementing values. The value of any counter at any time is arbitrary. PER, PLR and other usefule parameters cannot be derived from the raw values in any of the MIB counters. Delta values over any time period may be used for the intended purpose here. THat is counter values must be captured at the beginning and end of a period of interest. Subtracting the ending value from the value at the beginninBg of the period produces a relevant count for that period. This is only true, however, if counter overflow does not occur during the period of interest.d636g4966j Fix this basic misunderstanding.pby the contribution 07-0375-01w Principle{k) done 2007/12/1909/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_289`4aKc`4aKc4cwishWwithWWWWWWWWWWWWWW WWWW$W0W1W7WeWfWnWoWwWzW{W~WWWWWWWWWWWWWWWW6WEWXWhWyW|WWWWWWWWWWW W WWWworkWW7WWWWworking'W7Wworks7WworstWwouldWWWWWWWW WW+W0W7W=WgWxWyW~WWWWWWWWwouldn'tWWwouldn'titbeusefultoreferencepreviouslydefineddefiniVwrongW/W2W:WWWwwanWxmlWxmldoesnotcompileVxxx WxxxxWxyzWyankedWyes1WWyetWWWfWyet-to-be-definedWyieldWyouWWWzeroWB4 jcolumn;WWWdevelopmentfW)Ã20(Ã2@'Ã2P&Ã2`%Ã2p$Ã2#Ã2"Ã2!Ã3 Ã3 Ã30Ã3@Ã3PÃ3`Ã3pÃ3Ã3Ã3Ã4Ã4 Ã40Ã4@Ã4PÃ4`Ã4pÃ4Ã4Ã4 Ã5 Ã5 Ã50 Ã5@ Ã5PÃ5`Ã5pÃ5Ã5Ã5Ã6Ã6 Ã60Ã6@Ã6PÃ6`Ã6pÃ6Ã6Ã6Ã7Ã7 Ã70Ã7@Ã7PÃ7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpAvinformationWWWWWW&W'WkWWW WWWW WpWWWWWWWWWWWinformativeWWinformingwWinitiatedkWinitiatorWinputsWWinstantaneousWWinstantiatedWinsteadWint1WintendedWWinteractionAWWWinterfaceW@WWWKcinincaseof802.11smemakesintra-technologyhandoverdecisiVinfigure2youhavenumberedthecommunicationlinksaccordVinhocommittargetpoashouldnotbemacaddressifnetworkVinnumerousplacesinthisclauseconformancerequirementsiVinordertobeabletoperformalocalhandoveriereplacemxVyVintableb3datatypesforaddress3gppidentifiersareunc4VinthecaseofremotediscoverythisprimitivemaycontaintVinthelistofpoaonthebottomrightthefirstelementshoVintheoverviewsubclause1.3itisclearlystatedthattheVinthesendingstatethesourcenodeiswaitingforeitheraVin-correctWinaccurateWinadequatelyWincludeWWWfWWWWWWBWMWWWWWWincludedWWWW|WWWWWWWW.W4WWWwWWindicatedWWWWWtAB@DcE@v GcH@JGKcAL@gYM@ N@a{O@ jP@Q@S@T@W@gNX@~j[cA]\@wg]@jAt^@p_@|`@a@vAUb@c@@date PoA" to "candiddate Point of Attachment" Spell out other acronyms in this section as well. Acronyms need to be spelt out the first time they are used, the acronym can then be used subsequently.wAgree 2007/11/1409/13/2007 15:42:30 EDTNoHE Cole, Terry LF DisapproveGGeneral Interest^General_6`32a3.7cAI blieve the use of acronyms in the abbreivation to be confusing.d198g5404j+Spell out MN and PoA in the definition 3.7.wAgree 2007/11/1409/13/2007 15:42:30 EDTNoIE Cypher, DavidF DisapproveGGeneral Interest^ Technical_113`53DTjdefinitionWWWWWW6W>W?WAWBWWWWWWWWW W#W$W:W;WHWWWWWWWWWWdefinitionsW%WWFWWdefintionsWdegree(WdegreesWdeiveries WdelayQWjWkWWdeleteWWWWWWWWWWW W1W=W?W@WFWYWjWnWoWpWrWsW|WWWWWWWWWW<W@WAWTWVWYWWWWWWWWWWWWWWWvidF DisapproveGGeneral Interest^ Technical_113`53a742112cd197g4107 2007/09/1709/13/2007 13:56:26 EDT1cinWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWW!W"W#W%W&W/W4W6W7W=WDWEWFWSWbWfWgWiWkWlWmWpWvWwWxWyW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWW#W$W%W&W'W/W0W2W5W6WBWEW&E Xie, QiaobingF DisapproveGUser^ Editorial_37a6.3.2c,6.3.2 should be moved after 6.3.3 discussiond346g5256j8move 6.3.2 content to the end or after 6.3.3 discussion.pduplicate with 110{l) none needed 2007/12/1909/15/2007 22:08:13 EDTNoo 6.3.3 discussiond346g5256j8move 6.3.2 content to the end or after 6.3.3 discussion.pduplicate with 110{l) none needed 2007/11/1809/15/2007 22:08:13 EDTMarkedNo07 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Technical_124a7.4.24cMIH_N2N_HO_Commit currently does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d351g5251jcadd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit. 2007/10/0709/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^General annex.Gd352g5250iredinthespVBpEHeubaum, Karl FFApproveGProducer^ Editorial_11`14a4cN"Network management system" should be capitalized to match the other acronyms.d64g5538j&Change to "Network Management System".{k) done 2007/12/1909/11/2007 11:51:13 EDTNoEHeubaum, Karl FFApproveGProducer^ Editorial_3`35c|(note this refers to page iii, line 35) "Michael HogHooghi" should be spelled "Michael Hoghooghi" (he's a former co-worker).d63g5539jChange to "Michael Hoghooghi".{k) done 2007/12/1909/11/2007 11:49:56 EDTNoEKiernan, Brian GFApproveGProducer^General_292`24aAnnex LcAnnex LcAnnex Lcghooghi" (he's a former co-worker).d63g5539jChange to "Michael Hoghooghi".{k) done 2007/11/1809/11/2007 11:49:56 EDTMarkedNoEKiernan, Brian GFApproveGProducer^General_292`24aAnnex Lcf ".There are two kinds of transport...".d66g5536j/Change to "There are two kinds of transport..."H!pby7W8W[W\WWWWWWWWWWWWW W WWWW W#W'W>WMWWWWWWWWWWWWWWby21-07-375-01Vbythecontribution07-0375-01VcWWc-2WWc2WOWcanWWWcandidategWW WcapabilityWcapableWcarriedWcasenWoWWWWWcauseWcellWWchanbeoWchanbetomihlinkconfigurethresholdsoVchangeWWWWW W WWW#W(W+WWW{W|W/WWWW㰃WWchange3serviceserviceVchangemadeper21-07-0430-00-0000VVVVconfusionWconsistencyWconsistentWW3WcontainerWconventionWcorrectWcorrespondingWcoverWcreateWcrossWs an 80$~japplyWWappreciatedWapproachWapproaches'WappropriateWWtWWWEWWWapsWarchitecturalWarchitectureWWWWareWWWWWW W(W2W7W;W=W]WbWcWkWlWmWtWwWWWWWWWWWWWWWWWareaWarfcn1W4Warq Warrive_W`WarrowWarrowsWasWWWWWWWWWWWWW&W'W(W0W7W8W=WOW]WeWgWvWWWWWWWWWWWWWWWWWWWWWWW!W"W-W.W0W8WWWWWWWWWWWWWatWWW'W5W6W7W@WXW`WwWWWWWWWWcwhileWW7W<W?WJWtWWWJWwWWWwhoWiWwholeWWwhomWwhouldcWcorrected.d474g4479jDefine ARFCN, BSIC, GSM vs W-CDMA band by references to 3GPP specifications. Does PSC mean Primary Scrambling Code ? If yes, use the right name of the scrambling code identifier in the RRC specifications, cite it.al_177`27c[In table B.3 Data types for address, 3GPP identifiers are unclear and need to be corrected.d474g4479jDefine ARFCN, BSIC, GSM vs W-CDMA band by references to 3GPP specifications. Does PSC mean Primary Scrambling Code ? If yes, use the right name of the scrambling code identifier in the RRC specifications, cite it.nd need to be corrected.d474g4479jDefine ARFCN, BSIC, GSM vs W-CDMA band by references to 3GPP specifications. Does PSC mean Primary Scrambling Code ? If yes, use the right name of the scrambling code identifier in the RRC specifications, cite it..<EEmmelmann, MarcF DisapproveGAcademic^ Editorial_12`10a5.1.1c8incoherent usage of "single" vs "double" quotation marksd31g5571j*replace 'hard' / 'soft' by "hard" / "soft"{k) done 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_6`37a3.8cSthere are two definitionf for the same thing: a/ "higher layers" and b/ "MIH Users"d30g5572jA5There might be "higer layers" which do not use the MIH functionality. Therefore, delete the definition of higher layers and include the aspects of the higher layer definition in the definition of MIH users, i.e. state there that MIH users can also be those higher (protocol) layers which use MIH functionality5y5e, delete the definition of higher layers and include the aspects of the higher layer definition in the definition of MIH users, i.e. state there that MIH users can also be those higher (protocol) layers which use MIH functionality5nical_12vchangeupperlayerstomihusersVchangedWWW W W0W{W}WWWWchangedsectiontosubclause0VchangedsentencetoonlymihnetworkentitiesshallrespondVchangedsentencetothealgorithmdefinedinietfrfc2988m{Vchangedsentencetothemihfunctionsinmnandnetworkenti}VchangedtoVchangesWWW0WWWWchangestobemadeontopofchangespecifiedincomment384VVWclarifiesWclarifyWWuWWclarifythisaslinkauthenticationVclarifyingWWclassWclassesWWclassificationWclauseWWWclearW0WWcloselyWcmtWco-locatedWcodeWcodesWcolumnW0WcombinationWcombinations/Wcombined4Wcombines/WcomeWcommandWiWWcommandsWW WWW'WWWcomment2'VWkdcassumptions7W WassumtionWasymmetricfWatWWWWWWWWW W W!W'W5W7W>WAWBWKWLWMWNWaWWWWWWWWWW WWNWWWWWWWWWWW W WWbehavior, which cannot be used in these cases.Cd193g4111jdAdd new state diagrams, or remove this capability and any associated material from the entire draft. 2007/09/1709/13/2007 13:56:26 EDTYesWAWgWkWlWmWWWWWWWWWWWW=WOWpWWWWWinformational9Winformative%W<WWinitWWinitactionQWinitiateWWinitiatingWinitiationWinlcude8Winlcudeasaminimumthelatest802.11roll-upandforexamp8VinsertW-W.WWWWinsertacommaafternetworkstargetnetworksinorderVinsertanewparagraphandreplacethesinglesentencestartVpitVintendedWintendendKWLWMWNWBclinkconfigparamallowsonetorequestthatareportbegen[Vlinkidshouldbelinktupleidtoallowconnectingtoaspe7VlinkparamreportcanbegeneratedatperiodicintervalsbutaVlinkparamtypenowincludesqoslistwhichisasequenceof^VWvWvWWvWvWvWvWvWvWvWvWvWvWvWWWamendmentuWamendmentsW=WLWGWammendmentsWamongWWWGWanWW WWW'WBWEWGWHWbWoWpW߁W߂WߒWߝWߞWߢWߥWߧWߨWߵW߸WWWWWWWWWWW WW%W/W0W6W:WIWJWKWNWSWUWVW`WbWcWfWiWrWuWvWyW{WWWWWWWWWWWWW"W#W&W(W)W,W7W8W;WCWIWRWSWZW[W\W]WbWpW\ vrefersWreflectWWregardingWregisterWregistrationWWregistrationrequestcodedependingontherequestcodetheVrejectWrejectthetechVWrel-7/Wrel-8/Wrel-99/rel-4/WrelateWrelatedWrelevantWreliableWreliesWremainingWremedywWremotewWWWremotely<Wremove,WWWWWWWEWWWWWremove802.15fromfigure1andfrompage4line-14VVremoveapinparenthesisVremoveipconfigstatusfromisquerybutleaveitforotherVremovesection8.2.3.1VremovethedefinitionofhigherlayersVremovingWrenameW2Wrenamemihnon-posnetworkentitytomihnon-pos3.21VrenewalWreplace2W@WW replacebullet5withtheproposedbulletsandaddsometextVreportaWreportingpWreports Wrepresent2WWTechnical,FE Cole, Terry LF DisapproveGGeneral Interest^General_8`36a3.42c1I believe this is already in the IEEE dictionary.d200g5402j6Remove definitions already defined in IEEE dictionary.vDelete this term. (SAP)wAgree{k) done 2007/12/1909/13/2007 15:42:30 EDTYessons L1 and L2 from this Annex. Change the title of this Annex to "Media specific mapping for SAPs" Elsewhere in the draft it is mentioned that medi aspecific enhancements should be included in draft. Remove such statements (pg 23 line 52).w Principle 2007/11/1809/13/2007 15:42:30 EDTMarkedYesFE Cole, Terry LF DisapproveGGeneral Interest^General_8`36a3.42c1I believe this is already in the IEEE dictionary.d200g5402j6Remove definitions already defined in IEEE dictionary.vDelete this term. (SAP)wAgree{k) done 2007/11/1809/13/2007 15:42:30 EDTMarkedYesry LF DisapproveGGeneral Interest^General_8`36a3.42.3.1Qa zyrefDWUW[W\WlWxWyWWWWWWWWWWWWWWWWWW W WW W!W"W#W$W'W,WMWWWWWWWWWWWWWWWWWWWWWWref10supercededVref105Vref105duplicatedVref106VVref106duplicateVref11supercededVref114duplicatedVref141Vref141duplicateVref2superceded'Vref20Vref210Vref227duplicated,Vref260V Vref260duplicateVref277Vref339VVUVref344duplicatedV"VVVref347duplicatedV!VVVref351 VVref351duplicatedVref351superceedVref378Vity, must support L2 MIH transport (but does. 2007/09/1909/16/2007 08:19:02 EDTYes d494g5108OWxMMEMyles, Andrew FF DisapproveGProducer^ Technical_67`64a7.3.5cdelivered when the last possible L2 connection to a specified network is about to be broken. From the definition in the text, a possible interpretation is that a link going down event will be generated whenever an STA makes a transition from 1 AP to another; this is out-of-scope for 802.21 which is facilitating inter-technology and intra-technology (when these are between different networks--e.g., different SSIDs in WLANs) haBndovers.d93g5509jClarify the text.p- text from Vivek emailvRefer to TGu draftw Principle{i) to do 2007/12/0709/11/2007 17:46:47 EDTMarkedYes EMyles, Andrew FF DisapproveGProducer^ Technical_67`64a7.3.5cen these are between different networks--e.g., different SSIDs in WLANs) haBndovers.d93g5509jClarify the text.vRefer to TGu draftw Principle{c) instructions unclear 2007/12/0509/11/2007 17:46:47 EDTMarkedohbayoshihiroDVve that a proposed standard such as this, which is intended to specify mechanisms across multiple other standards, has exactly NO normative references. This is laughable, and to me, simply demonstrates that the document is not ready for prime time. Apart from anything else, the standard appears to be trying to re-define the MAC service. Why is there no normative reference to the existing MAC service definition?nk_Up.indication is from MIHF to MIHF user, not MAC-WLAN to MIHF or PoA-WLAN to PoS-WLAN.d178g4126j@Expand the block to properly include the link and MIH primitives 2007/09/1709/13/2007 13:56:26 EDTYesKcThere are two places where the MIH_Link_Up is used. Neither of which are correct in name or in placement. MIH_Link_Up.indication is from MIHF to MIHF user, not MAC-WLAN to MIHF or PoA-WLAN to PoS-WLAN.d178g4126j@Expand the block to properly include the link and MIH primitives 2007/09/1709/13/2007 13:56:26 EDTYesKqESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_71`54a7.3.10cA MIH is not the only way through which the higher layers and link layers interact with each other. User place functions don't need MIHF involvement. It is logical and perfectly possible for upper layer buffers to receive frame delivery indications from the link layers. d611g4991j"Remove the whole section. (7.3.10)v07 21:41:08 EDTMarkedYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_71`54a7.3.10cA MIH is not the only way through which the higher layers and link layers interact with each other. User place functions don't need MIHF involvement. It is logical and perfectly possible for upper layer buffers to receive frame delivery indications from the link layers. d611g4991j"Remove the whole section. (7.3.10)v)d230g5372jCIncrease the degree of flexibility for usage of the related events._258aH6:30 EDT< UchaveWWWWWWWWWWhaven't WPoS is sendingWWWWWWWfeaturesWfewWfieldW/WfigWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWe}WWWWWW6WݛWW W?WއWޕWެWްW޲WWfigure-7Wfirst܍WܟWܠWWWPW|W}WݽW WfirstintroducesomethinglikeapicssomewhereintheannexVfixW܀W܄WWWWWfixthefontthisisthereisseveralotherplacesindraftVfixthemodellingsothatthestandarddoesn'tplayfastandVfixthepdfand/orthetextsothepagenumberscorrespondVfixthetextV^@v3gppWW/W0W2WW3gppand3gpp2networkshavebeenincludedinthetablecommV3gpp/3gpp2WW3gpp2WWW4W/W2WWW4-2552W40W407}W41<W414-02W42<W427W428W429\W432GW444W471W49W497W8WWWW5WW2WWWWW5-19/W5.1.77WWW5.1.9W5.7.2W5.7.2transportconsiderationsV52aWEW53W55<W556W57<W588W590W6W2WW6.5.5WW6.5.6.26W619WW643/W65<W7&W'WWWWWWWWWWWWWWWWWW02.1W802.11WWWWW,WWWWW802.11u,W802.15WW802.16W,WWWW802.16e<W802.16g,W802.1abW802.2WjusedWWW&W'W2W=WWWWWWWWWWW0W:W;W=WWWusefulWuser>W]W`WiWjWtWwWWWW*WWWuser's%Wusers@WWW%WWWusingWWWWWW(W7WWWutilizescWvalidWWvalueWWW9W=W^WeWW5WJWwWvaluesWWW=WWvariableWHWvariable-length=WvariousWvendor-specificWversaWversionAWveryWWviceWvocabularies.W)cneedWWWW'W4W7W~WWWWWWWW WMWWWWWWWWWneedtoaccountforalocallygeneratedmnhocommitrequest~VVneedtoaddtexttosayhowredundantackmessagearehandleVneedtostateatleastaworkingassumptionorlistof2-3o'VneededW'W9WRWkWlWmWWW=WWWWWneedlessWWWW#W$WWWWWWWWWnmsisusedfornetworkmanagementandistobeastand-alonVVnoWWWWWWWWWWnoinforesponsebinarylisttlvintablec2VnooctetisencodedforthisdatatypethisdatatypeisuseVnoreferencesareprovideddespitethefactthatthisstandaVnodeWWWnodesWnonexistentWnormalizedWnormativeWWWWWWW}'ERudolf, MarianF DisapproveGProducer^ Technical_32`47a5.7.2cANeed to state at least a working assumption or list of 2-3 options for technical solution to MIH transport for 3GPP-based cellular technologies. If this specification is to apply to encompass 3GPP cellular, then an implementor must know which options he can use to realize the needed signalling. Independent of which SDO standardizes the solution, there must be at least a limited set of choices available ?d487g5115jAFor example, assume and describe here whatever MIPSHOP will produce one day can be used as one realization for IP-based external transport interfaces. Alternatively, describe a means to transport at least a limited set of MIH messages through GMM or GTP messages, like Direct Transfer etc., even if any formal specification would be incumbent to 3GPP one day. needa t least to describe or at least outline the principle of 2-3 technical approaches to guide an implementor. The only other alternh>caWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWW!yuuOWPWQWRWSWTWUWVWWWXWYWZW-W.W/W0W1W2W3W4W5W6WzeiraWzeiraeldadVzunigaWWWWzunigajuancVVVVesEJeffree, Anthony AF DisapproveGGeneral Interest^ EditorialDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ EditorialcIThe line numbers are positioned such that the change bars overwrite them.d247g4706j&Move the line numbers left by a few mm 2007/09/1709/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ Editorialeneral Interest^ EditorialcIThe line numbers are positioned such that the change bars overwrite them.d247g4706j&Move the line numbers left by a few mm 2007/09/1709/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ Editoriald246g4707 2007/09/1709/14/2007 08:30:59 EDTKckenichiipconfigurationmethodsdhcpserveraddressfaaddrOVkenichilinkactionreqshouldbelistlinkactionreqQVkenichilinkactionrspshouldbelistlinkactionrspPVkenichimihscanisnotneededbecauseitisoneofthemihRVkenichisupportedlcpisnotdefinedasadatatypeVVkenichisystemparametersisnotdefinedUVkenichitypeieroamingpartnersshouldbesingleroamingpaWVkeptWkeysWkindWkindsWWknowWWWWW'W,WwWWWWWWWknowingWknownmWknowsuWWWlWWWl143Wl2WWWWW W0WcWvWWWWWWWWWWl3W.WcWuWWWWWl323WportionswWposaWWPWpositiveAWpossibilityߊWWWLWpossiblecWߊW߹WHWVWWpossiblyߥWWWWceverytimeWexactWexactlyWWexampleWWW W WWW%W/W0WYWZW]WWWWWWW'W(WWWWWWWWWWWWeWWWWWWWWWWWgeWWWWl3ݘWWwWބWޡWlabelWlanguageWWWWWWl3ݘWWwWބWޡWlabelWlanguageWWguageWWageWWWWlatest&W&W&WW&W&W&W&W&W&W&W&Wt&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&W&WޡWlabelWlanguageWlaptopWlatest&W&W&W&W&W&W&W&WSEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_29`9a5.5.6igure 12, you might want to indicate that the MIH Event Subscription Request/Response and the MIH Command Request/Response do not have to go in the directions they are shown; that the reverse directions are also allowed.d554g5048j1Indicate that the reverse directions are allowed.vThe text description does not say anything about direction in this figure. Both the directions are allowed and tthe text does clarify that...page 34, line 36 wDisagree 2007/11/2609/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_29`9a5.5.6n in this figure. Both the directions are allowed and tthe text does clarify that...page 34, line 36 wDisagree 2007/11/1809/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_29`9a5.5.6s.d553g5049jWLE Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`18a64311c+Consistency: There is no MIH_Configure_Linkd194g5408j?Change to MIH_Link_Configure_Thresholds to match clause 8.6.3.3wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes ME Cypher, DavidF DisapproveGGeneral Interest^ Technical_154`5cACThe broadcasting of this message cannot be consumed by any of the state diagrams in 8.2. New state machines need to be added to permit transmission and reception of this very special case. None of the current state diagrams can be used because they all include the ack/rep bit behavior, which cannot be used in these cases.Cd193g5409jdAdd new state diagrams, or remove this capability and any associated material from the entire draft.psuperceded by comment#11v)Please see contributon 21-07-0302-00-0000w Principley Ref Cmt 11.{k) done 2007/12/1909/13/2007 13:56:26 EDTYesInterest^ Technical_113`53DTtDccompliant/WWWcomplicateWcomplicatedWW[WWcomponentWWcomponents7Wcomprehension<WcomprehensiveWcomprisingWcomputer-basedWconceptWWWWconceptsWconcernedWWWconcerningWWconcernsWconcurrentlyWconditionsWW%WWconfidenceWconfig[WWconfigurableWconfigurationOWgWkWlWmWnWoWWWconfigurationofthemihfisnotspecifiedinthisstandardVconfigurationsWconfigureWLWXWoWWconfiguredWconfiguring[WconfirmWconfirmation^WconfirmingWconflicting/overlapp[WconflictsWconformWconformanceWWWWWWWW!W"WGWHWWWWWWconfusionWconjunction7Wconnect0WconnectedWWWconnecting7Wr"E Cheng, HongF DisapproveGProducer^General_57`1a6c["Negtwork Communication" is not a MIHF Service according to the defintion in subclause 5.3.d492g5110j#Move this to be a subclause of 6.2.wAgree{k) done 2007/12/1909/16/2007 08:19:02 EDTYes#E Cheng, HongF DisapproveGProducer^General_56`1a6cW"Network management" is not a MIHF service according to the defintion in subclause 5.3.d491g5111j#Move this to be a subclause of 6.2.p6The section was removed by change from another commentwAgree{l) none needed 2007/12/1909/16/2007 08:19:02 EDTYesrvice according to the defintion in subclause 5.3.d491g5111j#Move this to be a subclause of 6.2.p6The section was removed by change from another commentwAgree{l) none needed 2007/12/1209/16/2007 08:19:02 EDTYessss=GicalsoiWalternateWWWWalternativelyWalthoughWWWalthoughthisintroductionreferstoieee802.15itappearsValthoughthistextreferstoieee802.15itappearsthattheValtogetherWalwaysWWWWWamWambiguity<Wambiguous0W;WWWWWamendmentWamendmentsWWWWammendmentsWamongIWWWWanWWWWWWWWWWWWW W WW&W'W+W.W0W1W>WAW]W^W_WjWpWtWvWwW~WWWWWWWWWWWWWWWWWWWWWWWWWW WWW#W$WIW|WWWWWWWWWWWWWWWWWWWWWWWWWcreferencedWWW/W4WreferencesWWW WWWWWWWWWEWWreferencingWreferredBWreferring}WWrefersWBWWWWWWreflectWWWWregardWregardingWW&W=W'WW Wregister0WBWregisteredWregistrationWW)WWregulatoryWrel-5/Wrel-6/Wrel-7/WrelateWWrelatedWW]WWW>W?WWrelationshipWkWlWmWWWWWrelationshipsWrelativeWreleasingrWsWrelevanceWrelevantWWW߸WW߸W߸WW߸W߸W߸W߸W߸W߸W߸W߸W߸W߸WW߸W߸W6g4138j!Add blank link between 9) and 10) 2007/09/1709/13/2007 13:56:26 EDTYesWE Cypher, DavidF Disapprove9 2007/09/1709/13/2007 13:56:26 EDTbcusersW@W[WWWW%W*WWusesWWWWWWWWWusingWWWWWWW*WJWhWW0W@WuW}WWWusingthemihprotocolmessagesspecifiedinthissectionis0VusrWusualWusually'WutilizationWutilizeWv3W%WvalueWWWWWWWW.WGW[W^WWWWvaluesWWWWWWFWGW^WvariableWWvariables'WvariousWWWWW$WvaryWW#WvendorWvendorsWWverbose<WverifiedWversionWversionsWveryWWWWWW<W[WWWWWWviaWcWviewedWviolatesWvirtualWvisibleWwWWw-cdma W WW0W3W7WwaiteWwaitingeWWWyE Kim, YonghoF DisapproveGProducer^ Technical_46`44a6.5.1cA_802.21 MIIS supports static information parameters. However, for pratical network selection, dynamic information elemets could be more helpful sometimes rather than querying through its serving PoA(PoS). Therefore, I suggest 802.21 MIIS provide static and also dynamic information. Refer to contribution, 21-07-0315-00-0000-Dynamic_Information_Support_d337g5265jDDiscuss contribution, 21-07-0315-00-0000-Dynamic_Information_Supportw Principle6.5.1cA_802.21 MIIS supports static information parameters. However, for pratical network selection, dynamic information elemets could be more helpful sometimes rather than querying through its serving PoA(PoS). Therefore, I suggest 802.21 MIIS provide static and also dynamic information. Refer to contribution, 21-07-0315-00-0000-Dynamic_Information_Support_d337g5265jDDiscuss contribution, 21-07-0315-00-0000-Dynamic_Information_Supportw PrinciplenghoLcabbreviationsWabilityWWWablexWyWWWaboutWWWWWW<WgWvWWWW'WWWWWWWW W WaboveWFWJWWWabreviationWabritrary1Wabsence6Wabsenceofamedia-dependentsapforgsm/egprsthereisonly6VabsoluteWabstractWWabstractionsWacWacceptabilityWacceptedWaccessWWWW W WWWW&W1W5W6WOWWWWWWW WWWWWWWWWaccess-network-aux-iWaccessibleuWaccommodateWaccomplishWeb-2page176networkerrorisindicatedbVaccount~WWWackWWWWWWWWWW'WWackfailureisnotrelatedtoplrackfailureisatransmitVack-rspWWack/repMWDT~ QjApage 285 line 27 change MIH configure line to MIH_Link_Configure_Thresholds; line 32 change MIH_Link_Parameter_Report to MIH_Link_Parameters_Report; figure K-1 three changes: 1) MIH_configure_link to MIH_link_configure_thresholds, 2) no more InitAction, 3) no more ExecAction); page 287 line 6 remove link from packet error rate; line 46 remove transfer from CoS Packet Delay Jitter; page 288 line 13 change Table E-2 to K-2; line 40 remove transfer from CoS Packet Delay Jitter;wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYesRE Cypher, DavidF DisapproveGGeneral Interest^General_282`45c~Consistency for NAT. Does NAT stand for Network address Translation as in line 45 or Network Address Translator as in line 64?d188g5414j Use one method and stay with it.pSecton was deleted.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes SE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_282rial_282rial_282R ,ctheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWWWW W!W"W#W$W%W&W'W*W+W,W.W0W7W<W=W>W?WAWBWCWDWEWFWGWIWJWKWLWMWNWRWYW[W\W]W^WaWbWeWfWgWkWlWmWnWoWpWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWW 6csometechnologiessuchas3gpprequirethepreparationofreVsomehowWsomethingWW]WWWsometimesWsomewhatWsomewhereWWWsoonWsort2WsortedWWWsouldWsoundWWWsoundsWWWsoundslikeyouareattemptingtore-definemechanismsthatVsourceCWDWEWJWKWLWMWNWWWWWWWWWWW Wsource/destinationWsparql-results<WspeakWspeakingWspecWWWW&WWWWWWWW WspecialMW WspecificWWWWWWW WWWW^WWWWWW(W)W7WWWWWWWWWWWWWWWWGGeneral Interest^ Technical_55`3a6.5.6.3d316g4637 2007/09/1709/14/2007 23:15:41 EDT>EEastwood, Lester FF DisapproveGProducer^ Editorial_36`48a6.3.1crepeated statementsd109g5493jZdelete "MIH events may be local or remote. Remote MIH events originate at a remote MIHF. "{k) done 2007/12/1909/12/2007 02:37:36 EDTNoEEastwood, Lester FF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d108g5494joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1909/12/2007 02:37:36 EDTYes EEastwood, Lester FF DisapproveGProducer^General_33a6.2cAThe concept and procedures for MIHF discovery are only discussed but are not specified in this spec (i.e., no mandatory messages/flows defined for MIHF discovery). This is the right way to do it. Just the text and title in 6.2.3 and 8.2.3.5 may mislead readers otherwise.d107g549555494rcbeyond7Wbibliography WbinaryWWWWZWW6Wbinary-encodingYWbinding(WbitWWWWWW@WMWNWnWoWsWWbitmapWXWWWbits=WWtW Wbits34and5arenotinthesamemeaningorderasforthetVblerWblieveGWHWblockWblocksdWbodyW/WbookmarksWbothWWWW$W6W@WFWIWcWgWW%WWWWWboththesubclause5.3and6aresimplynamedmihfservices$VboththetermmihfunctionandmihfunctionsareusedinthiVbottomWboundariesWbracketWbreakuWbringWvWWW$WWbringsWW#WWbroadcastWW WWWbroadcastedWWbroadcastingWMWW0W6W7WFWaWeWqWvWWWWWWWW*W^@b@Rv@@@@acBJa@`@@?@bE@*ca@ @G?@Ajy@G[@c^>@cAj@@<jP@@GTcAOcAvv@ve@UcA@%cA@c\cAcr@v[c@ZcAYc@icBR@@@cA`vA@1j@vA@@cH@H{B@cASjA@cA@vr@VjA_@@cAr@W@wvV@lvAO@5@-@K@S`45cConsistency Address or addressd187g5415j Use one method and stay with it.pSecton was deleted.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes TE Cypher, DavidF DisapproveGGeneral Interest^ Technical_281`8cIThe MIH_N2N_HO_Complete does not cross the R1 and R3 as currently definedd186g5416jDelete R1 and R3wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes UE Cypher, DavidF DisapproveGGeneral Interest^ Technical_281`6cLThe MIH_MN_HO_Complete message may be sent to the target POS as per page 228d185g5417jAdd R2wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes VE Cypher, DavidF DisapproveGGeneral Interest^ Technical_280`60cPThe MIH_N2N_HO_Query_Resources does not cross the R1 and R3 as currently definedd184g5418jDelete R1 and R3wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes W W W W Wdressd1878ccom/morris/glossaryWcombinationwWWcombinations&WcombinedWwWcome$Wcomes_W`WcommaWWWcommandWWW7WfWwWxWyWWWWWWW W W*WsWWWWWcommand'sWWcomputer-basedWconceptWWconcernedWconfidenceWconfiguredWconnectionWconnectionsWconnectivityWconsistentWcontainWWWcontainerWWWcontinueWcontrolWcorrectWWWcorrespondinglyWcosWcosisnotincludedinlistofabbreviationsVcouldWcountWcounterWcounterpartWcountersWcriticalWWcuriouslyWcurrentWcurrentlyWdataWWWWWWWWWWdatatypeWdatatype1Wdatatype2WdcdWdecidesWdecisionWWW$vin{W}WWWWWWWWWWWWWWWWWWWWWWWWW W W WinmnhocommitconfirmVVintableb-4page182lines5and36addthefollowingsenteVinthedocumentthetermlinkgenerallyreferstoalogicalVinclude,WWWWincluderesourceretentiononlywhenthemessageissentinVincludedWW W WEWWWWincluding&W'WWWWincompatibilityAWinconsistencies&W'WWWWincorporateWincorporatethenewreferencediagramfromtgudraftVincorrectWincrease1Wincreasethelengthtounsignedint21VincrementedAWindicate/WiWindicatesW W WWWWindicationWeWfWtWwWWWAWindicationsWindividualWinferWinferences5WWinfo}jaddthefollowingsentenceorsomethingsimilartotheparagVaddthefollowingsentencetotheendoftheparagraphseea4VaddtheoptionthathoresourcereservationcanberequestedVVVVaddthemVVaddthiscapabilityVVVVVVVaddtosection8.2.3.5.1page149line42sincesendingorlVaddunderscorebetweenpacketandtransferrVaddwwancellidtothelistofentriesonb-9VaddedWWaddingWadditionWadditionalWWW.WWadditionallyWaddressW WgWkWlWmW|WWWWWaddressedWadjustWWWWadjuststatemachineVVVadjustment=Wadjustments=WadmissionWadoptWWBWadopt21-07-0226-00-0000-mregistartionnitsthisisjustanBVadressWadvertiseWaffectWafterWwWWWWWWg4713OcypherdavidIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVVVVVVVVVVVVVVVVVdavidWWWWWWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWeastwoodWWWWWWWWWWWWWW17QE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_121`43ctypod22g5580j#replace LINK_ACTIONS w/ LINK_ACTIONpFix the parameter name also.{k) done 2007/12/1909/04/2007 16:19:39 EDTNo E Golmie, NadaF DisapproveGGovernment/Military^ Technical_118cA The parameters in the primitives cannot be filled properly upon receiving an MIH_Link_Detected. MIH_Link_Detected provides the Link identifier (LINK_TUPLE_ID) of the detected link. The PoA indicated is the detected PoA.It does not provides the current link identifier d21g55818cA The parameters in the primitives cannot be filled properly upon receiving an MIH_Link_Detected. MIH_Link_Detected provides the Link identifier (LINK_TUPLE_ID) of the detected link. The PoA indicated is the detected PoA.It does not provides the current link identifier d21g558121g558121g5581E Golmie, NadaF DisapproveGGovernment/Military^ Editorial_182`57'olveraWolveraulisesVrthisfieldthedestinationmihfwill`V`V`V`V`V`VߴW6W8WdstWdualtWdue'WNWduplicateZW_WduplicationWduring WWdynamic4WdynamicallyߒWeW W!W&W߰WWWWWWWWWWWWWW.WeachWWW"WDWEWOWPWRWTW߂WW:Weachbitofabitmapnvaluen8ii12isencodedasannEVeachcharacterisencodedinorderofappearancewhereeachDVeap߮WearlyYWeastAWec/io߅WeffectWeffectiveߴWefficientߴWeffortߴWegprsߧWegprs/w-cdmaߧWeitherQWsWW`WelementWJWKWelementsW=Welemets4WeliminateXWeliminatesXWelse|W߅WemergencyWemphasise߷WemsWenableTWWWexhibit WexistedWexistingW[cthemihn2nhocompletedoesnotcrossther1andr3ascurrTVthemihn2nhoqueryresourcesdoesnotcrossther1andr3VVthemihnethoqueryrequestprimitiveisinvokedbyanmihVthemihprotocolisinadequatelyspecifiedinparticulartheVthemihprotocolreliesontheunderlyingmechanismsietheVthemihservicesdefinedbytheieee802.21standardincludiVthemihxxxrequestshouldneverybeusedbythemihfitis VthemihfscopefunctionblockisincorrectlyplacedinconteVthemissingdefinitionmustbefilledVthemobilenodeiscapableofsupportingmultiplelink-layerVtheneedanduseofthemihnethocandidatequerycommanda Vthenumberofoctets27isnotcorrectusingthenumbersconuV007 18:36:55 EDTNolE Julka, VibhorF DisapproveGProducer^ Technical_65`49a 7.3.2.2.2capproveGProducer^ Technical_65`49a 7.3.2.2.2cd281g4672 2007/09/1709/14/2007 18:36:55 EDT ᆃᇃሃቃኃዃጃፃᎃᏃᐃᑃᒃᓃᔃᕃᖃᗃᘃᙃᚃᛃᜃᝃឃៃ᠃ᡃᢃᣃᤃ᥃ᦃᧃᨃᩃ᪃᫃ᬃᭃᮃᯃᰃ᱃ᲃ᳃ᴃᵃᶃ᷃ḃṃẃểἃὃᾃῃƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ cAWhen more than one PoA container is present, it is important to specify if the there is any meaning to how to the list is populated or if it is random. It is beneficial to the receiver of this information to know this so it can apply this information for network selection and decisions.d605g4997jAAttach an explicit statement to line 49 that "When more than one PoA Container is provided in this IE, they shall be prioritized in the order of preference from the information server's perspective with first PoA Container as the top priority and with decreasing prority going down the list. This would enable the receiving entity to untilize this information in the same order as provided in this list for network selection or handover decisions."v5w Superceded 2007/11/1509/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`49a6.5.5.2c\ÃT`[ing message to list 2007/11/06BVjclarifyifcommandsareallowedtobesentfrommihftomihVclarifyifcos-idareconsistentlyrepresentedacrossallliVclarifymappingtransportaddresswithmihfidVclarifyorcombineVclarifyorre-writeVclarifyorremoveVclarifyorrephrasebemorepreciseVclarifyorrephraseparagraphVclarifythattheoldlinkactionsreferstothedestination}VclarifythefigureorthecaptionifthecaptionisclarifieVclarifythefunctionoftheregisterfeatureiedoesitpaiVclarifythetextVVVVWWWWWWLWXWWclausesWclear WGWclearly W WWW7WWWWclearlydefinetheinfoquerybinarydataieorifitexistsadVclearlystateif802.16providesamechanismsimilartothe VclearsWcleverWcode4W_WWcodesWcodingWcollapsed%WcolumnWWW:WcbroadcastsWbrokenWWbssW7WbufferW WbuffersWbuild,WbuiltWbulletsWburied WbusWbusinessWbusyWbutWWWWWWWW WWW0W6W7WFWaWeWqWvWWWWWWWW*WWWWWWWWWWWWWWWWWWWWWWnctions and design. 2007/09/17q_/jinvestigateWWWWWhowtore-organizethedatatypedefinitionseitVinvestigateifthiscapabilityisneededandhowtobestimpVinvestigateifthiscapabilityisneededandthebestwaystVinvokedWinvokesjWipW W&WgWkWlWmWWip-based'W+Wipaddressinformation>W?Wipconfigurationmetho?WisWWWWWWWWWWWWWWWWW W W WWWWWWW&W'W(W)W0W7W=W?WBWGW]W`WbWfWhWvWwWxWyW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW0W:W;WDWJW^WcWWWWisn'tWissuetWwWW4'cwhyWWWWW WW8WeWfWgWWW'WJWYW[WmWWWWWWW Wwhydoesamihmnhocommitrequestmessageproduceamihne[VwhydoesthemobilenodeneedtoknowtheipaddressoftheVtthiscontainershouldhaveatleastVwhyistherenonormativereference8VwhythereisaseparatemacaddressfieldinmihmnhocommiVwhythisrequestcontainsmoreinformationaboutresourceregVwhywouldthelinklayersmacmakehandoverdecisionsevenfVVwillWWWWWWWWWWWW&WkWlWmWWWWWWWW WWW$W/WWWWWWWwillthedifferentcosidberepresentedconsistentlyacrossVwimaxWW_W`WwiredWWWwirelessW W/WWW%WWihhandoverprimitivesxVlj"For example, the occurrence of a handover of a mobile node from one access network to another will result in the reestablishment of a link layer connection to the target access network."{k) done 2007/12/1909/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_35a6.2.5cFigure 12, you might want to indicate that the MIH Event Subscription Request/Response and the MIH Command Request/Response do not have to go in the directions they are shown; that the reverse directions are also allowed.d554g5048j1Indicate that the reverse directions are allowed.vThe text description does not say anything about direction in this figure. Both the directions are allowed and tthe text does clarify that...page 34, line 36 wDisagree{l) none needed 2007/12/1909/16/2007 15:56:25 EDTYes s s gle radio/dual radio case and provide solution for both cases.wDisagree 2007/11/14erest^ Technical_33W-ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_32`44a5.7.2cIs the recommendation valid? 802.11 is not providing any management frame extentions other than for Information services and entity discovery/d597g5005jYmay be either carried using media specific link services or using higher layer protocols.psuperceded by change from 45wAgree{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYessal Interest^ Technical_32`44a5.7.2cIs the recommendation valid? 802.11 is not providing any management frame extentions other than for Information services and entity discovery/d597g5005jYmay be either carried using media specific link services or using higher layer protocols.psuperceded by change from 45wAgree{l) none needed 2007/11/2609/16/2007 21:41:08 EDTMarkedYestocols.psuperceded by change from 45wAgree{l) none needed 2007/11/2609/16/2007 21:41:08 EDTMarkedYesDT}lXjanWWWWWW WWWWW&W'W1W^WbWgWjWwWWWWWWWWWWWWWWWWWWWW W*W8WBW|WWWWWWWWWWWWW WWWWWWWWWWWWWWWWWWWW W W WWWWWWWWWW%W&W'W(W+W,W.W1W2W3W5W7W8W;W<W=W>W?WDWEWFWIWJWOWRWSW[W]W^WaWkWlWmWtWvWzW{W|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWt^ERajkumar, AjayF GProducer^ Technical_75`59cA7LINK_PARAM_TYPE now includes QOS_LIST which is a sequence of parameters that contains actual values and is not a mechanism for asking for a specific value. Similarly, the confirmation is a LINK_PARAM which contains the type and value. However the value is an UNSIGNED_INT2 which is unable to contain a QOS_LIST.7d432g5170jChange QOS_LIST to LINK_PARAM_QOS_LIST. Add LINK_PARAM_QOS_LIST with an enumerated type and a value of 0 requesting the return of QOS_LIST. QOS_LIST which is a sequence of parameters that contains actual values and is not a mechanism for asking for a specific value. Similarly, the confirmation is a LINK_PARAM which contains the type and value. However the value is an UNSIGNED_INT2 which is unable to contain a QOS_LIST.7d432g5170jChange QOS_LIST to LINK_PARAM_QOS_LIST. Add LINK_PARAM_QOS_LIST with an enumerated type and a value of 0 requesting the return of QOS_LIST.:23:06 EDT(jtype/id=WtypesWWW=WWuir@WulWumtsW3WunambigouslyWunambiguousWunavailableWWunified@WuniformWuniqueIWunitBWunitsWunrecognizableWWunsignedW1Wunsignedint2unsignedint21VunsolicitedWWWunsubscribeWWunsubscribedWunsubscriptionWuntilWuntilizeWWup W7WaWW+W,WWupdateWWWWW)W^WcWWupdatesectionwithtextonsecurity)VupdatethedefinitionoflinkidtoindicatethatthelinkaVupdatethediagramanddescriptiontoincludethe802.11autVupdatethenormativereferencelistVupdatethestatediagramtomatchthetextdescriptionVVupdatedWupdtaeWupdtaefigure-7andsection5.5.3VuponWtWWupperwWWurlWusage(WWusagesWe MIHF.tEMeylemans, MarcFApproveGProducer^ Editorial_71`36a7.3.9.2c^the set of link layer parameters is not specified in 7.3.3, only the primitive is listed thered374g5228jochange text to 'The primitive to set parameter thresholds that could trigger this event is specified in 7.3.3.'wAgree{k) done 2007/12/1909/16/2007 02:47:09 EDTNo o cified in 7.3.3, only the primitive is listed thered374g5228jochange text to 'The primitive to set parameter thresholds that could trigger this event is specified in 7.3.3.'wAgree{k) done 2007/12/0709/16/2007 02:47:09 EDTMarkedNo 7.4.17.2.2cTypo in LINK_SACNd376g5226jcorrect to LINK_SCAN 2007/11/1409/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_96`22a 7.4.12.1.2c!missing bracket in UNSIGNED_INT2)d375g5227j-add missing opening bracket - UNSIGNED_INT(2) 2007/11/1409/16/2007 02:47:09 EDTNo 'EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_78`64a 7.4.1.1.2c#"List of supported events on MIHF."d557g5045j-"List of supported events on the local MIHF."wAgree{k) done 2007/12/1909/16/2007 15:56:25 EDTYes s Chaplin, Clint FF DisapproveGGeneral Interest^ Editorial_78`64a 7.4.1.1.2c#"List of supported events on MIHF."d557g5045j-"List of supported events on the local MIHF."wAgree{k) done 2007/12/0709/16/2007 15:56:25 EDTMarkedYes rted commands on MIHF."d558g5044j/"List of supported commands on the local MIHF." 2007/10/3109/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_78`64a 7.4.1.1.2c#"List of supported events on MIHF."d557g5045j-"List of supported events on the local MIHF." 2007/10/3109/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_69a7.3.6c0g5042<vEEmmelmann, MarcF DisapproveGAcademic^ Editorial_6`59a3.14c?singular or plural should be used ("changing link implies ...")d28g5574jIChange either to "changing A LINK implies" or to "changing LINKS implies"{k) done 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Editorial_6`38a3.8c.no capitalization of "internet protocoel (IP)"d27g5575j#change to: "Internet Protocol (IP)"pCmt 30 deleted the definition{l) none needed 2007/12/1909/10/2007 07:08:58 EDTNoE Zeira, EldadF DisapproveGProducer^ Technical_304aAnnex KcAnnex K is informative and does not enforce uniform mapping of QOS parameters by different vendors. Preventing unpredictable behavior will require vendor - specific solutions which will complicate testing and delay market acceptability.d26g557626g557626g5576echnical_304aAnnex Kers" and b/ "MIH Users"d30g5572jj5.1.77WW5.1.8W5.3$W5.5.27W5.5.3W7W5.6.2.6W5.6.3.2W50WWW50-74W50mNW51=W55W55-56W57W580W59W6WQWWW6-14+W6.2"W#W6.2.1*W6.2.3WW6.3.2WW6.3.3WWW6.5.5W6.7W60iW61W62W63W64XW65W66[W7WW3W7.1W7.1.1 W7.2^WcW7.3W7.3.10W7.3.3W7.4.18RW7.4.19.3gW7.4.20.4.2OW7.4.21.3.2OW7.4.21.4.2OW7.6WW71[W\W75-100W8WWWWWWWWWWWWWWWWW8.2.2.2W8.2.3.5.1W8.3W8.3mihprotocolstepsV8.3.1W8.3.1informationqueryV8.3.2W8.3.2resourceavailabilitycheckV8.3.3W8.3.3resourcepreparationV8.3.4WW~Mjattableb-121replacebitmap64withrevisionintherawoXVattachWWattachanexplicitstatementtoline29thatwhenmorethanVattachanexplicitstatementtoline49thatwhenmorethanVattachmentWattributehWauthenticateWauthenticated W Wauthentication W7WWWWauthenticatorWauthorisationWauthorizationWauthorizedWauxWavailabilityW1709/13/2007 13:56:26 EDTYes{E Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`20a64311c). However the expanded view contains Operator_1d130g4174jChange Operator_1 to Operator_2 2007/09/1709/13/2007 13:56:26 EDTYes{E Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`20a64311cnterest^ Technical_44`20a64311cd129g4175 2007/09/1709/13/2007 13:56:26 EDTwcthechangebaratleftsideshouldnotappearinthisdraft!VtheconceptandproceduresformihfdiscoveryarenotspecifVtheconceptandproceduresformihfdiscoveryareonlydiscuVthecontentsofpoasysteminformationiearenotdefinedwiVthecontentsoftableb-13attemptstodefineaccesstechnolVthecurrentcommandserviceallowsforqueryingofavailable*VthecurrentlinkidentifierisinconsistentwiththeotherhzV{Vthedefaultmimetypevalueisincorrect:V;VthedefinitionofnmsnetworkmanagementsystemisnotdefinVthedescriptioncontainsthisidentifiesthecurrentlinkfoCVVVVthedescriptionofthesourcelinkidentifierandtargetlinKVLVMVNVthedescriptionsforinfoquerybinarydatalistinfoqueryVthedestinationofaneventisestablisheddynamicallydoesVxT{e) editor disagrees 2007/12/1909/16/2007 02:47:09 EDTNo 209/16/2007 02:47:09 EDTNoo~E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_138`24a75112cOCTECT_STRING?d143g5459j OCTET_STRINGwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s gree{k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedYes ncthereisalackofapositivepredictivemiheventmihlink+VthereisaperiodinfrontofthesentenceVthereisareferencetomihuserthatisinchargeofmnhoiVthereisnoactiontypetoperformintra-technologyhandover8VthereisnobitforlinkactioncommandsVthereisnohandoverackparameterortlvinthemihmnhocaYVthereisnoinformationaboutaccessnetworkidentifierwhicVthereisnoinformationelementdefinedhoweveritmaybeapVthereisnolinkactionsdatatypeitmustbelinkactionVthereisnomihconfiguremessagewiththisnameXVthereisnomihlinkactionsmessagecorrespondingtoclausWVthereisnominmncommitrequestbVeVfVthereisnomobilitymanagementieinthiscontainerVthereisnoneedtomakeanexceptionfor3gppand3gpp2andVthereisnotransactionstatediagramforbroadcastmihcapaVWߑWfamolaridavidߌVߍVߎVߏVߐVߑV109/14/2007 17:39:46 EDTYes s 141`1ccZTable K-2 does not provide a very comprehensive mapping between 802.21 and 3GPP parametersd278g5324jReplace the column that provides the mapping between 802.21 and 3GPP technologies by a different table as defined in 21-07/321r0v Accept 21-07-0321-00-0000 The link packet error rate is computed on the aggregate classes. Are parameters mapped to CoS really computed per class of service? (only Transfer Delay and Maximum Transfer Delay) w Principle 2007/11/1809/14/2007 17:39:46 EDTMarkedYesEZuniga, Juan CF DisapproveGProducer^ Technical_141`1cervice? (only Transfer Delay and Maximum Transfer Delay) w Principle 2007/11/1809/14/2007 17:39:46 EDTMarkedYesEZuniga, Juan CF DisapproveGProducer^ Technical_141`1cnciple 2007/11/1309/14/2007 17:39:46 EDTYesEZuniga, Juan CF DisapproveGProducer^ Technical_141`1cion 8.d280_wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes `E Cypher, DavidF DisapproveGGeneral Interest^ Technical_266`50csThe Link_Action.request is sent to MAC_WLAN, however the corresponding Link_Up.indication comes from the MAC_WiMAX.d174g5428j"Change to arrive from the MAC-WLANwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes aE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_263`47cDMIH_Link_Parameters_Report.indication is not a message between MIHFsd173g5429j+Remove period between Report and indicationwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes bE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_261`19c!There is no MIN_MN_Commit.requestd172g5430jMIH_MN_HO_Commit.requestwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes cE Cypher, DavidF DisapproveGGeneral Interest^General_261`36_261`36_261`36_261`36_261`367AjreplacethisparagraphwiththeprimitivesdefinedaspartoVreplacewith802.11terminologyVreplacewithnotificationfromeithersourceortargetmihfdVreplacementWreplacing>WAWreportWQWaWreportedWreportingWreportsWWWWrepresentationWWrepresentedWWreqWreqiredWexample, how would THRESHOLD map to the 802.11 Beacon RSSI ? Or is this described somewhere else in the draft and CI skipped over it ?y= calongnWoWqWqWqWqWqWaqWqWqWqWqWqWqWqWqWqWqWqWetpWWWWW WWtargetpoaqWqWqWetpWWWWW WWtargetpoaqWqWqWfinedaslinkidinnethocommitsappage1targetpoaqWqWqWqWqWqWdundantasitcouldbeincludedinthetargetargetpoaqWqWqWqWqWqWqWqWqWqWqWoaqWqWqWqWqWqWqWtcp/ip#WludedinthetargeVtargetpoa<WqWtcp/ip#W#W#W#W#W#W#WedinthetargeVtargetpoa<WqWtcp/ip#W#WtechnicalWߝWߞWtechnically߮W߷WtechnolgyߔWtechnologieSWtechnologiescWdW߂W߄W߅WߔWߝWߞWߨW߭W߮WpWWGWJWNWtechnologycW߅W߬WWW:W;W=WWWGWJWPWQWSWXcThe number of QoS levels of service is not defined for 2.11 in Table K-1. 802.11 TGk defines Available Admission Capacity as an indicator from an AP to the BSS of the ability of the AP to admit new services at various QoS levels.d634g4968j=Use Available Admission Capacity for Supported number of CoS.vAdd available Admission Capacity for Supported number of CoS in table K0-1 Need more text from Nada Golmie Please refer to contribution 21-07-0375 wAgree{k) done 2007/12/1909/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_284`53aKc,CoS is not included in list of abbreviationsd633g4969j Add it there.paddedwAgree{k) done 2007/12/1909/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_287`3aKcJoseph AF DisapproveGGeneral Interest^ Technical_287`3aKc`3aKc`3aKc&cthe@SRuqthe802.21specseemstodoagoodjobofdefiningamechani@wthechangebaratleftsideshouldnotappearinthisdraft@thediagramdoesnothaveanymihusersaretheupperlayers@theequationpresentedforatdmpduisnotcorrectdividingt@*theieee802.21standardspecifiesmihfunctionthatcouldb@themihn2nhocompletedoesnotcrossther1andr3ascurr@thenumberofqoslevelsofserviceisnotdefinedfor2.11@[thepurposeandusefulnessofmihnethocandidatequerycom@thesentencebeginningwithsincetheseemstostatethatpr@thetextincludelocalmihfhowevertheregistrationisbetw@=thetextstatesthatalinkparametersreportindicateschan@ /there@ithereisalackofapositivepredictivemiheventmihlink@thereisnowayforthiseventtoindicatethatitwasgener@ntherefore@thing@GpEGiesberts, Pieter-PaulF DisapproveGProducer^ Technical_150`60a8.4.1cPMIH Protocol header is of fixed length, as indicated in fig 27 on the next page.d239g5363jBcorrect figure 26 to show MIH Header has fixed length of 8 octets.psuperceeded by comment #454wAgree{k) done 2007/12/1909/14/2007 03:15:28 EDTYes EGiesberts, Pieter-PaulF DisapproveGProducer^ Technical_105a7.4.19cMThe Purpose and usefulness of MIH_Net_HO_Candidate_Query command are unclear.d238g5364jJremove definition and all occurences of MIH_Net_HO_Candidate_Query commandpSuperceeded by 260.v by 260.vuperceded{l) none needed 2007/12/0709/14/2007 03:15:28 EDTMarkedYes 2007 03:15:28 EDTMarkedYesis mandatory and which is optional under concerning inter-operability among different vendors developing the IEEE 802.21 compliant modules.d240g5362rd HF DisapproveGProducer^ Technical9/11/2007 17:47:21 EDTarq߂WarreyW cand$W%W)W/W6W?WIWMWTWVWdWgWpWtWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWd contains XML text". This sentence is out of context.d210g4743jDelete the sentence. 2007/09/1709/13/2007 16:03:47 EDTYes7 EDTYesEOhba, YoshihiroF DisapproveGProducer^ Technical_198`36aB.2.9cy"When the MIME type is "application/ sparql-results+xml", this field contains XML text". This sentence is out of context.d210g4743jDelete the sentence. 2007/09/1709/13/2007 16:03:47 EDTYesjDelete the sentence. 2007/09/1709/13/2007 16:03:47 EDTYesd209g4744 2007/09/17;~jtotoendofline16addfollowingtextandnotwithinthescopVto/fromWtogetherWtoolsWtopWWtotallyWtransactionWWtransactionsWIWtransferW'WAWQWjWkWrWtransitionWWtranslationWtransmissionWtransmittedWtransparent(WtransportWWW&W'W(W+WcWWWCWWWtransportofmihmessagesoverieee802.11andieee802.16c(Vtrasnmit Wtrasnport&W+W7WtrchWtriggerWtriggers?WtruevWWtryWtsapWtuple7WtwoWWdWWtypeWWWWWW=WGWXW^WhWiWkWlWmWWWWWW+W,W5W8W:W;W=WDWWWWWW WiptionVVupdtaeWupdtaefigure-7andsection5.5.3VuponWtWupperwWurlWAfwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTMarked gE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_231`1c~Many figures are missing the vertical/horizontal lines indicating where the messages and primitives are started and terminatedd167g5435jHPlace blocks in correct drawing software order so that the lines appear.wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTYes hE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_228`47c,Consistency with paragraph/bullet conventiond166g5436j!Add blank link between 9) and 10)wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTYes iE Cypher, DavidF DisapproveGGeneral Interest^General_226`1cDAnnex needs to be update for consistency to the rest of the documentd165g5437jLpage 226 line 60, missing list in supported_lcp; missing mobility managementp6Kenichi is will modify the figure based this revision.wAgree{h) defer to next round  ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃⺃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{IcbeWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWW W&W'W*W/W0W2W4W5W6W7W=WOWPWQWTWWWZW[W]WaWcWeWhWjWkWlWmWpWqWrWsWuWwWxWyW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWW&W'W(W.W/W0W4W6W7W9W>W?WCWDWGWHWIWMWNWOWQWUWiWjWkWpWWWWCcreserveWjayF GProducer^ Technical_128`22c"The "may" makes it sound optional.d392g4561jChange "may" to "shall" (i.e. always generates an indication when a request is received and always generates a confirm when a response is received, from peer MIHF). 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_128`22c"The "may" makes it sound optional.d392g4561jChange "may" to "shall" (i.e. always generates an indication when a request is received and always generates a confirm when a response is received, from peer MIHF). 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_128 "may" to "shall" (i.e. always generates an indication when a request is received and always generates a confirm when a response is received, from peer MIHF). 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_128d391g4562 2007/09/1709/16/2007 03:08:31 EDT]ccorrected2W4WWcorrectlyWcorrectnessWcorrelateWcorresponding WgW~WWWWWW_W`WWWWcorrespondinglyWcosWWFWqWWcosidisvalidbetween0-255thereforeitneedstobesetaVcosisnotincludedinlistofabbreviationsVcouldWW WeWgWqWwW|WWWWWWWWcountWcounterWcounterpartWcountersWcountryWcoupledWcouples W WcourseWcoverageWNWWWWcoveredWWcpichWcreatetWcreates[WcriticalWWcrossTWVWWcross-referenceWcrossed[WWcrossing[WcsWWcuriouslyWcurrentWW=WCWDWEWaWzW{WWWWWWW*WMWWWWWWWW07/09/1709/12/2007 02:37:36 EDT1 vAThe definition of a term (link switch, handover) in this section does NOT define the scope of the standard. 802.21 primarily deals with vertical handovers and not horizontal handovers. For description of scope of this standard please refer to clause 1.1 and 1.3 (second paragraph)wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYes snly receive a link-down indication when the STA become disassociated from the ESS (or is about to become disaBossociated from the ESS). This is because MIH is concerned about roaming between networks and NOT L2 transition.]d76g5526j:Correct the figure and the resulting reference model text.v4Incorporate the new reference diagram from TGu draftw Principle 2007/11/1809/11/2007 17:46:47 EDTMarkedYesEMyles, Andrew FF DisapproveGProducer^ Technical_6`57a3c2.21 is really trying to accomplish.Vd781 is really trying to accomplish.Vd787sW ZjmisunderstandingWWmlmeWmlme-sapWmmWmnWWWW&W2WJWbWgWwWxWyWWWWWWWWWWWHWNW[WbWeWfWWWmn'sWmobileWWW WWW%WmobilenodemncommunicationVmobility<WiWjWxWWWmodelWWmodellingWmodelsWmodifyWWmodifyarrowtextfrominittoreceivedtoreadrecvreqVmodifythesecondsectionoftheparagraphtostatethattheVion8.2.2toannexVmovethistobeasubclauseof6.2"V#Vmoving W5WmultipleWWWmust&W5W7WWmutualWmutually]WnWWn/8Wn2nWWWJWjWWWWnaiWname4WzW{WWWnames2WnativeWnecessary=Wate=WWsequence#WWservߵW߸WnDKjbotWWbothWW&WDWEWJWzW{WWWYWWboxesWbracketWbreakwWbrief+Wbring7WbroadcastWWWWWbroadcastedWbroadcastsWbsic4WbssWWbtsWbut WW&W/WeWwWWWWbyWWWWWWW,W4W7W=W>W@WAWBW`WcWwWWWWWWWWWWWWWWWW}WWWWWWWWcalculateWcall&WcalledGWcanWWWW&W'W(W+W7WWW WWWcandidateWgWkWlWmWWWWW W WWWWcandidatesWWcannot&WcapabilitiesWW]WcapabilityWWWWWWWWCWDWMWWWWWWWWbajkogaborVVVVVVbarrWbarrjohnrVbenjamin&W'W(W)W*W+W,WbrianWcWWWWchan-wahWchaplinWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWs23-43fordiscussionremovingWreorderWWWWWWgWreorderWWWonVVremovedUWremovingWreorderWWWremovedUWremovingWreorderWWWWreorderWWWonVVremovedUWremovingWreorderWWW5throughoutthedocumentreorderWWWWWW5asj1j5throughoutthedocumentVreorderWWWWWVreorderWWWesent!Wrepetitive*WrephraseWZjprovideadditionalnormativerequirementsrelatedtotheuseVVprovideadditionalrequirementswhichwilldefinemihfserviVproviderequiredmihproceduresinsteadofjustexamplesofVprovidethecapabilityforthemih-capablemobilenodetobrVprovidedWW,W7WWWprovider>Wprovides WWWWprovidingWprudentWpsc4WpublicationWpurposeWpurposes WputWputbackthetextVqosWW5WFWGW^WkWlWmWqWqueryWWWZWgWjWWWWWWWW WW WDWKWWWWquestions@WclausVrangeWWrangesWrateWWWFWratherWvWrawXWrdf.W0W4Wre-organizeWre-use1Wre-writeWWre-writedefinitiontodescribethefunctionandresultsVre-writingWre-writtenW disapproveʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㐃㑃㒃㓃㔃㕃㖃㗃㘃㙃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒ.interesthWiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWng, not eliminates it.d301g4652jModify the second section of the paragraph to state that the protocol minimizes the scanning required to discover and select another network as a handover candidate. 2007/09/17ne57p207ށVށVށVށVdstypenameހVremoveciviclomethodline57p207ށVށVށVVljreplace@replacemaynotwithneednotorwordingwithsimilarintent@replacethisparagraphwiththeprimitivesdefinedasparto@request@Arespective@restrictdescriptionofmihacknowledgementoperationtothe@2retransmitted@roll-up@scope@qsection2@Fserver's@!sets@(several@[service@9sets@several@#see@service@zesponse@resulting@_sap@Zsee@service@z_sap@Zsee@service@z_sap@Zsee@service@zservice@z@z@zzer's@z1jincludethingslikecontexttransferandbearerpathsetupaVincludeupperlayersasthemihusersasdefinedin3.23VincludedWWW5WWincludesWWincompatibleWincorporateWincorporateasecuritymethodduringtheregistrationprocesVindicating_WdWWindicationW WeWtWWWindicationsWindividual&WinfoWinfoquerybinarydataWinformationWWWWWW7W>WAWgWkWlWmWWWWWWWWinformational9Winformative%W<WinitWinitiatingWinitiationWinlcude8Winlcudeasaminimumthelatest802.11roll-upandforexamp8VinsertW-W.WinsteadWWintWintegralWintegrateWintegratemihnetsapandmihlinksapintomihlowersapitVintendedWintendendKWLWMWNWVtableb4VV1 eastwoodWWWcer^ Technical_121`32cIn order to be able to perform a local handover (i.e. replacement for switch command) the destination MIHF ID would not be remote.d406g4547a local command). The MN_HO_Commit command could issue to Link HO Imminent at the beginning of the processing of this command. However, we still have a couple of problems. The local MN_HO_Commit command does not have any Link Actions so it would have to be driven by MIHF but it doesn't know whether it should be maBke before break or break before make. Also, we are still left with the problem of knowing when to issue the Link HO Complete event (e.g. after upper layer handover processing, MIP). 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_121`32cIn order to be able to perform a local handover (i.e. replacement for switch command) the destination MIHF ID would not be remote.d406g4547 2007/09/1709/16/2007 03:08:31 EDTNo9producerᆃᇃሃቃኃዃጃῃƒÃăŃƃǃȃɃ  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMN[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⡃⢃⣃⤃⥃⦃⧃⨃⻃⼃⽃⾃⿃ƒÃ  !"#$%&'()*+,789:;<=>?@ABCD㐃㑃㒃㓃 cnotWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWW!W"W#W,W7W>WAWGWRWSWUWVWYW[W^WbWcWdWfWkWlWmWnWoWqWuWwWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWW#W*W-W.W2W@WAWCWDWEWIWJWPWTWVWZW\WaWtWuW{WWWWWWWWWWWWWWWcaWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWW"W#W%W&W'W+W.W0W5W6W7W=W>W@WAWBWGWHWIWJWVW[W\W^W_W`WbWdWeWiWkWlWmWrWsWtWvWwWxWyW|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWW#W&W'W(W+W,W/W0W1W7WAWBWEWIWNW[WaWmWpW{WWWWWWW>8EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_17`53a5.3.4cThe text states that the AN is responsible for providing a secure channel for communication of MIH information. However it does not state anything about whether the MN in authorised to obtain that information.d304g5298on is to support a mechanism to provide handover candidates by location, state clearly that mechanism is supported but the algorithm for deciding what information to provide is out of scope.vAdd this to next paragraphwAgree 2007/11/2609/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_17`53a5.3.4cThe text states that the AN is responsible for providing a secure channel for communication of MIH information. However it does not state anything about whether the MN in authorised to obtain that information.d304g5298eds to be some form of ensuring that the MN is authorized to obtain the MIH information.YesLcfocused<WfollowedWwWfollowingJW_WtWWWWWWfontWfontofparametersinlistneedstobemadeconsistentVforWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW%W'W+W/W0W4W6W7W:W=WBWCWGWJWKWLWMWNWYWZW[W\W]W^W_WcWeWfWqWrWsWxWyW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWf MIH_N2N_HO_Commit. 2007/09/1709/12/2007 02:37:36 EDTYesފd114g4190 2007/09/175j802.21needstoclearlystateworkingassumptionsregarding V802.21'sWW802.37WW802.3&3gpp2W9=WhWWWaWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW"W#W%W&W'W)W+W,W2W5W6W7W8W=W@WBWGWIW^W_W`WeWhWiWkWlWmWtWwWxWyWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW&W+W,W8WEWJW|WWWWWWWWwjmovesection8.2.2toannexVmovesentenceonline49and50ieinthereceivedstatewiVmovethelinenumbersleftbyafewmmVmovethistobeasubclauseof6.2"V#Vmovement%Wmoving W5WmuchWmulti-octetWmultipleWWWmust&W5W7WWWWmutualWmutually]WnWWn/8Wn2nWWWJWjWWWWW WKWWWnaiWname4WzW{WWWWyWWWnames2WnativeWWnecessary=WWWnecessitatingW2007 03:35:02 EDTYesECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_191`39aB.2.8c,(Kenichi) BITMAP(64) should name as REVISIONd438g4515 2007/09/1709/16/2007 03:35:02 EDTYes)W*Wmimo/ofdmWminPWSWTWmincardinalityBWmindWminimalݶWminimise+WminimizesWminimumW%WݹW Tcmy@need@needs@)networknetworkinmostcasesdoesnotcareaboutthespecificsofl@Bnetworktypeandrevisionpresentationforwirelessumtsis@networks--e@nobitformihlinkactions@9noinforesponsebinarylisttlvintablec2@not@bof@Uoff@on@onmessagesmihmnhocommitrequestandmihmnhocommitin@onlyanmihfcapablenetworkentityshallrespondwiththis@optional@order@others@pages@partners@Lplaces@Ipleaseclarifytherelationshipbetweenthemihlinksapand@point@tpositive@apand@ypoint@positive@erbasis@7periodicnotificationisonaperparameterbasis@7notificationisonaperparameterbasis@7periodicnotificationisonaperparameterbasis@777|vhandovershappensW W WWWhasWWW&W'W7WEWaWuWWWWWWWWWW WhaveWWWW5WWW WhavingWWhelpsWhenceWWhessidWhighWWWhigherWAWWhoWWWWEWiWtWuWwWxWyW}WWW W WWWhom/WhorizontalWhowWWWWWWhowthetransportaddressisdeterminedisoutsidethescopeVhowever Whsdpa/Whsupa/WiWWWW<WeWWidWWWWWWWWWideaWidenticalEWidentifierWWWW1WDWEWWWWWidentifiersEWidentifyWWvWWWieWWWWWWWpWWWietypeisusedbyiereportingtemplatepV]gWWWWWWWWWgaborWWWWWWgiesbertsW W!W"W#W$Wgiesbertspieter-paulV V!V"V#V$VgolmieWWWWWWWWWgolmienadaVVVVVVVVVgregoryWWWWguptaWWWWWWWWWWWWW WguptavivekVVVVVVVVVVVVV VhWWWWWWWWVVVVVVVVVleeuwenWWlevyWWWWlevyjosephsVVVVmWWmichaelWWWWWWWnamenatarajanWWWWWWWWWnatarajankadathursVVVVVVVVVolveraWolveraulisesVcmessagesWWWWJWeWzW{WWWWWWWWWW'W(W0WgWWWW WWmessages/flowsWWmetWmetaWmetersNWmethodkWlWmWrWsWWWmethodsWOWkWlWmWnWoWmetricWmgmt WmibW'WmichaelWmicroWmiddleWmifh-idWmifh-idcanbedifferentdependingontheaccesstechnologyVmightWWW7V8V9V:VkwakW W W W W WWWWWkwakjosephaV V V V V VVVVVlach߳WߴWߵW߶W߷W߸W߹Wlachhong-yon߳VߴVߵV߶V߷V߸V߹VleeuwenqWrWlevy6W7W8W9Wlevyjosephs6V7V8V9VmqWrWmarcW W W W W WWWWWWWWWWW A(09/12/2007 02:37:36 EDTYes EEastwood, Lester FF DisapproveGProducer^ Technical_203`1c"Missing definition must be filled.d119g5483jDefine the missing definitionvHDelete NETWORK_SECURITY_IE Can be added later if definition is availablew PrincipleyRef 532 (superceded){l) none needed 2007/12/1909/12/2007 02:37:36 EDTYes EEastwood, Lester FF DisapproveGProducer^ Editorial_174c\The entire Annex B is poorly organized. The grouping is not on a clear and consistent basis.d118g5484j}Investigate how to re-organize the data type definitions, either on a per-premitive, and/or per-message, and/or per-IE basis?p'Wait till the last review of the draft.{j) in progress 2007/12/1909/12/2007 02:37:36 EDTMarkedNo ^ Technical_203`9cThe heading of this clause is missing definitions. Why was this draft put forward to Sponsor ballot if it is a known fact that there are missing definitions?d161g5441 David(jseveralWWshallWWWWW<WWWWWWWshifting=Wshort,WshouldWW%W7WXWvWwW}WWWWWWWWWWWW'W/W2WNW^WcWWWWWWWWshouldbelinkactionVshowWWWWWWWshowtherelationshipVVshowingWshowsWWsideWW}WWW!W"WWWWWsignalling WWWsignificanceWWWsignificantWWsilentlyWWmuchxWmultipleaWcWWmustߝW߬W߮WWtWmutualTWmutuallyWnEWWn/8Wn2n<WjWsWWWWW&WpWWW WWnai;Wname߫WWWWW`WW WnamesߩWnativeWWnecessaryߴWW`0 M⻃@ᐃᖃᵃу⒃ă҃5{㓃Pᓃᙃ8P`ὃ˃߃ⳃɃ!M㉃㟃pЃ݃Uᒃᾃڃ:␃4pዃ؃ރ Zw₃⢃⾃ȃT} Gu0m‚!ፃἃY➃⡃‚"ᎃᴃ‚#Nv⏃⦃ǃ ‚$P℃⇃⼃⿃=O~㯃ȃ‚%σ1⣃˃̃΃%3ㆃʃ΃ ‚&᷃݃Wڃ ‚'ᡃ*⌃̓‚(⑃╃▃㳃ۃ‚)L‚*2kbdef‚1@⎃Ⓝⶃ"㍃㢃‚2ᔃ΃zσ㒃‚3ៃ᠃>tↃ◃1̓‚4‚5ᆃኃʃZ\Ѓ҃‚6┃ⱃtゃ㝃㱃㴃㵃㶃㷃‚7̓‚T}‚Uᝃᮃṃ(A⽃‚V‚Wᨃ׃FXjfollows=WfontWforWWWWWWWWWWWWWWWW W W WWWWWWW&W'W)W+W-W2W3W6W7W8W:W=WBWGWZW`WcWeWhWvWzW{WWWWWWWWWWWWWWWWWWWWW%W&W(W*W.W2W4W7W=WnWsWtWWWWWWWWWWWWWW W Wewhatevermipshopwillp'Vforexampleinthespecificcaseof802.11statethatmihre7Vforexampletheieee802.11lowerlayersarethemacsublayeVforexampletheoccurrenceofahandoverofamobilenodefrVforexamplewirelessnetworkscouldbeenhancedforcarrying)Vformobileusershandoversmayoccurduetochangesinwirel%VformWformal'W6WW^technicalwasWDisapproveGProducer^General_42`5a6.4.1 2007/09/1709/11/2007 17:47:21 EDTYesޗENoens, Richard HF DisapproveGProducer^General_42`5a6.4.1d101g4203 2007/09/1709/11/2007 17:47:21 EDTB~cnetworktypeandrevisionpresentationforwirelessumtsis/Vnetworktypeinclusiondoesnotincludevaluesfor3gppandVnetworktypeinclusionvalidrangedatadoesnotmatchsameVnetwork--meaningWnetwork-wise WnetworksWWWWWWWWWWWWWWWWWWWWWMWdWWWnewest^WcWnextWWWuWWnihWnmsWWWWWWW W#WWWnmsisusedfornetworkmanagementandistobeastand-alonVVnoWWWWWWWWWWWW WWW/W8W\W_WaWgWrWsWWWWWWWWWWWWWWWWW#W)W8WKWLWWWXWYWbWeWfWnWoWpWsWxWWWWWWWWW9ckenichibitmap64shouldnameasrevisionXVkenichicardinalityshouldbemincardinalityTVkenichicommentintheschemaisnotcorrectSVnwWwWshouldcontainmeanstodiscovtheirUWVWthenwWwWshouldcontainthemeanstoditheirUWVWthenwWwWwWwWwWwWwWwWwWwWwWwWWthem*WthenWWW&W'W*WwWwWwWm*WthenWWWW&W'W*WwWwWW&W'W*WwWwWwWwWwWwWwWwWwWwW*WwWwWWtWWWWW&W'W*WwWwWwWwWWrWtWWWWW&W'W*WwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWWWWWWWWWWWWWWWWWWWWWWWWYVCecresponseWWWWWWWWWfWgWpWtWuWvW~WWWWWWWWWWW@WJWYWWWWedWWretransmittedmihresponseisreceivedduetoalotmihackVreverseWrevision/WXWrlc W7Wrlc/mac0W7Wrnc WroamingWWroleWWrouter WOWrouters WrscpWrsniWrspWPWrssiWruleWruledWWrunningWsfWsaWWsacnWsameWWWWWWW W W0WIWKWLWMWNWfWkWlWmWsapWWWWWWWWW6W>WAWBWcWsapsWW&WsayWWW7WsayingWscanWWRWscenarioWscenarios&WschemaWschemeWscope6W7W<W?WscratchWsdo'WsduBWWcexamplesW<WYWWWWexceptWexception]WWexceptions7WexcessiveWexchangeBWwWWWexchangedWWWexchangesWBWeWWWWexclusivelyWexecutedWexecuteswWexecutionWWexhibitWexistW0WWW#WWWWWWWWexistedWexistingWWWWWWWWWWexists.W]WexpandedWexpectedWW=W=WW=W=W=W=W=W=W=W=W=Wicient for voice or whether voice service is provided by the network--meaning end-to-end QoS is supported.ed97g4207jClarify the text. 2007/09/1709/11/2007 17:46:47 EDTYesޜEMyles, Andrew FF DisapproveGProducer^ Technical_72`59a7.3.11.1cd96g4208 2007/09/1709/11/2007 17:46:47 EDT?E Cypher, DavidF DisapproveGGeneral Interest^ Technical_52`60a6552c$Network System ID IE does not exist.d131g5471jChange to Access Network AUX IDwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s E Cypher, DavidF DisapproveGGeneral Interest^ Technical_52`60a6552c$Network System ID IE does not exist.d131g5471jChange to Access Network AUX IDwAgree{k) done 2007/11/2809/13/2007 13:56:26 EDTMarkedYesof this parameter.vby 427w Superceded 2007/11/1809/13/2007 13:56:26 EDTMarkedYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_53`12a6552c5There is no Mobility Management IE in this container.d132g5470jAdd Mobility Management IEwAgree 2007/11/1809/13/2007 13:56:26 EDTMarkedYesavidF DisapproveGGeneral Interest^ Technical_179`43c'There is no bit for Link_Action commandd155g5447jAdd bit for link action commandTCcjhandoversWeW%WhardWWhasWWW&W9WWWWWWWWhaveW&W2WwWW5Whavethetlvschematypeassignmentplusthevaluedatatype5VheaderWWWWWWhenceWWhereWW'W+W2W6W7WWhigerWhighWhigherWWWhighestWhoWWWJWgWjWtWvWwWxWyWWWWWWW W W WKW[WbWeWfWWWWWWWW-WEWWWhoweverWW]WwWhttpWhyphenWWiWWWWW&WdWeWtWwWWWWWJWWibelievetherehastobeatleastonequerythereforethesViproposetomakemiheventsubscribeandunsubscribepartoVisuggesttoreplacethe802.3&3gpp2boxesinfigure11bytV<vE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_175`49cConsistency LINK-ID or LINK_IDd152g5450jChange to LINK_IDwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes wE Cypher, DavidF DisapproveGGeneral Interest^ Technical_215`34c]Value of TYPE_IE_POA_MAC_ADDRESS is 10000302 here, while it is 10000200 in Table A-1 page 173d151g5451jConsistently use one valuewAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes xE Cypher, DavidF DisapproveGGeneral Interest^ Technical_173`41c*No Mobility Management line item or codingd150g5452jCConsistently add or remove Mobility management from entire documentpfixed inconsistencywAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYesyE Cypher, DavidF DisapproveGGeneral Interest^ Technical_214`39cTName is missing "list" to agree with page 173, Table A-1: TYPE_IE_LIST_SUPPORTED_LCPd149g5453d149g54533cumentwAgree{i) to doe;cresultWW[W\WWWWretainWretentionWretransmissionWWW WretransmissionsWWretransmittedWW WretransmittedmihresponseisreceivedduetoalotmihackVreverseWrevisedWrevision/WXWrewordedWrfWWWrfc^WcWrightWWWrigorouslyWriskWrlc W7Wrlc/mac0W7Wrnc WroamingWWWWWroleWWWrollbackWrouter WOWWWW3WWWnWWWWsaWWsacnWWsameWWWWWWW W W0WIWKWLWMWNWfWkWlWmWWWWWW$WdWtWWWsapWWWWWWWWW6W>WAWBWcWWWWWW W WWW#W$WWWWWWHjforexampleassumeanddescribeherewhatevermipshopwillp'Vforexampleinthespecificcaseof802.11statethatmihre7Vforexampletheieee802.11lowerlayersarethemacsublayeVforexampletheoccurrenceofahandoverofamobilenodefrVforexamplewirelessnetworkscouldbeenhancedforcarrying)Vformobileusershandoversmayoccurduetochangesinwirel%VformWformal'W6WW09/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_124`35a7.4.24.1.2 and othersoveGGeneral Interest^ Technical_121`41a7.4.23cLTarget PoA is already included in Target Link Identifier. This is redundant.d618g4335jRemove 2007/09/1709/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_124`35a7.4.24.1.2 and othersical_124`35a7.4.24.1.2 and othersd617g4336 2007/09/1709/16/2007 21:41:08 EDTWb-10ށW€€noƒ %()*+,-./1349:;OPQRST[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃⑃⒃Ⓝ┃╃▃◃☃♃⚃⛃✃❃➃⟃⠃⦃⧃⬃⮃ⱃⴃⵃⴃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃⵃcal_103`33a7.4.18cK(Kenichi) MIH_Scan is not needed because it is one of the MIH_Link_Actions.d444g5158General Interest^ Technical_111`48a 7.4.20.3.21p.YQ%EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_47`1a6.5.2cAWhy does this standard only provide a query mechanism prior to authentication. IEEE 802.21 should support query or broadcast mechanism prior to authentication. For example, future amendments to IEEE 802.11 may all this information to be broadcast as part of a beacon or other data frame.d313g5289jgAdd a statement to allow the possibility of MIH information to be broadcast prior to L2 authentication.wDisagree{l) none needed 2007/12/19his standard only provide a query mechanism prior to authentication. IEEE 802.21 should support query or broadcast mechanism prior to authentication. For example, future amendments to IEEE 802.11 may all this information to be broadcast as part of a beacon or other data frame.d313g5289jgAdd a statement to allow the possibility of MIH information to be broadcast prior to L2 authentication.wDisagree{l) none needed 2007/11/26RNAEOhba, YoshihiroF DisapproveGProducer^ Technical_151`31a8.4.1.1cAUIR bit usage is not clear. Which entity is supposed to set this bit? If MN is supposed to set this bit, how PoS? can trust that MN is authenticated when the bit is not set? The underlying assumption for the response limiting using this bit to work is not clear.d206g5396jZDelete the UIR bit or add more text that answers to those questions. (21-07-0373-00-0000)pxchanged text in 8.4.1.1 according to contribution 21-07-0373-01-0000 Primitives in chapter 7 need to get updated as wellvTGu needs this feature in current version of draft. Other issues with this feature could be clarified separately. Please refer to contribution: 21-07-0373-01-0000w Principle{f) pass off to other editor 2007/12/0809/13/2007 16:03:47 EDTYes AEOhba, YoshihiroF DisapproveGProducer^ Technical_151`31a8.4.1.1a8.4.1.11809/13/2007 16:03:47 EDTMarkedYes1`43a8.4.1.1c=*cthetextstatesthatalinkparametersreportindicateschanVthetextstatesthatlinkdetectedindicatesthatanewtypeVthetextstatesthattheanisresponsibleforprovidingasVthetextstatesthatthedefinitionofmihfhasnoimplicatiVthetextstatesthatthelinkdownnotificationisdeliveredVthetextstatesthatthelinkupnotificationisdeliveredwVthetextstatesthatthemihfdemandsthattheservicemanagVthetextstatesthatthereshouldbeatleastonequeryVthetextstatesthedefinitionoflinkswitchastheprocessVthetextsdescribesthisaseitheranmihusertomihuserewVehandoverstatusdonotagreVthetypeiecontainernetworkshouldcontainmeanstodiscovVthetypeiecontainernetworkshouldcontainthemeanstodiVVVtheirWWvWWWWthemrWsWWWWWWthemselvesWE9jpredefined`WpredictiveW+W,WpreferWpreferablyWWpreferenceWWpreferredkWlWmWprefixWpreparationWpreparesrWsWpresentsWpreviouslyWprimary4WprimeWprimitesWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWuWfWuWuWuWuWfWuWuWuWuWWcalculate WcallWcalled߾WcanW:WjW߇WߝWߞWߟWߢW߮W&WtWW WWcandidatelWWWWW)WXW[W]WWWWWWcandidatesTWVWcannotߝWcapabilitiesGWTWWcapabilityGWHWJWKWkW'W3WAWWWWW0W1W2W3W4W<W17:EEastwood, Lester FF DisapproveGProducer^General_316cAnnex M.6 seems redundant and not adding any value, given that similar materials have been covered in the example call flows in Annex H and Information Service examples ind121g5481j remove M.6wAgree{k) done 2007/12/1909/12/2007 02:37:36 EDTYes EEastwood, Lester FF DisapproveGProducer^General_282c-Annex J does not add value to the final spec.d120g5482jIremove Annex J "Requirements to support 802.21 by L3 and above transport"wAgree{k) done 2007/12/192007/12/07n the example call flows in Annex H and Information Service examples ind121g5481j remove M.6wAgree{k) done 2007/12/0109/12/2007 02:37:36 EDTMarkedYesEEastwood, Lester FF DisapproveGProducer^General_282c-Annex J does not add value to the final spec.d120g5482jIremove Annex J "Requirements to support 802.21 by L3 and above transport"wAgree{k) done 2007/12/01pprovedisapproveᆃᇃሃቃኃዃጃፃᎃᏃᐃᑃᒃᓃᔃᕃᖃᗃᘃᙃᚃᛃᜃᝃឃៃ᠃ᡃᢃᣃᤃ᥃ᦃᧃᨃᩃ᪃᫃ᬃᭃᮃᯃᰃ᱃ᲃ᳃ᴃᵃᶃ᷃ḃṃẃểἃὃᾃῃƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ⡃⢃⣃⤃⥃⦃⧃⨃⩃⪃⫃⬃⭃⮃⯃Ⰳⱃⲃⳃⴃⵃⶃⷃ⸃⹃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃ7CcspecifiesWWWW]WWWWWAWWspecifyWWW?WfWWW(WWspecifyingWGW[W]WWWWspelled:WWspeperateWsplit WsponsorWmWsquareNWssidWssidsWWWstaWWWWWWWstackWW7WWWWW W#WWWWstacksWWWWWW W!W"W$WWWWWWstageWstandRWstand-aloneWWWstandardWWWWWWW?WWWWWWWWWWWWWWW/WEWWWWWWWWWWWstandardizeWVstatesthatitmayindicatethatthemnmayhavestartedahVstatesthatitpreparesresourceforhandoverthisisjustarVsVstaticWstating?W1+eastwoodlesterfVVVVVVVVVVVVeldadWemmelmannWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWemmelmannmarcVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV57cReference to wrong messaged388g4565j)Change N2N_HO_Complete to MN_HO_Complete. 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_131`6408:31 EDTNoERajkumar, AjayF GProducer^ Technical_131`57cReference to wrong messaged388g4565j)Change N2N_HO_Complete to MN_HO_Complete. 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_131`64OchaplinclintfVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVchengWWWWW W!W"W#W$WOWPWQWRWSWTWUWVWWWXWYWZW-W.W/W0W1W2W3W4W5W6WchenghongVVVVV V!V"V#V$VchengyuuhengOVPVQVRVSVTVUVVVWVXVYVZV-V.V/V0V1V2V3V4V5V6VchinWchinkevinaVWfWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWfamolariWWWWWWfamolaridavidVVVVVVWdÃdÃeÃe Ãe0Ãe@ÃePÃe`ÃepÃeÃeÃeÃfÃf Ãf0Ãf@ÃfPÃf`ÃfpÃfÃfÃfÃgÃg Ãg0Ãg@ÃgPÃg`ÃgpÃgÃgÃgÃhÃh Ãh0Ãh@ÃhPÃh`ÃhpÃhÃhÃhÃiÃi Ãi0Ãi@ÃiPÃi`ÃipÃiÃiÃiÃjÃj Ãj0Ãj@ÃjPÃj`ÃjpÃjÃjÃjÃqÃq Ãq0Ãq@ÃqPÃq`ÃqpÃqÃqÃqÃrÃr Ãr0Ãr@ÃrPÃr`ÃrpÃrÃrÃsÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0Ãt@ÃtPÃt`ÃtpÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃuÃuÃvu ctheqWtWuWzW|WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWW other data frame.d313g4640jgAdd a statement to allow the possibility of MIH information to be broadcast prior to L2 authentication. 2007/09/1709/14/2007 23:15:41 EDTYesMEMontemurro, MichaelF DisapproveGGeneral Interestd312g4641 2007/09/1709/14/2007 23:15:41 EDTwclink-detectWWlink-downWlink-handover-compleWlink-idvWlink-layerWlink-upWWlinkactionslistWlinkeWlinkedWlinkmacsfWlinksWWWW W WWWlinktypeWlipWlistWWWWWWWWWWWWWW WW'WFWGWOWPWQW]W^WkWlWmWWWBWCWDWJWtWyWWWWWWlistofsupportedcommandsonmihfVlistofsupportedeventsonmihfVlistofsupportedmiisquerytypesVlistofsupportedtransporttypesVlistedWWnWoWWWWWWlistingWlistskWlWmWllcW7WWWlldpWlmesWloWlocalWWWW]WwWxWyW~WWWWWW WW#W$WWWWWW&W5We cA"MIHF transaction: A combination of an MIHF Request or Indication message and the corresponding MIHF Response message (if applicable) that are exchanged between two MIHF peers. It is required to match each request message that is sent by the initiator with its response message. Acknowledgement messages associated with this message exchange are also part of the transaction." - This is describing any exchange. Definition should include the function and result of this MIHF Transaction.d268g5334j9Re-write definition to describe the function and results.vAChange as follows: "MIH Transaction: A combination of an MIH Request or Indication message and the corresponding MIH Response message (if applicable) that are exchanged between two MIH peers. It is required to match each MIH request message that is sent by the initiator with the corresponding MIH response message. Acknowledgement messages associated with MIH message exchange are also part of the transaction.") {done=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPWQWRWSWTWUWVWWWXWYWZW[W\W]W^W_W`WaWbWcWdWeWfWgWhWiWjWkWlWnWoWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WeW*W3W9WWWWWWWWWWeeditordisagreesV*V3V9VvjDe-emphasize MIHF Discovery as separate MIH service management function. Remove 6.2.3 and possibly merge the discussion into general MIH protocol discussion in subclause 8.w Superceded{l) none needed 2007/12/1909/12/2007 02:37:36 EDTNoEEastwood, Lester FF DisapproveGProducer^ Technical_63cA\MIH_NMS_SAP defines the interface between an MIHF implementation and a local Network Management System stack. Depending on the nature of the device, this local NMS stack may vary or may not even exist. Standardizing this interface brings no benefit to the implementation. In the contrary, it would impose needless constraints to the implementation.\d106g5496j3remove all definition and mentioning of MIH_NMS_SAPv%This would apply to the entire draft.wAgree{k) done 2007/12/1909/12/2007 02:37:36 EDTYes EEastwood, Lester FF DisapproveGProducer^ Technical_31cl_31cwith a period (.).d44g5558jDelete leading periodd48,cseWseamlessWsec WsecondW/WWWWsectionWWWWWWW W*W.W7WqWWWWWWW0W6WWWWWsection1.3statesthathopoliciesarenotwithinthescopeVsectionsWWWWsecureWWWsecuredWWsecurityW7WWWWWWW)WWseeWW&WFWeWgWqWWWWWWseemycommentsabout7.3.6thesameapplieshereVseeingWseemWWWW W6WseemsWWWW=WjWpWWW W'W(WWWWsenderIWsendingWWWsense7WsentKWLWMWNWWWWWWsentenceWW(W)WWWWWWWWsentencesWWseparateWwWsequenceW^Wserv>WAWlq cAThe equation presented for ATDmpdu is not correct. Dividing the ATDmsdu by the number of MPDUs in the MSDU will not yield an average MPDU transmit delay. The average MPDU transmit delay is the sum of the transmit delays of each MPDU divided by the number of MPDUs. The shortest MPDU transmit delay is the first MPDU of the MSDU The longest MPDU transmit delay is the last MPDU of the MSDU. The average MPDU transmit delay is approximately equal to the transmit delay of the middle MPDU.d637g4965j Fix this basic misunderstanding.v&Add summation to delay formula line 38w Principle{k) done 2007/12/1909/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_289`7aKc`7aKcVmarkedmWnW*W-WWWWWmaskedߴWmatchWLWMWWWmaterial7W9WWWmaxWmaximum Wmaximumdataratein802.11termsisthehighestavailableb V2WcbatteryWbatterylevelisapercentageandshouldusethepercentageVeful set of tools to make MIH work; however it provides very few requirements on how these tools should be used. This will allow for flexible use of this standard; however I believe it allows for too much flexibility and needs to provide standardized methods for the use of these tools.9d589g4364jProvide required MIH procedures instead of just examples of MIH. This is not intended to limit the flexibility of the tools, just to allow the definition of agreed basic procedures. 2007/09/1709/16/2007 17:58:08 EDTNo9lieve it allows for too much flexibility and needs to provide standardized methods for the use of these tools.9d589g4364jProvide required MIH procedures instead of just examples of MIH. This is not intended to limit the flexibility of the tools, just to allow the definition of agreed basic procedures. 2007/09/1709/16/2007 17:58:08 EDTNo9g4365OcteamWtearvWtechnicalW&W'Wtechnically7W@WtechnolgyWtechnologieWtechnologiesWW W WWW&W'W1W6W7WWWWWWWWtechnologyWW5WWWWWWWWWWWWFÃhpEÃhDÃhCÃhBÃiAÃi @Ãi0?Ãi@>ÃiP=Ãi`<Ãip;Ãi:Ãi9Ãi8Ãj7Ãj 6Ãj05Ãj@4ÃjP3Ãj`2Ãjp1Ãj0Ãj/Ãj.Ãq-Ãq ,Ãq0+Ãq@*ÃqP)Ãq`(Ãqp'Ãq&Ãq%Ãq$Ãr#Ãr "Ãr0!Ãr@ ÃrPÃr`ÃrpÃrÃrÃrÃsÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0 Ãt@ ÃtP Ãt` Ãtp ÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃucencodedWWWWWencodingW=W6Wencoding/decodingWWencoding/decodingisnotclearforparametersVencoding/decodingisnotclearforsysteminformationVencompass'Wencryption7Wencryption/integrity7WendW WWWWWWWend-to-endWendianness WendingWendpointWenforceWenglishWWenhanceWenhancementWenormous=WenoughWWenterWWentireWWWWentirelyWentitiesWWWWWWBWWWentityWWWWWW WWW@WWWWentrieskWlWmWWWWWWWWWWW\WbWfWevent-subscriptionWeventsWWWWW*W?Wevery WWexampleWWW W WWW%W/W0WYWZW]WWA2IjrespectiveWrespondWWWWrespondsWresponseWWWWWW]WgWjWtWvWWWWWWWWCWDWWWWresponse/confirmWresponsesWresponsibility]WresponsibleWrest5Wrestrict'Wchnologies. Yet, there is not even one normative reference. Is the MIH really built from scratch that does not rely on any prior defined technolgy?d497g4456 to "node", and "remote stack" to "remote node" 2007/09/1709/16/2007 08:19:02 EDTYesߔE Cheng, HongF DisapproveGProducer^General_5`1a2cMIH is about handover between different access technologies. Yet, there is not even one normative reference. Is the MIH really built from scratch that does not rely on any prior defined technolgy?d497g4456 prior defined technolgy?d497g4456 2007/09/1709/16/2007 08:19:02 EDTYes-HcmihfknowsonlyasourcemihfidanddestinationmihfidtheV_72`1a7.3.10cA.This seems to assume a nonexistent packet identifier common at both higher layers and link layers. TCP/IP layer uses its own sequence numbers which are not visible to MAC layers while MAC layer uses its own sequence numbers for link acknowledgements. What packet identifier is supposed to be used here?.d610g4343007/09/1709/16/2007 21:41:08 EDTYes#ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_72`1a7.3.10cA.This seems to assume a nonexistent packet identifier common at both higher layers and link layers. TCP/IP layer uses its own sequence numbers which are not visible to MAC layers while MAC layer uses its own sequence numbers for link acknowledgements. What packet identifier is supposed to be used here?.d610g4343ts. What packet identifier is supposed to be used here?.d610g4343 2007/09/1709/16/2007 21:41:08 EDTYesTmjdocumentsWEWdoesW4W7WwWWWdoesn't&W]WwWWdoing(Wdone)WWdownWW2WaWWWdowngrade&WdraftW W'WWWWWWWMWdrawinggWdrivenwWdstwWdueW%WduplicateW WduringbWWWerntain the means to discover the frequency bands supported by the network (e.g., 2.4-GHz, 3.7-GHz, 2.5-GHz, 5.2-GHz, etc.)d82g4222jAdd this capability. 2007/09/1709/11/2007 17:46:47 EDTYesޫEMyles, Andrew FF DisapproveGProducer6.5.5.2cThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the frequency bands supported by the network (e.g., 2.4-GHz, 3.7-GHz, 2.5-GHz, 5.2-GHz, etc.)d82g4222jAdd this capability. 2007/09/1709/11/2007 17:46:47 EDTYesޫEMyles, Andrew FF DisapproveGProducer2007/09/1709/11/2007 17:46:47 EDTYesޫEMyles, Andrew FF DisapproveGProducer46:47 EDTjifformerthenchangeqostocosandthesameonline27qViffragmentation/reasseisneededforproperoperationofmiVifmihnetsapisusedforl3onlythenthereisnoneedforVifpossiblecorrectVifthatistrueeitherremovepredictiveeventsfromthedraViftheintentionistosupportamechanismtoprovidehandovVifthisannexisgoingtocontainh7.2onpmipv6thenitsh^VcVtemurro, MichaelF DisapproveGGeneral Interest^ Technical_50`57a6.5.4 included in an annex, which is generally intended for additional information.d315g4638jKIf annex B is normative, make it a clause in the body of the specification. 2007/09/1709/14/2007 23:15:41 EDTYesKEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_50`57a6.5.4d314g4639 2007/09/1709/14/2007 23:15:41 EDT 0#cto/fromWtogether%Weendoflayer3handover޻Ver޻V޻Vthere'sanextraperiodatthebeginningoftherearetwoki޺V޺V'sanextraperiodatthebeginningoftherearetwoki޺V޺V޺V'sanextraperiodatthebeginningoftherearetwoki޺V޺V޺V'sanextraperiodatthebeginningoftherearetwoki޺V޺V7cconsistencyposposposposetc]Vconsistencyproblembit1thereisnomihconfigurelinkoVconsistencythemihgetlinkparametersresponsemessageconJVconsistencythemihn2nhoqueryresourcesrequestandthemIVconsistencythereisnomihconfigurelinkLVconsistencythereisnomihn2nhocandidatequeryKVconsistencythroughoutthedocumentastowhetheritismihzVconsistencywithparagraph/bulletconventionhVconsistencywiththeanbeforemih|VconsistentWWWWWconsistentlyWconstantlyWconstrainWconstraintsWWWW W#W$WWWWWconstructedWconsumeWconsumedMWcontact WcontainWWW.W^WWWIWWWWWWWWWcontainedWIWuWcontainerWWWWWWWWWWWWW<WJWWcontectWycactualW&W1W^WWWWWWactuallyW0W1WeWwWW&WWadWWadaptationWadaptionWWaddWWWWWWWWWWaddabreviationVaddedW.WFWWMWWaddingWWWaddition7W[W WadditionalYWWWWWadditionallyFWJWadditionallythefollowingisapplicabletotheabove4commJVaddressWWWWWWW4W7WOWgWnWoWpWuWWWRWSWwWWWWWaddressesWWW WkWlWmWnWoWWWÃQÃQ ÃQ0ÃQ@ÃQPÃQ`ÃQpÃQÃQÃQÃRÃR ÃR0ÃR@ÃRPÃR`ÃRpÃRÃRÃRÃSÃS ÃS0ÃS@ÃSPÃS`ÃSpÃSÃS+DEColban, Erik AF DisapproveGUser^ Editorial_30`43a5.6.2cAI"For communication between two remote MIHFs, the propagation from the local MIHF to the remote MIHF relies on MIH protocol messages." The sentence starts by introducing two remote MIHFs but continues by addressing one local and one remote MIHFs. Moreover, the communication is two-way, not only from the local to the remote MIHF.Id542g5060cifications." Also, add references to the particular specifications.PwAgree 2007/11/1809/16/2007 15:32:58 EDTMarkedNoEColban, Erik AF DisapproveGUser^ Editorial_30`43a5.6.2cAI"For communication between two remote MIHFs, the propagation from the local MIHF to the remote MIHF relies on MIH protocol messages." The sentence starts by introducing two remote MIHFs but continues by addressing one local and one remote MIHFs. Moreover, the communication is two-way, not only from the local to the remote MIHF.Id542g5060knatarajanWWWWWWWWWnatarajankadathursVVVVVVVVVngWngchan-wahVVVssages and how they identify a given handover. For N2N_HO_Commit we identified the handover by MN MIHF ID while here we are using source and target link identifiersd452g4501jEDTYesE Feder, PeretzF DisapproveGProducer^ Technical_132`47cAAdditionally, the following is applicable to the above 4 comments. There is some inconsistency between N2N_HO messages and how they identify a given handover. For N2N_HO_Commit we identified the handover by MN MIHF ID while here we are using source and target link identifiersd452g4501j 2007/09/1709/16/2007 03:38:14 EDTYes oYcgsm/egprs W6WguidanceW&WguidedWguildW{Wguildisanounnotaverbsowhatistoguild{Vh%WWWWhan-dovers Whand4WhandingWWhandledcWWhandlescWhandlingWhandoffWhandoff/handover/roaWhandoverWWWWWWWWWWWWWJW]W_WeWgWrWsWuWvWwWxWyWzW{WWWWWWWW8WdWWWWWWWWWWWWthoweverth_VhandoverdecisionmakingdoesnotalwaysrequirebothmobileVhandoverackYWhandoversWWWWWWWqWWWWWWWhappenWWWhappens]WeWhasWWWWW WWbWuWWWWWWWW6WJWNWWWWWWWWS 8cthat[W\W]W^WbWcWeWfWiWnWoWrWsWtWvWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW/W0W@WmWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW(WWWhongWWWWW W!W"W#W$Whong-yon<W=W>W?W@WAWBWjeeWWWWW%WjeejunghoonVVVVV%VjeffreeWWWWWWWWWWjeffreeanthonyaVVVVVVVVjeffreetonyVVjetteW W W W W WWjettealanV V V V V VVjohnWjosephWWWWWWWWWWWWWWjuanWWWWjulkaWWWWWWWWWWWWWWWWWWWWBWlachhong-yon<V=V>V?V@VAVBVleeuwenWWlevyWWWWlevyjosephsVVVVmWWmarcWWWWWWWWWWWWWWWW2ERudolf, MarianF DisapproveGProducer^ Technical_181`19c;LINK_PARAM_UMTS is sort of wrong and needs to be corrected.d476g5126jAdd CPICH_Ec/I0 and CPICH_RSCP which are the 2 most important measurements for the MN. Before writing down a long list here, please have a look into 25.215 and use the measurement names used there&pUpdated the elements (instead of bit maps, it's enumerated) No updates in section 4. But idenify the references required. No updates in Table B13.v81`19c;LINK_PARAM_UMTS is sort of wrong and needs to be corrected.d476g5126jAdd CPICH_Ec/I0 and CPICH_RSCP which are the 2 most important measurements for the MN. Before writing down a long list here, please have a look into 25.215 and use the measurement names used there&pUpdated the elements (instead of bit maps, it's enumerated) No updates in section 4. But idenify the references required. No updates in Table B13.vonnections to allow L3 data connectivity (e.g. IP connectivity) wDisagree!cprioritizedWpriorityWprobably Wprobe(WproblemWW[WwWoWpWWprocedureWWproceduresWWWWproceedrWsWprocess.WpWvWWprocesses?WWprocessingW?Wproduce[WproducedBWWproducesWpromoteWpropagationWproperWWWWproperlyWproperties Wproposed,WWWWproprietaryWprotection7WprotocoelWprotocolWWWWWW+WBWWWWWWWWWWWWW'W(W0WWWWWWWWWWWWW W WWWW5WFWGW^WkWlWmWqosisacriticalaspectofmihbutthereareveryfewnormaVVqoslistisnotalinkparametertypesinglevalueshavebeeGVqualifiersWqualifies7Wqualify7WWWcneedsWWWWW2W7WWW%WOWQWiWjWkWWWnegativeWnegotiateAWnegtwork"Wnegtworkcommunicationisnotamihfserviceaccordingtoth"VneitherZW\WnesWnetWWWWWWWWcWeWgWqWtWuWWWWWW W W W$W[WWWWWWWWWnetsapisnotonlyusedforl3ithandlesbothl2andl3jucVnetworkWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W/WgWqW}WWWWWWWWWWWWW WW#WRWWWWWWWWWWWWWWWWWWWWWWWWWWWctheequationpresentedforatdmpduisnotcorrectdividingtVtheexampleforistlvqueryorbinary-encodingqueryisnotYVthefigurecaptionindicatesthatfigure1showstheplacemeVthefiguredescriptiondoesnotlineupwiththeoctectheadVthefirstlinereferencesthemnmihfwhichisincorrectasVthefirstsentenceoftheparagraphstatesthatgeographiciVthefirstsentencestatesthatitinvokesmihn2nhoqueryrVtheframeworkpresentsthemedia-independenthandovermihreVtheheadingofthisclauseismissingdefinitionswhywasthmVtheieee802.11poaislikelyanessnotanapVtheieee802.21informationreducesthescanningrequiredtoVnethoqueryrequestprimitiveisinvokedbyanmihVthemihxxxrequestshouldneverybeusedbythemihfitis VthemissingdefinitionmustbefilledVthemobilenodeiscapableofsupportingmultiplelink-layerVthingW;cbe@I{besides@fbetweenrbeyond@broadcasts@by@bytes@Gcapabilities@cases@>choices@collapse@com/morris/glossary@commands@communications@compliant@conformant@tconnection@Kconsistencyaddressoraddress@consistencyposposposposetc@ containing@7contents@corrected@currentlinkidentifie@]data@decisions@jdefinelinksynchronouseventsratherthansayingwhatthey@definitionfornetworksecurityismissing@deleteannexjasitisredundantandnotrequiredinthesp@design@Ideveloping@device@hg@device@Yvice@YLdeveloping@device@Ye@YPcseemstobeanextraneouslinejVseldomWselectWselectedWselectionWWWWWWWselectorWself-contained7Wself-filfullingWself-referentialWself-writtenWsendWvWWWWWsenderIWsendingWWWWsense7WWsentKWLWMWNWWWWWWUW_W`WWWWsentenceWW(W)WWWWWWWW<WWWWWWWsentencedefinesservicecontinuitybutthedefinitionisnoVsentenceisambiguousVsentenceismissingpunctuationVsentencestartswithaperiodVsentencesWWseparateWwWWseparationWsequenceW^Wserv>WAWn of handover (definition 3.3) is based on this definition of link switch.d75g4229 2007/09/1709/11/2007 17:46:47 EDTYes>Djpleaseaddthefollowingsectionash10VpleaseclarifyandremoveoraddipsubnetprefixinformatioVpleaseconsideraddingnewentriestothemihfisbasedontVpleasedefinesomewheretheactionsthatanmihprotocolentVpleasemarkeachprimitiveasmandatoryoroptionalorspeciVpleasesee309VVpleaseseethecontribution305Vpleaseseethecontribution306change1Vpleaseseethecontribution306change2Vpleaseseethecontribution307Vpleaseseethecontribution308VVpleasespecifytherelationshipbetweenthemihlinksapandVpleasestateclearlyifmihsignallingexchangesusingdataVplugfestWpoaWWbWkWlWmW|WWWWWpoasbWpoorWportionsWposWWWpositiveWpossibilityW]WfWWpossibleWWBWWWWpossibly.WWW9109/16/2007 01:46:33 EDTYes Yes sO1jlink-layerW7WacceptableuWuWuWuWaccordingWgWWWachieveWchieveWWack-rspiWiWiWiWiWiWiWiWiWiWiW`WiWiWiWiWiWWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiWiW-rsp`WiWiW`WiWiWiWiWiWiWiWiWWackNW`WdWgWiWack-rsp`WiWiWiWiW. If the caption is clarified, then a figure should be added which shows the mobility management architecture that 802.21 specification is based upon. 2007/09/1709/11/2007 17:46:47 EDTYes޳EMyles, Andrew FF DisapproveGProducer^ TechnicalaGeneral. 2007/09/1709/11/2007 17:46:47 EDTYes޳EMyles, Andrew FF DisapproveGProducer^ TechnicalaGenerald73g4231 2007/09/1709/11/2007 17:46:47 EDTEOlvera, UlisesF DisapproveGProducer^General_292`1aAnnex LcAj1) These recommendation should be normative for 802.21, although the actual realization of the recommendation is upto the Technical Standards Organization that implements it. 2) Furthermore, references to specific requirements and suggested amendments are stil not defined. The reference iteself shows "xxxx" that denote that these docuements are not available. jd646g4956j1) Simple write "(Normative)" at the begining of the section. 2) Either generate the reference and write the appropriate number or do not reference documents that have not been written.wAgree{k) donestil not defined. The reference iteself shows "xxxx" that denote that these docuements are not available. jd646g4956j1) Simple write "(Normative)" at the begining of the section. 2) Either generate the reference and write the appropriate number or do not reference documents that have not been written.wAgree{k) done/30XEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_133`8a7.4.271ceThe section is titled "Binary Information Query". However I believe it defines Info Query Binary Datad327g5275jsClearly define the InfoQueryBinaryData IE or if it exists add a refernce to it in clause 7 and 8, where it is used.vAdd a referencewAgree 2007/12/0709/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_133`8a7.4.27^ Technical_195`12aB2.9.1ceThe section is titled "Binary Information Query". However I believe it defines Info Query Binary Datad327g5275jsClearly define the InfoQueryBinaryData IE or if it exists add a refernce to it in clause 7 and 8, where it is used.vAdd a referencewAgree 2007/12/0709/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_133`8a7.4.27:31:14 EDTYes 2007/09/1709/16/2007 21:41:08 EDTcawkwardWb WW3W4W5WWW/WNWWWb-10Wb-13WWb-15Wb-2Wb-8Wb-9Wb13WbackW WvWWbadWbadandpoorsignalstrengtharethesameinmymindVballotWmWbandsWbar!WbarsWbasedWWWWbasis[W`WkWlWmWWers to ammendments needed in the various media to support MIH, yet when I looked into the referenced Cdocument for 802.11 (21-05-0359r2) no such standard definitions in 802.11 terms existed. Without the detailed native definitions for the common terms, no functions can operate in a standard way. It is not clear to me how we may finalize a standard which is so incomplete. Perhaps the work should continue? In its current state the 802.21 document provides a coherent transport mechanism for various yet-to-be-defined IEs which are meant to translate into common MIH terms for use in common MIH )*EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_7`15a3.18c"Note for a network entity comprising of multiple interfaces, the notion of MIH PoS is associated with the network entity itself and not with just one of its interfaces."d548g5054j"Note that for a network entity comprising of multiple interfaces, the notion of MIH PoS is associated with the network entity itself and not with just one of its interfaces."{k) done 2007/12/1909/16/2007 15:56:25 EDTYessetwork entity itself and not with just one of its interfaces."{k) done 2007/11/1809/16/2007 15:56:25 EDTMarkedYes FF DisapproveGGeneral Interest^ Editorial_6`64a3.15c"As an example, the IEEE 802.11 Lower Layers are the MAC Sublayer and the PHY and the 3GPP Lower Layers are the MAC and UMTS layers."d547g5055j"For example, the IEEE 802.11 Lower Layers are the MAC Sublayer and the PHY, while the 3GPP Lower Layers are the MAC and UMTS layers."8acwhydoesthisstandardonlyprovideaquerymechanismpriorVwhyisitnecessarythatthiscontainershouldhaveatleastVwhyistherenonormativereference8Vwhyisthisannexonlyinformativedoesn'tthestandardprovVwhythereisaseparatemacaddressfieldinmihmnhocommiVwhythisrequestcontainsmoreinformationaboutresourceregVwhywouldthelinklayersmacmakehandoverdecisionsevenfVVwillWWWWWWWWWWWW&WkWlWmWWWWWWWW WWW$W/WWWWWWWWWWwillthedifferentcosidberepresentedconsistentlyacrossVwimaxWW_W`WwiredWWWwirelessW W/WWW%WW(,EEmmelmann, MarcF DisapproveGAcademic^ Editorial_40`41a6.3.5cWould be nice to have the MIH events in Table 4 ordered according / sorted by their type. Order of types should be according to items / paragraphs 1) through 5) of this section 6.3.4.1d48g5554jreorder table entirespdid both tables 3 & 4{k) done 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Editorial_39`50a6.3.4.1cWould be nice to have the link events in Table 3 ordered according / sorted by their type. Order of types should be according to items / paragraphs 1) through 5) of this sectiond47g5555jreorder table entires{k) done 2007/12/1909/10/2007 07:08:58 EDTNoooMarkedNolde be media-independent. 802.21 should define "generic" link-commands as it does e.g. in table 7. The adaption of such genric commands to the actual technology shoEEmmelmann, MarcF DisapproveGAcademic^ Technical`cspecificallyWW5WWWspecificationWWWWW&W'WWWWWWWAWWWcified in the request)?d458g4495jEither change "Current Link Identifier to "Source Link Identifier" or to "Target Link Identifier". Alternatively, remove "Current Link Identifier" and add both source and target link identifiers. 2007/09/17WnterfacesWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWޚWޡWްW޳WWinterfacesWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWmixedWinternal3WWinternetWW` cspecificsWWWWspecifiedWWWWWDWEWbWtWWWWWWWWWW0WWWWWWWWWWWWstandardWWWWWstandardizedWWWstandardizingWWstandardsWWstartingWstartsWstateWWWWWWstatisticalWstatisticsWstatusW W WWstilWsublayerWsubmittedWsubnetWsubscribeWWWsubscribedWsubscriberWsubscriptionWWWsubtractingWsuccessfulWsuccessfully WsuchWWWW W WsuffersWsufficientWsuggestedWsuiteWsumWsupportWWWWsupportedWWWWWsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliWykcMIHF knows only a source MIHF ID and destination MIHF ID. Then how MIHF ID(s) can be changed into source/destination transport address? MIHF knows transport address? It is an MN's local interaction but I think at least 802.21 should mention this in draft.d335g5267j/Clarify mapping transport address with MIHF ID.v The MIHF does know the transport address. How the transport address is determined is outside the scope of this draft. The network MIHF entity may have FQDN as it's identifier The MN may not have a FQDN.w Principle{l) none needed 2007/12/1909/15/2007 00:01:16 EDTYes s + cjustwhenisalinkhandoverconsideredcompleteseepage98eVkW.W5W7WWk-1Wk-2Wkeep%WWWkeepthemainpartofthestandardtechnologyindependentanVkenichiOWPWQWRWSWTWUWVWWWXWkWeWkWkWkWkWkWkWeWkWkWkWkWkWkWkWkW WeWkWkWkWkWkWkWkWkWkWkWkWkWkWkWkWeWkWkWkWkWkWkWkWkW WeWkWkWkWkWkWkWWkWkWkWkWkWkWkWkWWeWkWkWkWkWkWkWkWkWkWkWkWkWeWkWkWkWkWkWkWW WeWkWkWkWkWkWBWXWyWWWTWrequirementwWrequirementsW7W8W9WߕWߝWߥWWwWrequiresWrequried?WreservationjW&WWW WW7jcontainingWcontainsvWW=WWcontentW0WWcontentsSWWWcontextW0Wcontexts WWcontinutity&WcontributionWWWWWWYWWW2W6Wevel indication for the MIH entity to check or have reported back if the underlying link has been authenticated or associated such that at least implicitly "authentication" can be deduced from the link status for wireless links. Then, in the specific case of L2 MIH over Ethernet, is any PoA trying to contact another oneB= in the same broadcast domain by definition "authenticated" ?+d516g4437jin the specific case of L2 MIH over Ethernet, is any PoA trying to contact another oneB= in the same broadcast domain by definition "authenticated" ?+d516g4437j 2007/09/1709/16/2007 13:36:45 EDTYesHjmentionWmentioningWWWWWWWWWmergeWWdWWmergethetexttosubclause5.1.1orremovethesubclauseVmergethetwoblocksintoonedVmeridianWmessageWWWxWyW~WWWWWWWWWWWWWWWCWDWIWWWWWmessagesWW'W(W)WWWW'W Wmet WmethodgWWRWSWlWzWWWmethodskWlWmWWmichaelWtext and title in 6.2.3 and 8.2.3.5 may mislead readers otherwise.d343g4610cedures for MIHF discovery are not specified in this spec (i.e., no mandatory messages/flows defined for MIHF discovery). This is the right way to do it. Just the text and title in 6.2.3 and 8.2.3.5 may mislead readers otherwise.d343g4610islead readers otherwise.d343g4610 2007/09/1709/15/2007 22:08:13 EDTNo007 07:08:58 EDTVtmeylemansmarcVVVVVVVVVVVVVVVVmedia access independent mechanisms to facilitate handovers between and among IEEE 802 systems as well as certain external systems. This document only partially addresses that stated purpose. For example, the informative Annex L specifically identifies the need for certain amendments to several IEEE 802 technologies. These recommended amendments are identified by contribution numbers and, as such, may not be readily available tBo the Standards user, nor is there any indication that these proposed amendments have actually been adopted by the specific technology, therefore calling into question both the viability of and the ability to implement the proposed 802.21 standard.d62g4242j 2007/09/17 cthetextincludelocalmihfhowevertheregistrationisbetwVthetextstatesatransitionfromsendingtoinitaftertwoVthetextstatesbeforeastationhasassociatedandauthentiVthetextstatesthattheanisresponsibleforprovidingasVthetextstatesthatthelinkdownnotificationisdeliveredVthetextstatesthatthelinkupnotificationisdeliveredwVthetextstatesthatthereshouldbeatleastonequeryVthetextsdescribesthisaseitheranmihusertomihuserewVthetitleisnotdescriptive-Vthetitleisnotdescriptivemoreoversomedescriptionshoul.VthetypeanddescriptionforthehandoverstatusdonotagreVthetypeiecontainernetworkshouldcontainmeanstodiscovVthetypeiecontainernetworkshouldcontainthemeanstodiVVVtheirWWvWWthemrWsWWWWWWthemselvesWFccasesWWW=WgWWMWWWcategoriesWcategoryWWWcauseWcausedWcausesWccaWcellidWcellsWcellular'W6W7WWcenterNWcertainWW WWWWWWchairWWchalkWchangeWWW!W(WWW%WNWchangesentence(VchangedW^WcWWchangesWWWWWchangingWWWchannelWW1WWWchannelidwithrespecttowhatisitdefinedisthisanabr1VchannelutilizationhasnothingtodowithmaximumlinkdataVchaptersWcharacterWcharacteristicWcharacterizeWcharacterizedWchargeiWcheck WcheeseWchoiceWÃ#Ã# Ã#0Ã#@Ã#P Ã#`Ã#ߺÃ#߼ jjI suggest to replace the 802.3&3GPP2 boxes in Figure 11 by these SAPs. Consider to move text describing mapping of LINK_SAP to access-specific SAPs from Section 7.1 page 59 here.p/modified fig 11 to be more consistent with text{k) done 2007/12/1909/16/2007 12:18:13 EDTNoEFamolari, DavidFApproveGGeneral Interest^ Technical_90`24c[7.4.5.2.2] the parameter "Response Link Event List" in MIH_Event_Unsubscribe.confirm does not include status information as specified in the description.d505g5097jChange the description of "Response Link Event List" from: "List of MIH events along with their unsubscription status." To: "List of successfully unsubscribed link events."wAgree{k) done 2007/12/1909/16/2007 10:24:17 EDTNo EFamolari, DavidFApproveGGeneral Interest^ Technical_198`38cfTable B-15 -Data type for RDF information query: Wrong default value has been specified for MIME_TYPE.d504g509804g509804g5098V cthisWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWEEastwood, Lester FF DisapproveGProducer^ Technical_150`60a8.4.1cPMIH Protocol header is of fixed length, as indicated in fig 27 on the next page.d117g5485jKcorrect figure 26 to show MIH Protocol Header has fixed length of 8 octets.psuperceeded by comment #454wAgree{k) done 2007/12/1909/12/2007 02:37:36 EDTYes EEastwood, Lester FF DisapproveGProducer^General_144a8.2.2cAMIH protocol transaction state diagrams only have some significance when the MIH level ACK mechanism is used. Otherwise, MIH protocol is mostly a transaction-oriented protocol. Since MIH level ACK is optional to use, it may be better to move the state diagram discussion to an annex.d116g5486ACK mechanism is used. Otherwise, MIH protocol is mostly a transaction-oriented protocol. Since MIH level ACK is optional to use, it may be better to move the state diagram discussion to an annex.d116g5486116g5486116g5486346g4607 2007/09/17EDT&cnetworkinmostcasesdoesnotcareaboutthespecificsoflVnetworkmanagementisnotamihfserviceaccordingtothede#VnetworkmanagementsystemshouldbecapitalizedtomatchtheVnetworksecuritydefinitionmissingVnetworksystemidiedoesnotexistVnetworktypVXE[c]j_j`jA/gccAdfFXhEijAqlcA dojqcrjtcAdujwGycAd>|G~jccKdcAdcBdccBdcAdOjE|~EcAldtabE^GNQcAIdEccFd<jE,.d$jFcAd>jG"jhoghooghiWhomeWhow WWWW-WEWWWhoweverWW]WwWhttpWhyphenWWiWWWWW&WdWeWtWwWWWWWJWWWWWWibelievetherehastobeatleastonequerythereforethesViproposetomakemiheventsubscribeandunsubscribepartoVirecommendaconventionssubclausebeforeb1.1thatdefineVisuggesttoreplacethe802.3&3gpp2boxesinfigure11bytV both IS and ES (but CS is optional), it must support the following list of media-specific SAPs XYZ and the following list of local and remote primitives XYZ. Another example, a MN that has both 802.11 and EGPRS, must support L3 IP trasnport option (but doesn't need L2), must support the following SAPs and the following list of primitives. Or, define above minimum MIH protocol sets per access technology if supported in the MN. Like, any MN that has an 80jintent@introduce@qinvestigate@investigatehowtore-organizethedatatypedefinitionseit@_ip@Xisn't@issues@itisnotclearwhattheintentwasforthischangeperhaps@/layer@limit@linkOlink-layer@/links@1listofsupportedmiisquerytypesonthelocalmihf@llc@Ylong@makerequestedresourcesetparameteroptionalinbothther@imanual@~tparameteroptionalinbothther@manual@xeroptionalinbothther@manual@x jpossiblyremovethereferencetoieee802.15asitisnotspVVpotentiallyWpractice&Wpre-configured+WpreciseWWpreciselyWWWWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXWXW[ERudolf, MarianF DisapproveGProducer^ Technical_140`27a 7.6.1.1.1ceIt may sound trivial, but "Initialize" upon receipt of the MIH_NMS_Initialize.request is not defined.d508g5094jA Please define (somewhere) the actions that an MIH protocol entity is supposed to follow upon receipt of this primitive through MIH_NMS_SAP. For example, "MiH entity clears all transactions contexts, deletes all existing registrations to peer MIH entities and so on." vMIH NMS SAP has been deletedw PrincipleyRef 106{l) none needed 2007/12/1909/16/2007 12:18:13 EDTNo o supposed to follow upon receipt of this primitive through MIH_NMS_SAP. For example, "MiH entity clears all transactions contexts, deletes all existing registrations to peer MIH entities and so on." vMIH NMS SAP has been deletedw PrincipleyRef 106{l) none needed 2007/12/0709/16/2007 12:18:13 EDTMarkedNo ommandswDisagree 2007/11/14Producer^ Technical@F DisapproveGGeneral Interest^ Technical_33a6cFor Inter-Tech Handover 802.21 needs to define if the handovers would take place with Single radio in operation or dual radio in operation. Solutions needs to be provided for both cases.d529g5073jpDiscuss specific solution aspects for both for single radio/dual radio case and provide solution for both cases.wDisagree{l) none needed 2007/12/1909/16/2007 13:58:33 EDTYessare genarated 802.11 SME, and as suchB invoking them from any other layar violates the 802.11 architecture. When the 802.21 plays in the context of the 802.11 SME, then it becomes reasonable for the 802.11 WG to architecturally define 802.11 specific interfaces for 802.21.d273g5329jCorrect the 802.21 architecture. The 802.21 entity must reside inside the 802.11 SME. This way, 802.21 can define mechanisms that can use 802.11 SME components. Likewise, same for 802.16 SME.v&Please refer to TGu draft contributionYesjEFamolari, DavidFApproveGGeneral Interest^ Editorial_103`19cLINK_SACN -> LINK_SCANd503g5099jLINK_SACN -> LINK_SCANp done in 19wAgree{k) done 2007/12/1909/16/2007 10:24:17 EDTNo EFamolari, DavidFApproveGGeneral Interest^ Technical_149`42ciThe state machines do no capture the case of : Unsolicited MIH Capability response (broadcasted message).d502g5100jALAdd to section 8.2.3.5.1, page 149, line 42: Since sending or listening to an unsolicited MIH discovery response is an optional feature and an exception to the way normally the protocol works (a response is sent/received only after receiving/sending a request), this option is not represented in the transaction state machines aboveLpW52W54W6$WWWW6.0WW6.2.1W*W6.2.3WW6.3.2W6.3.2shouldbemovedafter6.3.3discussionV6.3.3WW6.3.4.1W6.5.5WW6W6.5.5.1=W6.7W62W64WXWRW65W65535W7WWWWWW7-45W7.0W7.3.1.2.4W7.3.10.1 W7.3.3W7.3.5.4W7.3.6W7.4.19qW7.4.23W7.4.23.2W7.4.5.2.2W7.4.5.2.2theparameterresponselinkeventlistinmihevenV8WWWWHWWWWWWWW8-26W wvAThere is agreement with this principle. Further work required in developing a remedy. MN_HO_Commit should be used only as a local primitive and not as a remote primitive: - Need a request and confirm only. - Dont need Indication and Response primitives (and corresponding MIH messages in section 8) - The functionality of informing the remote side of handover completion/commitment can be accomplished with MN_HO_Complete - This is a local primitive only so may need to change the name w Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNoxERajkumar, AjayF GProducer^ Technical_121`32cIn order to be able to perform a local handover (i.e. replacement for switch command) the destination MIHF ID would not be remote.d406g5196jChange that the destination may be local or remote. Also, specify that it sends a MN_HO_Commit.request message to the destination MIHF only when the destination is not local.pMN_HO_Commit is local only now.oyrefWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW&W'W[W\WlWxWyWWWWWWWWWWWWW W WW W!W"W#W$W'W,WWWWWWWWWWWWWWWWWWref10supercededVref105Vref105duplicatedVref106VVref106duplicateVref11supercededVref114duplicatedVref141Vref141duplicateVref2superceded'Vref20Vref210Vref227duplicated,Vref260V Vref260duplicateVref277Vref339VVref344duplicatedV"VVVref347duplicatedV!VVVref351 VVref351duplicatedVref351superceedVref378VAcvVersion field is not useful unless the specification completely specifies how MIHFs can negotiate on a single version.d205g5397jDelete the Version field.pAgroup disagreed to remove the version field and agreed to add the following: This field is used to specify the version of MIH protocol used. 0: Not to be used 1: First Version 2 - 15: (Reserved) The version number will be incremented only when a fundamental incompatibility exists between a new revision and the prior edition of the standard. An MIH node that receives an MIH message with a higher version number than it supports will discard the frame without indication to the sending MIH Bnode. "vield.vhis field allows implementations to recognize different versions. wDisagree 2007/11/1509/13/2007 16:03:47 EDTYesBEOhba, YoshihiroF DisapproveGProducer^ Technical_82`37a 7.4.2.1.2cKIt is better to include a list of link identifiers in MIH_Register.request.d204g5398|ajreordertableentiresVVreperesent3Wrepetitive<WrephraseWWansport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. To the contrary, it would impose needless constraints to the implementation.6WWWWWWWWWWW;WWWWWWWWWWWWWWWWWWW;WWWWWWW>wEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_18`6a5.3.4cAThe first sentence of the paragraph states that geographic information can be used to obtain handover candidate information. However the rest of the paragraph goes on to discuss how the information is transported to the MN and how the mechanism is out of scope.d305g5297rm used in 3GPP, 3GPP2 and WiMAX Forum. Stay consistent with that.vMStick with Reference Points. This needs to be done throughout the document. wDisagree{f) pass off to other editor 2007/11/2609/16/2007 15:56:25 EDTMarkedYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_20`8a5.4.2cIn Figure 2, you have numbered the communication links according to the classification scheme starting on line 21 of this page. You might alsoi want to number the entities according to the table starting at line 8d550g50528....wDisagree 2007/10/3109/16/2007 15:56:25 EDTYesEcvirtuallyWvisibleWvoiceWvsWwWWw-cdma W WW0W3W7WwaiteWwaitingeWW6g4258jjReplace "The following set of service primites" with "The set of service primitves listed in Table 2 ...." 2007/09/1709/10/2007 07:08:58 EDTNoEEmmelmann, MarcNoEEmmelmann, MarcF DisapproveGAcademic^ Editorial_33`45a6.2.2cEFinal layout by IEEE editorial team will result in tables to "float".d46g4258jjReplace "The following set of service primites" with "The set of service primitves listed in Table 2 ...." 2007/09/1709/10/2007 07:08:58 EDTNoEEmmelmann, Marcmelmann, MarcF DisapproveGAcademic^ Editorial_33`45a6.2.2cEFinal layout by IEEE editorial team will result in tables to "float".d46g4258jjReplace "The following set of service primites" with "The set of service primitves listed in Table 2 ...." 2007/09/1709/10/2007 07:08:58 EDTNoEEmmelmann, Marc9/17,yciWEWFWGWHWWWWWWWWWWWWWW WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWV ctechnology-independeWGGeneral Interest^ Technical_141a8.2.2cThe ACK mechanism is Optional to use and since the State diagrams arre applicable only in this optional case move this section to the Annex.d524g4429jMove section 8.2.2 to Annex 2007/09/1709/16/2007 13:58:33 EDTYeszE Gupta, VivekF DisapproveGGeneral Interest^ Technical_141d wherever appropriate. 2007/09/1709/16/2007 13:58:33 EDTYesyE Gupta, VivekF DisapproveGGeneral Interest^ Technical_144a8.2.2cThe ACK mechanism is Optional to use and since the State diagrams arre applicable only in this optional case move this section to the Annex.d524g4429jMove section 8.2.2 to Annex 2007/09/1709/16/2007 13:58:33 EDTYeszE Gupta, VivekF DisapproveGGeneral Interest^ Technical_1412.2 to Annex 2007/09/1709/16/2007 13:58:33 EDTYeszE Gupta, VivekF DisapproveGGeneral Interest^ Technical_141d523g4430 2007/09/1709/16/2007 13:58:33 EDT_jipW W&WgWkWlWmWWWWip-based'W+Wipaddressinformation>W?Wipconfigurationmetho?WisWWWWWWWWWWWWWWWWW W W WWWWWWW&W'W(W)W0W7W=W?WBWGW]W`WbWfWhWvWwWxWyW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW0W:W;WBWDWJW^WcWWWWWWWWWWWWWWWWWver control plane using a L2 management frame, such as a 802.11 management action frame or a 802.16 MIH MAC management message." 2007/09/1709/16/2007 15:56:25 EDTYesJd571g4382 2007/09/17jllcWWWloWload WlocalWWWWWWW&WwWxWyWWWWW!W"WWWWWWWlocally WW+WlocatedWlocationWWWWWWWlowerWW;Wlsb=WmacWWWWWW;W|WmachinesWmadeWmain5WmakeWWWWWW5W=WfWwWWWmakerequestedresourcesetparameteroptionalinboththerVVmaketheannexnormativeVmakes0Wmaking+W]Wmakingtheseparametersoptionaldoesn'tsolveanyproblemi]VmanagementWWWWW(W<Wmandatory5Wmap5WmappedWmappingWWmappingsWmarkedWWmasked=WmatchWWWmaterialWWmaxWmaximumWmaximumdataratein802.11termsisthehighestavailablebV ykjAAdd a statement requiring that the number of entries in each of the lists (LINK_POA_LIST and QOS_LIST) be the same; Combine Preferred Candidate Link List, Available Resource Set, IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address and IP Address Information Status into a single type and return a list of that type; Further, if resources on a candidate are dependent on a particular PoA then all of these parameters need to be on a link and PoA basis.vA'Please verify: Update the sentence: "On receiving the primitive the MIH User entity which originally initiated the candidate query request may decide to choose the candidate network for handover or abort it based on the list of PoA, available resources, and the IP address related information."'w Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o je_Query request message from a mobile node."Ow Principle 2007/12/0109/16/2007 03:08:31 EDTi EEastwood, Lester FF DisapproveGProducer^ Editorial_51`25a6.5.4csentence is ambiguousd113g5489j`Change to "Functional entities shall discard any received IE with an unrecognizable identifier."{k) done 2007/12/1909/12/2007 02:37:36 EDTNoEEastwood, Lester FF DisapproveGProducer^ Technical_106a7.4.19cMThe Purpose and usefulness of MIH_Net_HO_Candidate_Query command are unclear.d112g5490jJremove all definition and mentioning of MIH_Net_HO_Candidate_Query commandvEEastwood, Lester FF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d111g5491joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.w Superceded{l) none needed 2007/12/0709/12/2007 02:37:36 EDTYes the left-hand side.w Superceded{l) none needed 2007/12/0709/12/2007 02:37:36 EDTYesssFHctypesciviclomethodandgeolomethoddonothaveanyaddeV_cieee's.WiesWW6WWWietf.WWifWWWWWWWWWWWWWWW W WW'W.W1W]WfWgWnWoWrWsWtWuWvWWWWWWWWWWWWWWWWW@WIWNWmWWWWWWWWWWWWWW WWifacontainerislistedshouldbecapitalizedtomatchtheVifanewlyarrivedmihprotocolmessageisfoundtocarryth Vinstate1theywouldalsViftheintentisfortwomihfstomutuallydiscovereachothfVifthemihgetinformationprimitivemustcontainatleastoVifthereisnoreferencespleasechangeclausetexttothereVimminentWW_WwWWimplementWimplementationWWWWWWW W W#W$WWWWWkcisWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W W WWWWWWWWWWWW W"W#W$W'W+W-W.W/W1W2W3W6W7W8W9W;W<W=W?W@WBWFWGWHWIWJWKWLWMWNWRWSWUWVWYW[W\W]W^W_W`WaWbWcWdWeWfWhWiWkWlWmWnWoWrWsWtWvWwWzW{W|W}WWWWWWWWWWWWWX jinvestigatehowtore-organizethedatatypedefinitionseitVVinvestigateifthiscapabilityisneededandhowtobestimpVVinvestigateifthiscapabilityisneededandthebestwaystVinvokedWinvokesjWinvolveW&WgWkWlWmWWWip-based'W+Wipaddressinformation>W?Wipconfigurationmetho?WisWWWWWWWWWWWWWWWWW W W WWWWWWW&W'W(W)W0W7W=W?WBWGW]W`WbWfWhWvWwWxWyW}W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW0W:W;WDWJW^WcWWWWWWWWWWWWWWN jzAdd a subclause defining conventions for PDU structures/drawings in this standard. (See 802.11-2007 7.1.1 for an example).v#Show the bit ordering in the figurewAgree{k) done 2007/12/1908/24/2007 10:31:14 EDTYess isapproveJƒmylesandrewf disapproveƒ disapprove ƒmylesandrewf disapproveƒ disapprovezhƒmylesandrewf disapproveƒ disapprove} ƒmylesandrewf disapproveƒapproveUƒheubaumkarlf approveƒapprove$ƒheubaumkarlf approveƒapprove2aƒheubaumkarlf approveƒheubaumkarlf approveƒapproveovƒheubaumkarlf approveƒ3'ƒapprove3ƒheubaumkarlf approveƒ%"ƒapprove%ƒheubaumkarlf approveƒapprove}Fƒ]@JE Cypher, DavidF DisapproveGGeneral Interest^ Technical_61`34a7221cuTable 10 states air interface for Link_Get_Parameters. However this document's purpose applies to wired and wireless.d134g5468j"Change "air interface" with mediumwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes E Cypher, DavidF DisapproveGGeneral Interest^ Technical_57`5a67cAThis paragraph leads me to understand that the MIH_LINK_SAP is used for transport services when using L2 and MIH_NET_SAP when transport service is L3. However the text for MIH_NET_SAP includes a parameter to select whether L2 or L3 are chosen as transport method. If MIH_NET_SAP is used for L3 only, then there is no need for this parameter. If there is a need for the parameter then the text of this clause 6.7 needs to be changed to reflect the meaning of this parameter. Or could one think ter the text is in plural form.d135g5467j)Change "primitives are" to "primitive is" 2007/11/06 MIHF.)0cin@may@ my@potential@Treliable@some@the@thethreeitemsmakeanormativeassumtionorevenstandardi@things@transport@jagreed@|choose@:e@intent@Dmay@or@Vreplace@similar@pad@^reference@vcalculate@document@request@[thisisaconventionusedthroughoutspacesareusedintabl@{lnoneneeded@yilar@ofmihnethocandidate@similar@ofmihnethocandidate@similar@ingofmihnethocandidate@similar@ingofmihnethocandidate@similar@ngofmihnethocandidate@similar@similar@itionandmentioningofmihnethocandidate@similar@candidate@similar@itionandmentioningofmihnethocandidate@similar@h>0EEastwood, Lester FF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d111g5491joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.w Superceded 2007/11/2609/12/2007 02:37:36 EDTMarkedYesEEastwood, Lester FF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d111g5491joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.w Superceded 2007/11/1809/12/2007 02:37:36 EDTMarkedYesEEastwood, Lester FF DisapproveGProducering two unrelated stacks.d111g5491joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.w Superceded 2007/11/1809/12/2007 02:37:36 EDTMarkedYesEEastwood, Lester FF DisapproveGProducerer[Yes s TMarkedYes needed 2007/12/0109/15/2007 22:08:13 EDTMarkedYesis spec (i.e., no mandatory messages/flows defined for MIHF discovery). This is the right way to do it. Just the text and title in 6.2.3 and 8.2.3.5 may mislead readers otherwise.d343g5259jDe-emphasize MIHF Discovery as separate MIH service management function. Remove 6.2.3 and possibly merge the discussion into general MIH protocol discussion in subclause 8. 2007/11/1209/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Technical_63cd readers otherwise.d343g5259jDe-emphasize MIHF Discovery as separate MIH service management function. Remove 6.2.3 and possibly merge the discussion into general MIH protocol discussion in subclause 8. 2007/11/1209/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Technical_63cmove text "Local Entity" from the stack on the left-hand side. 2007/10/07cresponses]Wresponsible]WWWWWWWrestWWOWQWiWjWkWrestrictWWretainWretentionWretransmissionWWretransmittedWWretransmittedmihresponseisreceivedduetoalotmihackVreverseWrevision/WXWrewordedWrfc^WcWrightWrlc W7Wrlc/mac0W7Wrnc WroamingWWroleWWWrollbackWrouter WOWWrouters WrscpWrsniWrspWPWrssiWruleW/WruledWWrunningWsfWW3WWWsaWWsacnWWsameWWWWWWW W W0WIWKWLWMWNWfWkWlWmWWWWWW$WdWsapWWWWWWWWW6W>WAWBWcWWWWWW W WWW#W$WjchangetothelinkdetectedeventisgeneratedonthemnwhebVchangetotherearetwokindsoftransportVchangetotoby}VchangetouniqueonaperdirectionbasisamongallthependIVchangeumtstow-cdmafddintroducenewidentifiersforw-cd3Vchangevalidrangeto0success1failureVchangedWWchangesW%WQWWWchangingWchannelW1WchapterWcharacterWcharacterizeWcheckWl32WW7W9Wl3WWPWW%Wl32WW7W9Wl3WWPWW%Wl32WW*W7W9Wl3WWPWW%Wl32WWWWWWWWWWW32WWWWWWWWWe\w PrincipleyRef 429{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNoo ent related to event-subscription, link-detect and network commit to be used for network guided handovers. As a concept, the network PoS may not be aware or interested in the PoA specifics for handover selection and decision but only the network identifiers are sufficient to make the decisions. The attached usecase provides more information. Specification changes to support this are individually submitted. Note that these changes are useful even if applied individually to eacBh of the primitivesd615g4987j-Please see the contribution #305, 306 and 307pUpdated subclause 7, need to update 8 and annex 1. and TLV assignments. Note that the contribution shall not be directly applied. Some other comments changed the Link Identifier to LINK_TUPLE_ID. v305-2, 306-02, 307-2w Principle{j) in progress 2007/12/0509/16/2007 21:41:08 EDTYes 307McthistalksonlyaboutwirelesspowermanagementworkisundeVthoseWWuWWWWthough6WWWthoughtWthreeWWthresholdW[WWWthresholds[WWthroughWWWWWWWWWWthroughoutWWzWWthroughoutwholedocumentincorrectuseofindefinitearticlVthroughoutwholedocumentneedtobeconsistentintheuseoVthroughputWWFWthroughputisacommonlyusedcommunicationstermanditisVthrougputWthuskWlWmWuWWWWWWWWtied1W`32a5.3.4c&incoherent usage of singular or plurald36g42684267j"and its representation," 2007/09/1709/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Editorial_17`32a5.3.4c&incoherent usage of singular or plurald36g4268 2007/09/1709/10/2007 07:08:58 EDTNo% ncBh between two different WLANs having different SSIDs). Roaming within a network is an L2 event and is outside the scope of 802.21--yet the text continually refers to "links"--which is a connection to a single PoA, not a "connection" to a network. Thus the text is confusing and misleading--the reader cannot determine what 802.21 is really trying to accomplish.Vd78g5524jEUse the terms "link" and "network" precisely throughout the document.vA9In the document, the term "link" generally refers to a logical connection between the MN and an access network. When instantiated to a "real" link, it mapps to the connection between the MN and a PoA of the access network. The term "network" refers to an access network. The document is fairly consistent on this.9wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYes se information model proposed in Figure 19 is overly complicated as far as 802.11 networks go.d79g5523 2007/11/12?HjIn both line38 and 37: Change default value for Mime-Type from: "application/Sparql results+xml" (which is applicable for query result, but NOT query) to: "application/sparql-query"wAgreeyRef 210{l) none needed 2007/12/1909/16/2007 10:24:17 EDTNo etween basic W-CDMA features, but remove any reference to releases. 0 - R99 only. 1-HSDPA. 2-HSUPA. 3-MBMS&v reference section. 2007/11/1809/16/2007 07:13:12 EDTMarkedNo/ERudolf, MarianF DisapproveGProducer^ Technical_194`38cNetwork type and revision presentation for Wireless - UMTS is wrong. For example, there is no MIMO/OFDM in Rel-7. Then, any MS can be Rel-5 compliant without implementing HSDPA. Similar for Rel-6.d479g5123jxDistinguish between basic W-CDMA features, but remove any reference to releases. 0 - R99 only. 1-HSDPA. 2-HSUPA. 3-MBMS&vDM in Rel-7. Then, any MS can be Rel-5 compliant without implementing HSDPA. Similar for Rel-6.d479g5123J# (nadaWWWWW normative requirements related to the use of QoS in MIH. e.g. - make some; if not all, of the QoS examples of Annex K and related material normative.W޵W޵W޵W޵W޵W޵W޵W޵W޵WflowsރWރWރWރWfnaisusedwhichiscorrectfortheoriginalrfc4068howevQVQVQVQVQVwhichiscorrectfortheoriginalrfc4068howevLVQVQVQVQVQVLVQVQVQVQVQVQVQVQVQVQVQVQVQVQVQVQVQVQVfocused*W*W*W*W*Wsed*W*W*W*W*W*W*W*Wsed*W*W*Wsed*W*Wd*W*W*W {kdoneVVVVVVVVVVVVVVVVVVVVVVVVVVVV V V VlWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW#W&W'W(W+W/W5W7W8W=WGWIWJWUW[W\W]W_WlWqWvWxWyW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWVVVVVVVVVVVVVV17$cimplicitlyW WimpliesWWWimplyWimportantWWWWWWimposeWWWW#W$WWWimposesWWimpossibleWWimprove%WimprovedWWWWWimsiW߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V߲V/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Editorial_12`64a5.1.4c missing commad34g4270jCinsert a comma after networks: ".... target networks, in order ..." 2007/09/1709/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_12`27a5.1.2 2007/09/1709/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_12`27a5.1.2d33g4271 2007/09/1709/10/2007 07:08:58 EDTE Cypher, DavidF DisapproveGGeneral Interest^ Technical_110`61a742024c]The first sentence states that it invokes MIH_N2N_HO_Query_Resources.response primitive. Why?d139g5463jMIH_MN_HO_Candidate_Query.response primitive is more appropriate in response to a MIH_MN_HO_Candidate_Query.indication primitivepYThe sentence was deleted in 420. Change the starting sentence from "It" to "The MIH User"wAgreeyRef 420 (Superceed){k) done 2007/12/1909/13/2007 13:56:26 EDTYes s _Resources.response primitive. Why?d139g5463jMIH_MN_HO_Candidate_Query.response primitive is more appropriate in response to a MIH_MN_HO_Candidate_Query.indication primitivepYThe sentence was deleted in 420. Change the starting sentence from "It" to "The MIH User"wAgreeyRef 420 (Superceed){k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedYes esE Cypher, DavidF DisapproveGGeneral Interest^ Technical_119`25a74222415:41 EDTYes$chandovercompleteispostedfollowinganimminenthoweverth_VhandoverdecisionmakingdoesnotalwaysrequirebothmobileVhandover/roaming/disWhandoverackYWhandoversWWWWWWWqWWWWWWWhappenWWWhappens]WeWhasWWWWW WWbWuWWWWWWWW6WJWNWWWWWWWW W0/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_6`37a3.8cSthere are two definitionf for the same thing: a/ "higher layers" and b/ "MIH Users"d30g4274j09/1709/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_6`37a3.8cSthere are two definitionf for the same thing: a/ "higher layers" and b/ "MIH Users"d30g4274j 2007/09/1709/10/2007 07:08:58 EDTYesN0scdon'tWW~WWWWdon'tseetheneedforthisfieldthedestinationmihfwillV=WWWdstwWdualWdueWWduplicateWWduplicationWduringWWdynamicWdynamicallyWeWWWW9W[W]WgWkWlWmWuWwWxWyW~WWWWeachWWWWWWWWWW WfWWeachbitofabitmapnvaluen8ii12isencodedasannVeachcharacterisencodedinorderofappearancewhereeachVeap7WearlyWeastWec/ioWeffectuWeffective=Wefficient=Weffort=Wegprs0Wegprs/w-cdma0WeitherWWwWWelementWWWelementsWWelemetsWeliminateWeliminatesWelseWWemergencyWemphasise@WemsWenableWWexhibitWexistedWexistingWFBjscope W6W?WWWWWWscrambling4Wsdo'sWsduWsecondW:W;WsectionWWWWWWWWWWWWW-W.W7W<WRWgWhWWWWWWW)W.W0W3WWWWsecure7WsecuringWsecurityW7WWWWWseeWWWWWWWWWW%WXW[W\WhWWWseecommentVseecommentforproposedresolutionVseepage66lines35-36andpage71lines32-33[Vseepage71line32-32\VselectWselectedWselectionWWselectorWselfWsendWsenderIWsendingWsendsxWyWsense0Wsent7WvWWWsent/receivedWsentenceWWWWWWWWWWsentencesWseparateWWservergWkWlWmWf UcbetweenWWWWWWWWWWWWive may trigger MIH User to initiate the process to get IP address to be used in the target depending on the received candidate query response" mean? Seems to be an unrelated statement.d414g4539j Delete line. 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_114`112r. 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_113`2426cWhat does "This primitive may trigger MIH User to initiate the process to get IP address to be used in the target depending on the received candidate query response" mean? Seems to be an unrelated statement.d414g4539j Delete line. 2007/09/1709/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_114`112 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_114`112d413g4540 2007/09/1709/16/2007 03:08:31 EDTgeneralinterestVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW-WaWߧWߨWWWWWWjustprovidingmacaddressesofpoaisinsufficientfornetwV$VKcconformantWWconfused6WconfusingWWW$WKWLWMWNWwWWW!W"WGWHWWWWWWconfusionWconjunction7Wconnect0WconnectedWWWconnecting7Wfic implementations.d608g4345jDiscuss. 2007/09/1709/16/2007 21:41:08 EDTYes&ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_67`41a7.3.4.2conality? The parameters "Time interval" and "Confidence level" are based on vendor specific implementations.d608g4345jDiscuss. 2007/09/1709/16/2007 21:41:08 EDTYes&ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_67`41a7.3.4.2cnthula, SrinviasF DisapproveGGeneral Interest^ Technical_67`41a7.3.4.2cd607g4346 2007/09/1709/16/2007 21:41:08 EDTW޲WW޲W޲W BcA'"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in order of significance." I dont' think this is unambiguous. Does it mean that the lowest numbered such octet is first or last. Likewise references to "network byte order" later on have no normative definition.'d6g5596jI recommend a conventions subclause before B.1.1 that defines unambigously: 1. The ordering of bits in an octet (most or least significant is B0?) 2. The ordering of octets in a multi-octet integer (is the lowest numbered octet least or most significant?)vAlso look at comment 384 and changes made therein. Changes to be made on top of change specified in comment 384 Plesae refer to 21-07-0396-01-0000w Principley Ref Cmt 576{l) none needed 2007/12/1908/24/2007 10:31:14 EDTYes ptimizing the adaptation to the new conditions.a 2007/11/1809/03/2007 02:30:39 EDTNoEStephens, Adrian PF DisapproveGProducer^General_194Uz cAThe text states that Link_Detected indicates that a new "type of link" has been detected for use. The term "type of link" has not been defined and thus the text is unclear. Does "type of link" mean a link to a different network, another PoA in the current network, or something else? Hopefully it's referring to a link in a different network. If it's referring to another PoA in the current network, then the Link_Detected event will be sent to the higher layers constantly (e.g., whenever a neBJw AP is detected in a WLAN). This does not help inter-technology handover.8d94g5508jClarify the text.pAJChange "Link_Detected indicates that a new type of link has been detected for use." to "Link_Detected indicates the presence of a new PoA." Add the following sentence to the end of the paragraph: "Link_Detected is not generated when additional PoAs of the same link are discovered. In case of 802.11, this is generated by MSCGF."Jfy the text._192`51aB.2.7cd‚Ã!Ã! Ã!0Ã!@Ã!PÃ!`Ã!pÃ!Ã!Ã!Ã"Ã" Ã"0Ã"@Ã"PÃ"`Ã"pÃ"Ã"Ã"Ã#Ã# Ã#0Ã#@Ã#PÃ#`Ã#pÃ#Ã#Ã#Ã$Ã$ Ã$0Ã$@Ã$PÃ$`Ã$pÃ$Ã$Ã$Ã%Ã% Ã%0Ã%@Ã%P~Ã%`}Ã%p|Ã%{Ã%zÃ%yÃ&xÃ& wÃ&0vÃ&@uÃ&PtÃ&`sÃ&prÃ&qÃ&pÃ&oÃ'nÃ' mÃ'0lÃ'@kÃ'PjÃ'`iÃ'phÃ'gÃ'fÃ'eÃ(dÃ( cÃ(0bÃ(@aÃ(P`Ã(`_Ã(p^Ã(]Ã(\Ã([Ã)ZÃ) YÃ)0XÃ)@WÃ)PVÃ)`UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>007 16:19:39 EDTs:E Kim, EunahF DisapproveGGeneral Interest^ Technical_23`37cAThe definition of NMS (Network Management System) is not defined in section 3. NMS is a term that describes a computer-based software application suite dedicated to the management of networks of NEs (Network Elements). Typically, the NMS provides abstractions (such as signaling links and virtual connections) appropriate to the overall running of a network; that is, it is not exclusively concerned with the details of one NE. Communication between an NMS and NEs is typically executed via an suite dedicated to the management of networks of NEs (Network Elements). Typically, the NMS provides abstractions (such as signaling links and virtual connections) appropriate to the overall running of a network; that is, it is not exclusively concerned with the details of one NE. Communication between an NMS and NEs is typically executed via an mitives in text doesn't not match syntax in adjoining description table line 39-65d642e09/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_124`35cnHere "Target PoA" is specified as MAC_ADDRESS (as well as in MN_HO_Commit) but the Net_HO_Commit uses LINK_ID.d395g5207j#Change them to LINK-ID consistentlypSinstead, use MAC_ADDRESS in Net_HO_Commit for consistency (for less editorial work)wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_128`13c[The description contains "This identifies the current link" for the source link identifier.d394g5208j_Change "This identifies the current link" to "This identifies the source link of the handover".wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_128`65c"The "may" makes it sound optional.d393g5209393g5209393g5209393g5209A is already included in Target Link Identifier. This is redundant.d619g4983jRemovewAgree{k) done4gQ<crWWr1WTWVWr3TWVWr5WradioWWWradiosWWrandomWWrangeWWWWWWrapidlyWrateWWWWFWratesWWratherWWWWWWWrawWrdfWuWuWuWuW09/04/2007 16:19:39 EDTYesE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_102`17ctypod19g4285jchange LINK_SACN to LINK_SCAN 2007/09/1709/04/2007 16:19:39 EDTNoE Golmie, NadaF DisapproveGGovernment/Military^ Technical_102cd18g4286 2007/09/1709/04/2007 16:19:39 EDT8 E Seifert, RichF DisapproveGGeneral Interest^ Editorial_3`50a1.4cThe text states that the definition of MIHF has no implications on the way the function is implemented. This is clearly not true; if it is, then the definition is irrelevant.d14g5588e., no statement of exactly what procedures *shall* be implemented by a conformant device. Thus, the service management requirement is ambiguous.d15g5587jInclude a formal specification of the required service management procedures, either here or in Clause 6. Include a PICS proforma for these procedures, to ensure that all necessary functions are properly implemented.v10w Superceded 2007/11/3009/03/2007 16:49:33 EDTYesE Seifert, RichF DisapproveGGeneral Interest^ Editorial_3`50a1.4cThe text states that the definition of MIHF has no implications on the way the function is implemented. This is clearly not true; if it is, then the definition is irrelevant.d14g5588d15g5587Q_ERajkumar, AjayF GProducer^ Technical_73`65ctHandover complete is posted following an imminent. However, there is no mechanism for indicating a handover failure.d431g5171j%Add a status code indicating success.pPlease check again. w Principle{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNo o OS_LIST.7d432g5170jChange QOS_LIST to LINK_PARAM_QOS_LIST. Add LINK_PARAM_QOS_LIST with an enumerated type and a value of 0 requesting the return of QOS_LIST.pAnnex 1w Principle{j) in progress 2007/12/0709/16/2007 03:08:31 EDTMarkedNo _ERajkumar, AjayF GProducer^ Technical_73`65ctHandover complete is posted following an imminent. However, there is no mechanism for indicating a handover failure.d431g5171j%Add a status code indicating success.pPlease check again. w Principle{l) none needed 2007/12/0709/16/2007 03:08:31 EDTMarkedNo No^ERajkumar, AjayF " ca"A similar mechanism may be available for IEEE 802.16 for this query" - is there or isn't there ?d514g5088jClearly state if 802.16 provides a mechanism similar to the 802.11u action frames to allow for certain MIH IS exchanges before Authenticated and Associatedpsuperceded by change from 334v:This is supported in 802.16 as well before authentication.wAgree{l) none needed 2007/12/1909/16/2007 13:36:45 EDTNo ERudolf, MarianF DisapproveGProducer^ Technical_67`9a7.4.3cAwLINK_UP.indication contains MAC addresses of old and new access routers in its parameters list. That would probably apply for most LINK_UP indications received from 802 access technologies in certain deployments (but for home routers ?), but what would be the corresponding vales in the case of LINK_UP received for GSM/EGPRS or W-CDMA links where there is no access router ?wd513g508913g50892a6.5.2NXECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_191`39aB.2.8c,(Kenichi) BITMAP(64) should name as REVISIONd438g5164G_PARTNERd439g5163vA - p48 L15 TYPE_IE_ROAMING_PARTNERS -> TYPE_IE_ROAMING_PARTNER ROAMING_PARTNERS -> OPERATOR_ID - p50 L22 Figure 19: The TYPE_IE_ROAMING_PARTNERS -> TYPE_IE_ROAMING_PARTNER and add additional "..." in a way to identify there can be multiple TYPE_IE listed. -p52 L62 Roaming Partners IE -> Roaming Partner IE and add additiona "..." to identify there can be multiple entries. - p192 L13 Delete the ROAMING_PARTNERS - p201 LB714 Bit 8: TYPE_IE_ROAMING_PARTNER (remove S). %w Principle 2007/11/2609/16/2007 03:35:02 EDTMarkedYes XECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_191`39aB.2.8c,(Kenichi) BITMAP(64) should name as REVISIONd438g5164/1809/16/2007 03:35:02 EDTMarkedYes \EMontemurro, MichaelF DisapproveGGeneral Interest^ Editorial_32`33a5.7.2c5Remove the period from the beginning of the paragraphd308g5294j See comment.pSame as Cmt 44{k) done 2007/12/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_26`37a5.5.3cWIf MLME-SAP messages are permitted in State 1. They would also be permitted in state 3.d307g5295jSChange the text to state that the MIH MLME-SAP message are permitted in all states.wAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYesssrkedYesring the registration process to provide authorisation or remove this sentence from the draft because there is no authorization. 2007/11/1309/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_32`50a5.7.2Montemurro, MichaelF DisapproveGGeneral Interest^ Technical_34`58a6.3.4.1:::@] cthisWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW!W&W'W.W1W7W@WCW[W\W]WaWbWdWfWgWhWiWpWrWsWuWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW#W$W/W0W<W@WFWIWMWXWmWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWVkj0wAgree{k) done 2007/12/1909/13/2007 16:42:41 EDTNo 1ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_96`22a 7.4.12.1.2c8Missing a parenthesis for the type of Packet Identifier.d221g5381j!UNSIGNED_INT2) -> UNSIGNED_INT(2)wAgree{k) done 2007/12/1909/13/2007 16:42:41 EDTYes 2ECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_95`58a 7.3.14.1.2cParameters for Link_Get_Parameters primitive (LINK_PARAM_TYPE) does not support all the parameters required in MIH_Link_Get_Parameters (p99L12 LINK_STATUS_REQ). Data type LINK_PARAM_TYPE p180L5; LINK_STATUS_REQ p183L13.d220g5382j~The parameter for the Link_Get_Parameters should contain Link_Status & Link_Discriptor. See contribution 21-07-303-00-0000.docwAgree{k) done 2007/12/1909/13/2007 16:42:41 EDTYes3/2007 16:42:41 EDTMarkedNo07 03:35:02 EDTYeseng, Yuu HengF DisapproveGGeneral Interest^ TechnicalnicaljinsertmaydecisionmakingmayinvolveVinsideWinsteadWWintW1Wint21WintegerWintegralWintegrateWintegratemihnetsapandmihlinksapintomihlowersapitVintendedWintendendKWLWMWNWn previous or terminate the MIH function and capability discovery procedure."d571g4382jA "When the timer expires without receiving a response message, the requestor may try the combined MIH function discovery and capability discovery procedure using a different transport than previously or terminate the MIH function and capability discovery procedure."  2007/09/179cnetworks--eWWnever&WeWneverthelessWWnevery WnewWWW WKWLWMWNWuWWMWdWWWWWWW Wnewest^WcWnewly WnextWWWuWWniceWWWnihWnmsWWWWWWW W#WWWnmsisusedfornetworkmanagementandistobeastand-alonVVnoWWWWWWWWWWWW WWW/W8W\W_WaWgWrWsWWWWWWWWWWWWWWWWW#W)W8WKWLWWWXWYWbWeWfWnWoWpWsWxWWWWWWWWWWWWWWWWWWWsE Feder, PeretzF DisapproveGProducer^ Technicald448g4505 2007/09/1709/16/2007 03:38:14 EDTcrouters WrowsWrowsshouldbegroupedsortedbyservicecategoryVrscpWrsniWrspWPWWrssiWruleW/WruledWWrunningWsfWW3WWWnWWWWsaWWsacnWWsameWWWWWWW W W0WIWKWLWMWNWfWkWlWmWWWWWW$WdWtWWWWWW W WsapWWWWWWWWW6W>WAWBWcWWWWWW W WWW#W$WWWWWWWWWWWWW 2007/09/1709/16/2007 03:35:02 EDTYesERajkumar, AjayF GProducer^ Technical_100`64cd435g4518 2007/09/1709/16/2007 03:08:31 EDTz@%&@jEpA}FvcA@'ccw@L@@5@@ @@'j@j@c6@v~@)@3@*@3@@a+@"jDc.y@yd@r@@j@@FG@@@j@mj w @cB+ cAB++cB++@@M@@M@@M@@M@@jM@@@@@@M@@cmG+jaG j} jAF G jCcBdj?jB)HcAdbU4cvariables'WWvariousWWWWW$WWWWWvaryWW#WWvendorWWvendorsWWWver Wverb{Wverbose<WverifiedWversionWAWversionfieldisnotusefulunlessthespecificationcompletAVversionsWvertical/horizontalgWveryWWWWWW<W[WWWWWWMWWviaWcWWWWviabilityWviewWviewedWviolatesWvirtualWWWWWWWWWWWWWWWWWW0jtargetWWDWEWJWKWLWMWNWdW|WWWWW8WWtargetpoaWtbdWtd-scdma3Wtdd3Wtechnical W'W)WtechnologiesWW W'W0W3W6WWWWWtechnologyW W&W7WWWWWWtechnology-specific1WWtermWterminateWterminologyWtermsWWWWtest+WtextWWWWWW WWWW WWWWWWWWWWWWWWWWWWWWWWWW!W"W)W.W@WJWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWthatthemihuseruponreceivingthenethocommitindicatiotV1dÃrÃrÃrÃsÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0Ãt@ÃtPÃt`ÃtpÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃuÃuÃvÃvfective. A 32-bit "Type" field is enormous, so it seems reasonable to use 2 bits in the "Type" field to indicate the size of the "Length" field, representing 1-4 octets respectively for the size of the "Length" field. The encoding and decoding of such infoBXrmation seems to be also more efficient than the 3 cases described in the current draft.Fd465g4488j 2007/09/1709/16/2007 06:10:15 EDTYess not necessary for a conformant device to use internal lad12g4292 2007/09/1709/03/2007 16:49:33 EDT&chendersonWWWWhendersongregorysVVVVhengOWPWQWRWSWTWUWVWWWXWYWZW-W.W/W0W1W2W3W4W5W6WheubaumWWWWWWWWWheubaumkarlfVVVVVVVVVWWWWWkimWWWWkimeunahVVVVkwakWWWWWWWWWWkwakjosephaVVVVVVVVVVlach<W=W>W?W@WAWBWlachhong-yon<V=V>V?V@VAVBVleeuwenWWlevyWWWWlevyjosephsVVVVmWWmarian W W W WWWWWWWW%W&W'W(W)W*W+W,W-W.W/W0W1W2W3W4W5W6W7W8W9W:W;WNjsuggestWWWWWsuggestrewritingthissectionVsuggesttomove8.2.2toanannexVVsuggestedWWsuitableWsummarize7Wsummary,WWsuperset&Wsupplied7WsupportW&W8WWWWWsupportedWWWWWW&WVWWCWDWiWjWWsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliWsupportingWsupportsWWsupposedW7WGWswitchWWswitchlocationofremotemihfandremotelowerlayersinfiVswitchtheorderofassociateandauthenticateintherefereVsymmetricalWsyntaxWsystemWUWWt'WtableWWW=WXWWWWW3W8WPWQWWWWWWWWtakeWwW}Wtakealookwhatother802standardsdoesanddefinethenorVW83EEmmelmann, MarcF DisapproveGAcademic^ Technical_21`2a5.4.3cwFigure 3 alludes that MIH Reference points do not exist accross the Internet but only within coupled operator networks.d38g5564jinclude, e.g., an operator-4 core which is connected to the internet and label the arrows to/from the internet cloud with corresponding reference points.vFigure -3 is just an illustrative example and it's quite difficult to include the above suggestion in this example. This example has no bearing on other deployment scenarios (which may include MIH Ref Points going across the internet). wDisagree{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYesso include the above suggestion in this example. This example has no bearing on other deployment scenarios (which may include MIH Ref Points going across the internet). wDisagree{l) none needed 2007/11/2609/10/2007 07:08:58 EDTMarkedYesProducer^ Technical_26`1a5.5.3c807T vAIn table B-4 page 182, lines 5 and 36, add the following sentence in the Definition column of THRESHOLD_VALUE and LINK_PARAM_VALUE: "The format of the media-dependent value is defined in the respective media specification standard and the equivalent number of bits (i.e. first bits) of this data type is used. In case that there are remaining unused bits in the data type, these are marked as all-zeros (0). w Principle{k) done 2007/12/1909/16/2007 12:18:13 EDTYes How does the 802.21 THRESHOLD value map to the CPICH_RSCP measurement? Another example, TrCh BLER configurable as a type in 802.21 which in 3G is reported as 1 out of 64 values log10(measurement in the range of 0.00 to 1.0). Would this fit the 0...65535 range ? Moreover, I am almost afraid that the current draft is in a similar situation w.r.t other access technologies. For example, how would THRESHOLD map to the 802.11 Beacon RSSI ? Or is this described somewhere else in the draft and dÃSaÃT`ÃT _ÃT0^ÃT@]ÃTP\ÃT`[ÃTpZÃTYÃTXÃTWÃUVÃU UÃU0TÃU@SÃUPRÃU`QÃUpPÃUOÃUNÃUMÃVLÃV KÃV0JÃV@IÃVPHÃV`GÃVpFÃVEÃVDÃVCÃWBÃW AÃW0@ÃW@?ÃWP>ÃW`=ÃWp<ÃW;ÃW:ÃW9ÃX8ÃX 7ÃX06ÃX@5ÃXP4ÃX`3ÃXp2ÃX1ÃX0ÃX/ÃY.ÃY -ÃY0,ÃY@+ÃYP*ÃY`)ÃYp(ÃY'ÃY&ÃY%ÃZ$ÃZ #ÃZ0"ÃZ@!ÃZP ÃZ`ÃZpÃZÃZÃZÃaÃa Ãa0Ãa@ÃaPÃa`ÃapÃaÃaÃaÃbÃb Ãb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdWWb :cnotWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWW are the same in my mindd381g4572jqChange range 0-24 to 'Poor' and range 25-49 to 'Average', range 50-74 to 'Good' and range '75-100' to 'Excellent' 2007/09/1709/16/2007 02:47:09 EDTNo 'Poor' signal strength are the same in my mindd381g4572jqChange range 0-24 to 'Poor' and range 25-49 to 'Average', range 50-74 to 'Good' and range '75-100' to 'Excellent' 2007/09/1709/16/2007 02:47:09 EDTNo nal strength are the same in my mindd381g4572jqChange range 0-24 to 'Poor' and range 25-49 to 'Average', range 50-74 to 'Good' and range '75-100' to 'Excellent' 2007/09/1709/16/2007 02:47:09 EDTNo d380g4573 2007/09/17pERudolf, MarianF DisapproveGProducer^ Technical_45`30a6.4.3.2cI don't understand the logic behind classifying Link_Event_subscribe and _Unsubsribe into the MIH command service ? Wouldn't these two be part of Event Service ?d511g5091j;Move Link_Event_Subscribe and _Unsubscribe to section 6.3.3vThese are part of Service management category and not Command Service at the MIH level. At the link level they are part of Link CommandswDisagree{l) none needed 2007/12/19dYes ERudolf, MarianF DisapproveGProducer^ Technical_45`30a6.4.3.2cI don't understand the logic behind classifying Link_Event_subscribe and _Unsubsribe into the MIH command service ? Wouldn't these two be part of Event Service ?d511g5091j;Move Link_Event_Subscribe and _Unsubscribe to section 6.3.3vThese are part of Service management category and not Command Service at the MIH level. At the link level they are part of Link CommandswDisagree{l) none needed 2007/12/07,cserverOWkWlWmWnWoWserviceWWWW"W#W7W>WAWBWWWWWWW WWW*WqWWWWWWWWWWWWservicesWWWW$W7WWWWWWWservingWWdWsetWWWWWWWW&W'WWWWWW@WWWWWWsetsWsettingvWWWsetting/gettingGWsetup7WseveralWWWW WWseverallocationswheremacaddressisusedinsteadofagenVVVseveralmihhandoverprimitivesusecurrentlinkidentifieasVsgsn0W7WshadedW \EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_13`36a5.1.7cThe security clause states that information on link security will be made available to a UA for potential handover candidates. However it does not make a statement on security considerations for the IEEE 802.21 primitives or protocol themselves.d300g5302dify the second section of the paragraph to state that the protocol minimizes the scanning required to discover and select another network as a handover candidate.v by 331. w Supercededydeferred. Ref Cmt 331 2007/11/2609/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_13`36a5.1.7cThe security clause states that information on link security will be made available to a UA for potential handover candidates. However it does not make a statement on security considerations for the IEEE 802.21 primitives or protocol themselves.d300g5302emselves.d300g5302wAgreeWIPwg5195jAOne way forward is to have MIH User to MIH User exchange take place. This would be followed by an MN_HO_Commit request with the dst MIHF ID equal to the local MIHF ID (i.e. it is a local command). The MN_HO_Commit command could issue to Link HO Imminent at the beginning of the processing of this command. However, we still have a couple of problems. The local MN_HO_Commit command does not have any Link Actions so it would have to be driven by MIHF but it doesn't know whether it should be maBke before break or break before make. Also, we are still left with the problem of knowing when to issue the Link HO Complete event (e.g. after upper layer handover processing, MIP).vk Actions) the MIHF doesn't know when to issue a Link HO Imminent. In the combined case MIHF is in control and can issue the Link HO Imminent just before is executes the Link Actions. The problem with this is that the MN_HO_Commit command does not have any associated Link Actions.d407WYijlong2WlongitudeWlongitudeshouldbenormalizedtowithin180degreespositivVlook WW2WlooseWloosen WlostWWlowerWW;WWWWlowestWlsapWlsb=WmWWWm-mtm-rspWmacWWWWWW;W|WWWmac-wimax_Wmac-wlan`WmachineWWWWWmachinesWmadeWWWmain5WmakeWWWWWW5W=WfWwWWWWWWWWW*W3WWW Wmakeallowancestoenableanmihusertorequestforreserva*VmakeannexnormativeV<WWWmandatory5Wmap5WmappedWmappingWWWmappingsWmarkedWWWWmasked=WmatchWWWmaterialWWmaxWmaximumWmaximumdataratein802.11termsisthehighestavailablebVVgeneralWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWOWPWQWRWSWTWUWVWWWXWYWZWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWqcifatleastonequeryisrequiredthereshouldbesomeminim@implementations@$implicitly@mation for IP-based external transport interfaces. Alternatively, describe a means to transport at least a limited set of MIH messages through GMM or GTP messages, like Direct Transfer etc., even if any formal specification would be incumbent to 3GPP one day. needa t least to describe or at least outline the principle of 2-3 technical approaches to guide an implementor. The only other alternBative is to entirely remove 3GPP from the list of access technologies that 802.21 can operate with (everywhere in the 802.21 draft specification).EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_153`14a8.6cI assume that the TLV type assignment is normative for this protocol. If so, it should be included in the body of the specification.d320g5282nt should be "shall"vby 326w Superceded 2007/12/0709/14/2007 23:15:41 EDTMarkedYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_153`14a8.6cI assume that the TLV type assignment is normative for this protocol. If so, it should be included in the body of the specification.d320g5282 at least one query. Therefore the statement should be "shall"vby 326w Superceded 2007/12/0509/14/2007 23:15:41 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_153`14a8.6cI assume that the TLV type assignment is normative for this protocol. If so, it should be included in the body of the specification.d320g5282320g5282320g5282Montemurro, MichaelF Disapprove߲Wp bcA8"The MIH services defined by the IEEE 802.21 standard, including event, command, and information services, need to consider network traffic performance objectives and how well they meet the application quality of service requirements." sounds like a requirement, and not a description of the 802.21 architecture.8d270g5332jhRewrite this clause and other portions of Clause 5 to precisely reflect the 802.21 functions and design.psuperceded by 35v$by comment 35. Paragraph is deleted.w Principley Ref Cmt 35{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYes sYjsubsequentlyW=Wsubset5Wsuccess_WWWsuccessfulWsuggestrewritingthissectionVsummary,Wsuperset&WsupportW&WsupportedWWWWWW&WsupportedisquerytypeWsupportedmihcommandlWsupportedmiheventlisWsupportedtransportliWsupportingWsupportsWsupposedWsyntaxWsystemWt'WtableWWWtakeWtakealookwhatother802standardsdoesanddefinethenorVtargetWWtbdWtd-scdma3Wtdd3Wtechnical W'W)WtechnologiesWW W'W0W3WtechnologyW W&Wtechnology-specific1WtermWterminateWtermsWWtest+WtextWWWWWW WWWW WthWthanWWWWthatWWWWWWWWWW WWW&W'W)W0WRvbyWWWWWWWW)WpWWWWWWWWW WWby105Vby471Vby497V8VVVVby576VVVVV6VVV6VVVV6VV6VVV5VV5VVVVVV5VVVVVV9Vher will result in the reestablishment of a link layer connection to the target access network." 2007/09/1709/16/2007 15:56:25 EDTYes[EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_35a6.2.5cFigure 12, you might want to indicate that the MIH Event Subscription Request/Response and the MIH Command Request/Response do not have to go in the directions they are shown; that the reverse directions are also allowed. Request/Response do not have to go in the directions they are shown; that the reverse directions are also allowed.c21-05-0359r2W21-07-0315-00-0000-dW21-07-0316-00-0000-mW21-07-0317-00-0000-sW21-24bW216W22W228UW23W230eWwW231wW24W25W25.133W252wW26WFW27WWWWuWWW28-31eW2ndW2sW3WWW4W5W=WWWtWWWWWW3.3WYesuE Gupta, VivekF Disapprove09/16/2007 13:58:33 EDTYestE Gupta, VivekF DisapproveGGeneral Interest^ Technical_33a6cFor Inter-Tech Handover 802.21 needs to define if the handovers would take place with Single radio in operation or dual radio in operation. Solutions needs to be provided for both cases.d529g4424jpDiscuss specific solution aspects for both for single radio/dual radio case and provide solution for both cases. 2007/09/1709/16/2007 13:58:33 EDTYesuE Gupta, VivekF Disapprove5 2007/09/1709/16/2007 13:58:33 EDTRcwhichWWWWWWWWWWWWWWW WWW%W'W+W7WIW]W^WwW|W~WWWWWWWWWWWWWW/W@WMWZW\W^WcWWWWWWWWWWWWWWWWWd at the beginning and end of a period of interest. Subtracting the ending value from the value at the beginninBg of the period produces a relevant count for that period. This is only true, however, if counter overflow does not occur during the period of interest.d636g4317j Fix this basic misunderstanding. 2007/09/1709/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_289`4aKcd635g4318 2007/09/1709/16/2007 23:32:08 EDT10:31:14 EDTYesEStephens, Adrian PGProducerd2g4302 2007/09/1708/24/2007 10:31:14 EDT`c_‚E փ׃؃)‚F*‚Gⵃⶃ"㡃㢃‚Hⴃ‚I‚J᷃ḃ,‚Q+‚Rᴃᵃ<⚃‚Sⳃ!㟃‚T♃‚Ud*L㍃‚V‚W⽃‚X ‚YVW⺃‚Z‚aԃ㌃㾃㿃‚bⱃ6‚c᱃ᲃ᳃=㋃㹃㺃㻃㼃‚dӃ㊃㴃㵃㶃㷃‚f҃45‚g#‚h"c‚jڃ‚qу؃‚r㇃㈃‚s‚t⸃ #㤃‚v‚w‚xᯃ 㲃㳃‚yᮃ3‚z‚ᭃb‚᫃ `a☃(ㆃ㯃‚᪃ᬃ!@PRhÃ!`Ã!Ã!ⓃÃ!giÃ"jÃ" OmoÃ"0lÃ"@knpIÃ"PqsÃ"`rÃ"ឃᢃ Ã"tÃ#uvÃ# ᝃᤃwxy{|}Ã#0ᣃz~ Ã#@⁃Ã#P᥃⃃Ã#`Ã#CÃ#E℃⅃Ↄ0 2007/12/1909/17/2007 08:47:07 EDTYes EHenderson, Gregory SF DisapproveGProducer^General_208`1aAnnex DcXML does not compiled645g4957jtChange to: pA% In this draft we will still keep it this way so that we won't forget to update it. If we update the URL with a bogus address, it may cause confusion. Decision should be "Principle" Resolution is: "A valid URL will be placed when a persistent URL is assigned within next couple of revisions." %v&URL_TO_BE_ASSIGNED needs to be updatedwAgree{h) defer to next round 2007/12/1909/16/2007 23:51:48 EDTMarkedYes2d644g4958j$Define values for these two networksvu3GPP and 3GPP2 networks have been included in the table. Commenter to come back with any specific inputs if required.wDisagree{l) none needed 2007/12/1209/16/2007 23:51:48 EDTYes csingleWWGWWWWWAWWWWsingularWWsingularorpluralshouldbeusedchanginglinkimpliesVsitWsitting7WsituationW&Wsize=W WskippedWsmeWWWWWWsnrWsoWWWWWW=WtWvWWWWWWWW/WYW{WWWWWWWsoftwareWsolutionW&W'WsolutionsWWsolvedW(WamendWWamendmentuWamendmentsW=WLWammendmentsWamongWanWW WWW'WBWEWGWHWbWoWpW߁W߂WߒWߝWߞWߢWߥWߧWߨWߵW߸WWWWWWWWWWW WW%W/W0W6W:WIWJWKWNWSWUWVW`WbWcWfWiWrWuWvWyW{WWWWWWWcthings@this@@]thismessageisusedforcommunicationbetweenthemihfona@thistalksonlyaboutwirelesspowermanagementworkisunde@htime@Mto% to/from@too@0topic@Zopic@ZZZZZugh@to@w޼topic@_topic@_through@to@wިtopic@___thresholds@tlvs@wto{topic@_those@thresholds@tlvs@wto{topic@_ds@tlvs@wtogtopic@_c@_ic@_=topic@_nbeconfused@wto%=topic@_elementscanbeconfused@wto"=topic@_too@_onfused@wtoݿ=to/from@too@_wto݋=to/from@too@_beconfused@wto=to/from@too@_b1^ Technical_195`12aB2.9.1ceThe section is titled "Binary Information Query". However I believe it defines Info Query Binary Datad327g5275jsClearly define the InfoQueryBinaryData IE or if it exists add a refernce to it in clause 7 and 8, where it is used.pref added in clause 7.vAdd a referencewAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYes  annex B should be described in clause 7 and 8. (Please Verify)vAdd a referencewAgree{j) in progress 2007/12/1209/14/2007 23:15:41 EDTYes tled "Binary Information Query". However I believe it defines Info Query Binary Datad327g5275jsClearly define the InfoQueryBinaryData IE or if it exists add a refernce to it in clause 7 and 8, where it is used.vAdd a referencewAgree{i) to do 2007/12/1209/14/2007 23:15:41 EDTYes s s X^jfixthisbasicmisunderstandingVVfixedWWWWWWWflagWflexibilityW(Wflow&WWfmip&Wfmipv6^WcWfoWfollowWWfollowedWWwWfollowing WW&W+WWWWW.W4W8W=WWWWW WWWWWWW&W'W)W+W-W2W3W6W7W8W:W=WBWGWZW`WcWeWhWvWzW{WWWWWWWWWWWWWWWWWWWWforexampleassumeanddescribeherewhatevermipshopwillp'Vforexampleinthespecificcaseof802.11statethatmihre7Vforexampletheieee802.11lowerlayersarethemacsublayeVforexampletheoccurrenceofahandoverofamobilenodefrVforexamplewirelessnetworkscouldbeenhancedforcarrying)VformWformal'W6W;/ @ |@j@‚bƒ disapproveƒ,cypherdavid@ƒLcypherdavid@ƒkcypherdavid@ƒRƒcypherdavid@ƒmylesandrewf@ƒapproveƒemmelmannmarc@„ disapprove„"seifertrich@ @ @ @ vozj@@CE Cheng, HongF DisapproveGProducer^ Technical_14`45a5IH is about handover between different access technologies. Yet, there is not even one normative reference. Is the MIH really built from scratch that does not rely on any prior defined technolgy?d497g5105jVTake a look what other 802 standards does, and define the normative reference for MIH.v+Qiaobing to fx this and provide explanationwAgreey deferred. 2007/11/2609/16/2007 08:19:02 EDTYesE Cheng, HongF DisapproveGProducer^ Technical_14`45a5jVTake a look what other 802 standards does, and define the normative reference for MIH.v+Qiaobing to fx this and provide explanationwAgreey deferred. 2007/11/1809/16/2007 08:19:02 EDTYesE Cheng, HongF DisapproveGProducer^ Technical_14`45a59:02 EDTYesE Cheng, HongF DisapproveGProducer^ Technical_14`45a53:06 EDTYes09/16/2007 15:23:06 EDTYesWE Cypher, DavidF DisapproveGGeneral Interest^ Technical_280`52cFThere is no MIH_Link_Action(s) message corresponding to clause 8.6.3.6d183g5419jAdd missing message to listwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes XE Cypher, DavidF DisapproveGGeneral Interest^ Technical_280`51c0There is no MIH_Configure message with this named182g5420j?Change to MIH_Link_Configure_Thresholds to match clause 8.6.3.3wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes YE Cypher, DavidF DisapproveGGeneral Interest^ Technical_276`50coThere is no HandoverAck parameter or TLV in the MIH_MN_HO_Candidate_Query Response message, so why is it there?d181g5421jDelete both occurrenceswAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes ZE Cypher, DavidF DisapproveGGeneral Interest^ Technical_273`24_273`24_273`24_273`24t vstateWWWWstatementWWWWW&W'WWWWWstatementsEWstatuseWuWWstatussourcelinkWWstatustargetlinkWWstdev2WstickWstickwithreferencepointsVstructureWstyleWWsubWWsubclausedeletedVsubclause0W}WWsubmissionWsubsequentlyGWsuchWWWWWEWW WsufficientWWsuggested,W0WsuggestionWsummationWsuperceededWsuppliedWsupportWsupportedW WWsupportsWAWsupposeWswitchWswitchedWswitchingWsyntaxWtableWWWWW/WWWWWtechnologyW1WWWWWWtermFWWtermsWtextWWWW W,WWWWWWWtextwillbeupdatedappropriately VWJEFamolari, DavidFApproveGGeneral Interest^ Editorial_13`19c_[8.6] For extendibility of MIH, there is a need to allow defining experimental TLV type values.d501g5101j$21-07-0312-00-0000-extendibility.docwAgree 2007/11/3009/16/2007 10:24:17 EDTMarkedNoEFamolari, DavidFApproveGGeneral Interest^ Editorial_13`19c 2007/11/3009/16/2007 10:24:17 EDTMarkedNoEFamolari, DavidFApproveGGeneral Interest^ Technical_153`6c_[8.6] For extendibility of MIH, there is a need to allow defining experimental TLV type values.d501g5101j$21-07-0312-00-0000-extendibility.docwAgree 2007/11/3009/16/2007 10:24:17 EDTMarkedNoEFamolari, DavidFApproveGGeneral Interest^ Editorial_13`19crmally the protocol works (a response is sent/received only after receiving/sending a request), this option is not represented in the transaction state machines aboveLw Superceded 2007/11/14 WvcwellW]WkWlWmWWWWWWwereFWWwestWwfaWwgWWEWWW,W.W0W1W?WDWEW]WbWeWnWoWpWvW}WWWWWWwhatdoescurrentlinkidentifierrefertothesourceortarDVEVwhatdoesitmeanbytransparentinter-workingwithlegacyeVwhatdoesn8ii12meanVwhatdoesthatmeanbymihcommandindication/responseinfiVwhatdoesthisprimitivemaytriggermihusertoinitiatethpVwhatifasourcenodecannotreceiveanyanswerevenitsenVwhatisastackVwhatisexistingandwhatisnewisrelativetothedevelopmVwhatisthedifferencebetweenlink-upandlink-handover-comVwhatisthedifferencebetweenmihposandmihposnetworkeVwhatisthevalueaddedofannexjideallythissectionshou.VwhattypeofauthenticationisreferencedherethereisnosVUwcinteractWWinteraction>WAWWWinteractionsWWintercommunicateWinterefacesWWinterestWinterestedWWWinterfaceWWWWWWW@W[WWWWWW W WWW#W$WWWWWWWWWWWtion.'d6g4947ecific signalling). 2007/09/1708/24/2007 10:31:14 EDTYesEStephens, Adrian PF DisapproveGProducer^ Technical_174`22aB.1.1cA'"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in order of significance." I dont' think this is unambiguous. Does it mean that the lowest numbered such octet is first or last. Likewise references to "network byte order" later on have no normative definition.'d6g4947on have no normative definition.'d6g4947 2007/09/1708/24/2007 10:31:14 EDTYesFr E Jette, AlanF DisapproveGProducer^ Technical_124a7.4.24ccMIH_N2N_HO_Commit should also allow the option of requesting resource reservation at the HO target.d261g5341jMadd an option where MIH_N2N_HO_Commit can request reservation of HO resourcespSame as Cmt 351v/Please refer to contribution 21-07-0320-02-0000wAgreeyRef 351{l) none needed 2007/12/1909/14/2007 14:42:22 EDTYes E Jette, AlanF DisapproveGProducer^ Technical_105a7.4.19cKThe need and use of the MIH_Net_HO_Candidate_Query command are not defined.d260g5342j)remove MIH_Net_HO_Candidate_Query commandp commandpMarkedYes E Jette, AlanF DisapproveGProducer^ Technical_105a7.4.19cKThe need and use of the MIH_Net_HO_Candidate_Query command are not defined.d260g5342j)remove MIH_Net_HO_Candidate_Query commandpsagree 2007/11/1809/14/2007 16:50:16 EDTMarkedYesE Jette, AlanF DisapproveGProducer^ Technical_203`9R:#VjparametersWWW5WUW]WkWlWmWW2W3WQWoWWWpartW WW5WWWWpartially7WparticipantsWparticularWiWkWlWmWpartnership:Wparts%Wpast WpathWpdcp;WpdfWpdp W0Wpdu W WpeerWWBWdWWWWpeers+WpendingIWperW W&WIWWper-ieWWper-messageWWper-premitiveWWperhapsGWperiodWaWWWperiodicWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWoWCjidWWWWWW1W=WJWwW}WWW7WvWWWidentifiedWWWidentifierWW4WDWEWKWLWMWNWeW|WWWWW(WifWWWWWW WWW&W'W-W.W4W7Wiis7WimplementWimplementedW&Wimplementing Wimplementor W'Wimportant2WinWWWWWWWWWWWWWWWWWWWWWWW WWWWWW%W&W'W)W+W0W1W4W7W;W<WJWinbothline38and37changedefaultvalueformime-typefroVinchapter8.6.4.2mihgetinformationresponsechangethetVinmostcasesthemobilenodeiscapableofsupportingmultiVinthecaseofremotediscoverythisprimitivemaycontaintVincludeWWJW)ccommandsW]WwWWWWWcommasWcommentWWFWSWWWWWWcommentsWJWWWWWcommitWWWWWWJWeWrWsWtWuWwW~WWWWWW W[WbWeWfWWWWcommonWWWWcommonlyWcommunicateWcommunicationWWWWWW"WcWWcommunicationreferencepointihaveaproblemusingtheterVWcontrolWcorrectWWWcorrespondinglyWcosWcosisnotincludedinlistofabbreviationsVcouldWcountWcounterWcounterpartWcountersWcriticalWWcuriouslyWcurrentWcurrentlyWdataWWWWWWWWWWdatatypeWdatatype1Wdatatype2WdcdWdecidesWdecisionWWWuS?ELach, Hong-YonF DisapproveGProducer^ Technical_14`40cASub-clause 5.2.1: It is contradictory to state that "MIHF may do further processing on link layer triggers and other events" while also stating that "the definition of such processing is outside the scope of the standard. MIHF shall specify what it does (and processes).d463g5139jDelete "MIHF may do further processing on link layer triggers and other events. The definition of such processing is outside the scope of the stanndard."wAgree{k) done 2007/12/1909/16/2007 06:10:15 EDTYesscesses).d463g5139jDelete "MIHF may do further processing on link layer triggers and other events. The definition of such processing is outside the scope of the stanndard."wAgree{k) done 2007/11/1809/16/2007 06:10:15 EDTMarkedYesanF DisapproveGProducer^ Editorial_10`7a4cAcronym for 3GPP spelled wrongd468g5134ontained already at the end of s bcandthismessageistransmittedovercontrolplaneusingl2Vand/orWrWsWWWW%W.W5W9WannexjdoesnotaddvaluetothefinalspecVannexes%WanotherWW W WWanyWWWWWWWWW WWW/W5WanywhereWapWappear!W[WappearanceWappears=WFWbWnWoWapplicableWWJWapplicationWappliedWappliesW0WapplyWW W'W1Wappreciated<WappropriateWWWWappropriatelyWapproximatelyWarbitraryWareWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW$W&W.W4W<WJWKWLWMWNWeWkWlWmWqWarq WarreW9cnoinforesponsebinarylisttlvintablec2VnomobilitymanagementlineitemorcodingxVnonormativereferencesarelistedVnooctetisencodedforthisdatatypethisdatatypeisuseVnoreferencesareprovideddespitethefactthatthisstandaVnodeWWW W+WWWWWWWWWNWWWWWWWWWWW W Wnode'sWWnodesWWWWnonWWWnonexistingprimitiveVnoneMWWnonexistentWnorWWnormalizedWnormativeWWWWWWW WW%W8WWWWWWWWW/WWWWWWW W -cA,ACK failure is not related to PLR. ACK failure is a transmit side metric equivalent to packet not received or packet received with error. Packets with failed ACK are simply retransmitted. Many 802.11 links exhibit finite PER with zero PLR. This show the author's limited understanding of these terms.,d635g4967j*Delete or rewrite this erroneous equation.vAThis formula is provided as a way for the sender to infer that a packet is lost at the receiver by considering the ACK failure. Not clear what is meant by the comments Many 802.11 links exhibit finite PER with zero PLR Note that PER is a theoretical valuewDisagree{l) none needed 2007/12/1909/16/2007 23:32:08 EDTYes EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_287`21aK7`21aKal Interest^ Technical_289`4aKc`4aKc 2007/09/1708/24/2007 10:31:14 EDTYesEStephens, Adrian PGProducerd2g4951 2007/09/1708/24/2007 10:31:14 EDT`E Sood, KapilF DisapproveGGeneral Interest^ Technical_12`1a5cAIClause 5 is supposed to be general 802.21 architecture description. However, in multiple locations in this clause, there are references to more specific events in this specification, while there are other sentences that are too generic. Eg. Generic description of handovers in 5.1.2, generic QoS descriptions in 5.1.4, and so on.Id269 802.21 functions and design.v$by comment 35. Paragraph is deleted.w Principley Ref Cmt 35 2007/11/2609/14/2007 16:50:16 EDTMarkedYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_12`1a5cAIClause 5 is supposed to be general 802.21 architecture description. However, in multiple locations in this clause, there are references to more specific events in this specification, while there are other sentences that are too generic. Eg. Generic description of handovers in 5.1.2, generic QoS descriptions in 5.1.4, and so on.Id269GEKarocki, PiotrFApproveGGeneral Interest^ Editorial_25`1a2cIf there is no references, please change clause text to "There is no cited references". Now it looks like references are missing.d254g5348padded text "[to be identified and added]" for now. If in the final version there is still no normative reference identified, will state so.{k) done 2007/12/1909/14/2007 09:37:45 EDTNoEJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_15`46a5.1.8cAThis talks only about wireless power management. Work is under way in 802.3 to define power management features that will interact with the MAC operation - e.g., by changing data rates - what is the relationship between the .21 work and these kinds of features in wired LANs?d253g5349jShow the relationship.ationship.rates - what is the relationship between the .21 work and these kinds of features in wired LANs?d253g5349jShow the relationship.standardwAgreelV{lWWWWWWWWWWWWWWW W W W WWWWWWWWWWW W!W"W#W$W&W(W)W*W+W,W5W8WmWpWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWlnoneneededVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV007 18:36:55 EDTMarkedYesE Julka, VibhorF DisapproveGProducer^ Technical_146`65a8.2.2.2cSEHeubaum, Karl FFApproveGProducer^ Editorial_198`13aB.2.9cR"if a container is listed..." should be capitalized to match the other list items.d70g5532j'Change to "If a container is listed..."{k) done 2007/12/1909/11/2007 12:01:48 EDTNoEHeubaum, Karl FFApproveGProducer^ Editorial_164`50a8.2.2cMInsert "The" before "Following conventions are used..." (not proper English).d69g5533j.Change "The following conventions are used..."wAgree{k) done 2007/12/1909/11/2007 11:59:47 EDTNo EHeubaum, Karl FFApproveGProducer^ Editorial_71`14a7.3.9.1cCThere's a period missing at the end of "...for various parameters".d68g5534j&Change to "...for various parameters."p done in 136wAgree{k) done 2007/12/1909/11/2007 11:58:02 EDTNo EHeubaum, Karl FFApproveGProducer^ Editorial_67`65a7.3.5.1a7.3.5.1a7.3.5.1a7.3.5.1 cA[1.5.1]Sentence too complicated and unclear: "The IEEE 802.21 standard defines the information that helps in network discovery and specifies the means by which such information may be obtained for supported access networks and be made available to the MIH Users."d500g5102j'Remove "for supported access networks".{k) done 2007/12/1909/16/2007 10:24:17 EDTNoE Cheng, HongF DisapproveGProducer^General_15`62a5c"The destination of an event is established dynamically.."? Does it mean every time, an event is generated, the destination needs to be constructed by the MIH?d499g5103jOChange the text to clearly specify how the destaination of event is identified.vDelete the word "dynamically"wAgree{k) done 2007/12/1909/16/2007 08:19:02 EDTYesE Cheng, HongF DisapproveGProducer^General_15`62a5cWhat is a "stack"?d498g5104498g5104498g5104%3vpicoWWpics&W'WWWWWplacedWplacementWplacesW WWplanesWpleaseWWWWWWWWWW W6WVW\W^WkWlWmWtWWWWWWWWWWWWW W W@WMWWWWWWWWWWWWpleaselookatcontribution21-07-0302-00-0000Vpleasemakechangesaspercontribution21-07-0414-02-0000-3Vpleasereferto21-07-0191-00-0000VVpleasereferto21-07-0308-01VVpleaserefertocontribution21-07-0302-01-0000-sVVVVVVVVVVVpleaserefertocontribution21-07-0317-01-0000-sinformatioVpleaserefertocontribution21-07-0320-02-0000 Vpleaserefertocontribution21-07-0320-02-0000-rdefinitionVVVVpleaserefertocontribution21-07-0373-01-0000@V. cAThe 802.21 spec seems to do a good job of defining a mechanism for collecting media dependant data from diverse media and provides the opportunity for Media Independent processing of these data for Media Independent Handover. However, most of the media independent parts seem to be missing. The MIH events defined seem to be media independent, yet the media dependant standard definitions for each media independent event are not included in the standard. For instance the "Link Going Down" seeBms to be a media independent event (common term) which must have a standardized definition in media dependent terms (native terms) for the 802.21 standard to operate. For instance if "Link Going Down" is defined as PER < 10E-3 for 802.16 and is defined as "recently disassociated" in 802.11, we have a problem in that the MIH event in 802.11 is not an equivalent event in 802.16. This spec refers to ammendments needed in the various media to support MIH, yet when I looked into the referenced %MEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2 layer 2 connection is established on the specified link interface. However, the primitive includes the MAC addresses of the access router, IPRenewal flag and Mobility Management Support. The latter two parameters are clearly above L2 and the L2 link up may not even know about them. The term access router is not defined, but if it is the default gateway (router), then the L2 link up indication would not know about it either.d91g5511jDefine the link up primitive such that it is a L2 primitive that only includes L2 parameters or as an L3 primitive with L3 parameters (ie., provide layer separation).vaThese two parameters are optional and links which dont support these parameters can ignore these.wDisagree 2007/12/0109/11/2007 17:46:47 EDTMarkedYesEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2trFApproveGGeneral Interest^ Editorial_27`55a3.29qvrequestWW0WEWfWiWkWtWwWWWWWWIWWWrequest/indicationWrequire/W2WWrequiredWWW,W0W2W]WwWWW W WWWWWWrequirementsWWWWrequiresWreservatonWWreserved/W2W3WAWresidesAWresiltsWresolutionW\WWresolvedWresolvedinothercommentscmt427VWWresourceretentionreqWresourceretentionstaWresourcesWkWlWmW W WWWrespect WrespectiveW5WWrespondW WresponseWW<WEWuWwWWWJWresponse/confirmWresulteWvWretentionWretractedWretransmission{W Wretransmissions Wretransmit Wretransmitted WreturnWWreturns^Wrev2WrevisionW/WAWWPj}Investigate how to re-organize the data type definitions, either on a per-premitive, and/or per-message, and/or per-IE basis?pduplicate with 118{l) none needed 2007/12/1909/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Technical_150`60a8.4.1cSMIH Protocol header is of fixed length, as indicated in Figure 27 on the next page.d353g5249jKcorrect figure 26 to show MIH Protocol Header has fixed length of 8 octets.psuperceeded by comment #454wAgree{k) done 2007/12/1909/15/2007 22:08:13 EDTYes E Xie, QiaobingF DisapproveGUser^General_144a8.2.2cAGMIH protocol transaction state diagrams only have significance when the MIH level ACK mechanism is used. Otherwise, it is not really necessary since MIH protocol is mostly a transaction-oriented protocol without the ACK. Since MIH level ACK is optional to use, it may be better to move the state diagram discussion to an annex.Gd352Gd352Gd352E Xie, QiaobingF DisapproveGUser^ Editorial_36`48a6.3.1crepeated statementd345g5257jZdelete "MIH events may be local or remote. Remote MIH events originate at a remote MIHF. "pSame as Cmt 109{k) done 2007/12/1909/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^General_36`20a6.3.1c_Figure 13 is confusing by showing two unrelated stacks. Showing one stack would be good enough.d344g5258joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.wAgree{k) done 2007/12/1909/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^General_33a6.2cThe concept and procedures for MIHF discovery are not specified in this spec (i.e., no mandatory messages/flows defined for MIHF discovery). This is the right way to do it. Just the text and title in 6.2.3 and 8.2.3.5 may mislead readers otherwise.d343g525943g5259343g5259obingF Disapprove.^technicalȃɃ̃̓΃уՃփ׃ۃ܃  &',-/01245678=>?@ABCDEFGHIJKLMNOPQRSUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃⋃⌃⍃⎃⏃␃Ⓝ┃⡃⢃⣃⤃⦃⧃⨃⫃⭃⯃ⲃ⸃⹃⻃⼃⽃⾃⿃ƒÃăŃƃǃȃʃ˃̓΃σЃ҃ӃԃՃփ׃؃كۃ܃݃ރ߃EKarocki, PiotrFApproveGGeneral Interest^ Editorial_27`55a3.29cAdd abreviation:d255g5347j'... mobile node (MN): Communication ...{k) done 2007/12/1909/14/2007 09:54:24 EDTNooEKarocki, PiotrFApproveGGeneral Interest^ Editorial_27`55a3.29cAdd abreviation:d255g5347j'... mobile node (MN): Communication ...{k) done 2007/11/1809/14/2007 09:54:24 EDTMarkedNog5020jACTION_EXECUTION_TIME from NET*wDisagreey deferred. 2007/11/1809/16/2007 16:08:43 EDTYeschael GF DisapproveGProducer^ Technical_121cOn messages MIH_MN_HO_Commit.request and MIH_MN_HO_Commit.indication (7.4.23 and 7.4.23.2) and also in MIH_Net_HO_Commit request (8.6.3.15), there is undefinde type LINK_ACTIONSd581g5021jShould be LINK_ACTIONv$change LINK_ACTIONS to "LINK_ACTION"wAgree 2007/10/0709/16/2007 16:08:43 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ EditorialzOEMyles, Andrew FF DisapproveGProducer^ Technical_69`25a7.3.6.3cnk" has been detected for use. The term "type of link" has not been defined and thus the text is unclear. Does "type of link" mean a link to a different network, another PoA in the current network, or something else? Hopefully it's referring to a link in a different network. If it's referring to another PoA in the current network, then the Link_Detected event will be sent to the higher layers constantly (e.g., whenever a neBJw AP is detected in a WLAN). This does not help inter-technology handover.8d94g5508jClarify the text.pChange "Link_Detected indicates that a new type of link has been detected for use." to "Link_Detected indicates the presence of a new PoA."v*Use clarifying text from TGu mapping draftwDisagree{k) done 2007/12/0709/11/2007 17:46:47 EDTMarkedYes EMyles, Andrew FF DisapproveGProducer^ Technical_69`25a7.3.6.3cg5508jClarify the text.=jAdd the following sentence in Annex B: "This Annex defines data types used in the IEEE 802.21 standard. Any variable-length data type in this specification contains information needed for determining the end of data."wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes >EOhba, YoshihiroF DisapproveGProducer^ Technical_165`59a8.6.3.14cQIPAddressInformationStatus should be optional as other IP related attributes are.d208g5394j(Mark IPAddressInformationStatus optionalpsuperceeded by comment #207wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes ?EOhba, YoshihiroF DisapproveGProducer^ Technical_164`36a8.6.3.12clIPConfigurationMethods and IPAddressInformationStatus should be optional as other IP related attributes are.d207g5395jCMark IPConfigurationMethods and IPAddressInformationStatus optionalwAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes @EOhba, YoshihiroF Disapprove7}@1cj_h@@jp@j@e@Y@Y@Y@e@Y@YY@@|^pAnnex B. This is a problem because QOS_LIST is a sequence, and if it's in the choice, it means all of the emty structure needs to be in there. some refinement work may be needed.vAWithin LINK_PARAM_TYPE (pg 180, line 10) change QOS_LIST to LINK_PARAM_QOS_LIST then define LINK_PARAM_QOS_LIST as an enumeration as follows Type Name: LINK_PARAM_QOS_LIST Derived From: ENUMERATED Definition: a type to represent QOS_LIST parameters Valid Range: 0: QOS_LIST (returns QOS_LIST values as defined on pg. 186 line 26) Change LINK_PARAM to SEQUENCE(LINK_PARAM_TYPE, CHOICE(LINK_PARAM_VALUE, QOS_LIST)) (Vivek or Qiaobing: Please read the editor's note)w Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o g capabilities. The response, however, did not specify event and command as optional thus we are still left with the problems stated above.Dw Principle 2007/12/0109/16/2007 03:08:31 EDTMarkedNo^ERajkumar, AjayF 6rEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_175`5aB.1.1ce"No octet is encoded for this data type. This data type is used for to define an optional data type."d579g5023ja"No octet is encoded for this data type. This data type is used to define an optional data type."{k) done 2007/12/1909/16/2007 15:56:25 EDTYes EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_174`41aB.1.1cA"A one-octet Selector field, followed by a variable length Value field. The Selector value determines the data type. If Selector==i, (i+1)-th data type in the list of data types DATATYPE1,DATATYPE2,[,&] is selected. The Value field is encoded using the encoding rule for the selected data type." What is the binary encoding of the selector octet? Order ov value? Increasing order or decreasing order?d578g5024jg5024jchnical_174`41aB.1.1ceshat need to be addressed please clarify.wRejected 2007/10/07 EJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_5`8a2cAI cannot believe that a proposed standard such as this, which is intended to specify mechanisms across multiple other standards, has exactly NO normative references. This is laughable, and to me, simply demonstrates that the document is not ready for prime time. Apart from anything else, the standard appears to be trying to re-define the MAC service. Why is there no normative reference to the existing MAC service definition?GGeneral Interest^ Technical_5`8a2cAI cannot believe that a proposed standard such as this, which is intended to specify mechanisms across multiple other standards, has exactly NO normative references. This is laughable, and to me, simply demonstrates that the document is not ready for prime time. Apart from anything else, the standard appears to be trying to re-define the MAC service. Why is there no normative reference to the existing MAC service definition?V_Yes cF DisapproveGAcademic^ Technical_59`15a7.1cAwitems a) through e) contain a mapping of the MIH_LINK_SAP to media-dependent / technology specific SAPs. There are two issues with this. First, such a mapping of 802.21 functionality to a specific technology is very beneficial but should be included in a (possible normative) Annex. Second, such a mapping should be structured by "technology" and not by the name of the SAPs.wogies. "wAgree 2007/12/0109/10/2007 07:08:58 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_59`15a7.1cAwitems a) through e) contain a mapping of the MIH_LINK_SAP to media-dependent / technology specific SAPs. There are two issues with this. First, such a mapping of 802.21 functionality to a specific technology is very beneficial but should be included in a (possible normative) Annex. Second, such a mapping should be structured by "technology" and not by the name of the SAPs.wAvitWWWWWWWWkWWWWWWWWW WW W'WAWEWWWWWWWWWWW W Wit'sWWitemsWitheWitsW<WW'W WituWjanuaryWWjustWWWWWWWjustprovidingiprenewalflagisnotsufficientthismaybeVk5WWk0-1WkeepWWWWkeepitinmainbodysincethisisanoptionbutnotsomethiVkeepmihpos3.18VkeepthetargetpoaVkindEW(WknowWWknowsuWlWl1EWl13WWl14WWWllcWllcisspecificallyanieee802entityanditisvalidonlyVlocalwWlocally<WWlocated<WlongWlow-confidenceWlowerWWWlower-layerWmacW<WmadeWmainWmakefWuWWmanagement<WWWgefK@@cA(cA@9v8@@3@v>@c.@v<@j@Bc@j@@p]@@jAcA#vA@{j8@vA2cBl{r@IjvAcAv@KjAcAu @j` @N cAvBB cALKcBJD@cB=@6cA_@6@cA_@6cA_@6cA_@6cA_@66_@66@6cA_@6cA_@6@66@6@6@6Aj!suggest to move 8.2.2 to an annexpgroup disagrees with commentvJKeep it in main body since this is an option, but not something redundant.wDisagree{l) none needed 2007/12/1909/12/2007 02:37:36 EDTNo EEastwood, Lester FF DisapproveGProducer^ Technical_124a7.4.24cMIH_N2N_HO_Commit does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d115g5487jcadd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit.pSame as Cmt 351vCPlease refer to contribution 21-07-0320-02-0000-Resource_DefinitionwAgreeyRef 351{l) none needed 2007/12/1909/12/2007 02:37:36 EDTYesEEastwood, Lester FF DisapproveGProducer^General_87cMIH event subscription should allow the subscriber to set certain conditions or qualifiers. With that only events meet those conditions or qualifiers will be notified to the subscriber.d1148M pthemihfisalogicalentitywhosedefinitionisindependentVtheotherproposedieswillbedeferedtonextroundV is no interface defined to this technology, within the main part of the standard.d363g5239jjPossibly remove the reference to IEEE 802.15, as it is not specifically defined within this base standard.vremove 802.15 from Figure 1 and from page 4, line-14. Leave it on page 2 where it is used as an example to describe pico cellsw Principley Ref Cmt 363 2007/11/2609/16/2007 01:46:33 EDTMarkedYesEMccann, StephenF DisapproveGProducer^ Technical_2`33.15, as it is not specifically defined within this base standard.vremove 802.15 from Figure 1 and from page 4, line-14. Leave it on page 2 where it is used as an example to describe pico cellsw Principley Ref Cmt 363 2007/11/1809/16/2007 01:46:33 EDTMarkedYesEMccann, StephenF DisapproveGProducer^ Technical_2`334vdocumentWWWWWdoesWW/W2WWWWWWWdoingWWdon'twWdoneWWWWWW WdontIWWWdontneedonaperdirectionbasisIVWeffectuWelsewhereEWemergencyWemergencyservicesandotherapplicationsaswellmayrequirVenableWengine<WenhanceWenhancementsEWentireWentitiesWW}WentityWW<WWWWentityremovemobilitymanagementfromtheabovesentenceVentriesWWenumeraedaWenumeratedaWequipmentWesssWestablisheduWetcWevaluatedWevaluationWevent<WWevents<Wexample<WWWexceptWexchangeWexchangedWexclusiveAWexecutingiWexhibitWexistingWexpectedWexposed@WextensivelyWfailedeWfailureWWhandoversWWI|vatWWWWWWWWWWWWvWWWWWW'W8WW WatleastoneofthefollowingparametersshallbespecifiedVatthelinklayerthisoptionisnotvalid8VattachWWattachanexplicitstatementtoline29thatwhenmorethanVattachanexplicitstatementtoline49thatwhenmorethanVattachmentWGWattempt'W Wattempts'W Wauthentication WWavailabiilityWavailableWWWWWWWW5WkWlWmWWWW W W&W(WWWWWavoided,WbWbold/newaccessrouterofwaitingemailVb-10Wb-13W2WWb-4Wb-50Wb-9WbackWW W WWWWbasedWWkWW2W5W@WAWiWWWWWWWby471Vbycomment35VcWVp3'vsapsWWEWsayWWschema<WscopeWWWWsdo1WsecondWsection/W2W7WwWWW0WGWWsection5.1.7hasbeendeleted7VVsectionsEWseeWWseecmt556formoredetailsVselectorWsenderWsenseWWsentWWsentenceWW{W}WWseparateWsequenceaWservice@WAWWWWWservicesWWshallWWWWshould,WwWWEWshownWshowsWsidewWsignalingWsimilarly2WsinceuWWsingle2WsmaeGWsmaeascomment432GVsowWsomethingWsourcelinkactionsWsourcelinkidentifierWspecWspecifcWspecificWWWW1WWEWWspecificallyWspecification,WAWWspecifications,WspecifiedW2WW}WspecifiesWspeedW2vthroughoutWWWWWthroughputWWthroughputisdefinedastheinstantaneousbitrateienumbVthroughputisintendedtoreflecttheinstantaneousbitrateVthusuWtimeWWWWWGWtime-intervalWWWtimer{WtitleEWtlvWtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WW,W/W0W1W2W5W6W<W@WOWVWWW\W^WaWeWfWiWkWlmuWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWW W(W+W0W@WAWEWGWQRpmlmeWmnOWxWWWWW WWmnhocommitindicationisgoneVmnhocommitislocalonlynowxVmobileWmodificationsWmodifiedW(Wmodifiedfig11tobemoreconsistentwithtextVmodifyWmonitorWmonitorsWmoreWWWWmoveWWmscgfWWWn2nOWnWoW WnameWnas-port-type3WnecessarilyWneedWWVWWWWneedtobedefinedinannexbVVVVVVVVVVVVVVVVbVVVVannexbVVVVxbVVVVVVY ME Feder, PeretzF DisapproveGProducer^ Technical_131`2cA The description of the "Source Link Identifier" and "Target Link Identifier is confusing. For the case where the MN_HO_Complete message is sent to the new target PoS then source and target link identifier are one and the same (At least according to the description). d449g5153jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p7Remove the intended, since it is HO_Complete primitive.wAgree{k) donethe same (At least according to the description). d449g5153jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p7Remove the intended, since it is HO_Complete primitive.wAgree{k) doneQ MvsapsapdescriptionsaremovedtoannexlwhichalsohasmappingV*3EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_3`47a1.4c"The mobile node is capable of supporting multiple link-layer technologies, which may be wireless or wired." This assumption isn't absolute: handovers between 802.11 ESSs would use 802.21 but be limited to a single link layer technology.d546g5056j"In most cases, the mobile node is capable of supporting multiple link-layer technologies, which may be wireless or wired. However it is possible that the mobile node supports only a single link layer technology, such as 802.11 ESS handovers."vA{kOWPWQWRWSWTWVWXWYWZW^W`WaWbWcWdWeWfWgWhWiWjWkWmWnWoWpWrWsWtWuWwWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW%W'W-W.W0W1W2W3W4W6W7W9W:W;W<W=W>W?W@WAWBWCWDWEWFWGWHWIWJWKWLWMWNWOWPW €yes  !"#$&'025678<=>?@ABCDEFGHIJKLMNUVWXYZ⡃⢃⣃⤃⥃⨃⩃⪃⫃⭃⯃Ⰳⲃⳃⶃ⸃⹃⻃⼃⽃⾃⿃ƒÃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  !"#$&'()*+,.12456789;<=>?@ABCDEFIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Uw"EGiesberts, Pieter-PaulF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d236g5366jsremove the stack marked as "Remote Entity" and remove the text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1909/14/2007 03:15:28 EDTYes ter-PaulF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d236g5366jsremove the stack marked as "Remote Entity" and remove the text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1409/14/2007 03:15:28 EDTYes roveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d236g5366jsremove the stack marked as "Remote Entity" and remove the text "Local Entity" from the stack on the left-hand side.w Superceded{l) none needed 2007/12/01?@ELach, Hong-YonF DisapproveGProducer^ Technical_14`20cSub-clause 5.2.1: It is both unnecessary and inexact to emphasise that MIHF "offers a unified interface" to MIH users. This is technically misleading.d462g5140tion of such processing is outside the scope of the standard. MIHF shall specify what it does (and processes).d463g5139jDelete "MIHF may do further processing on link layer triggers and other events. The definition of such processing is outside the scope of the stanndard."wAgree 2007/11/1809/16/2007 06:10:15 EDTMarkedYes@ELach, Hong-YonF DisapproveGProducer^ Technical_14`20cSub-clause 5.2.1: It is both unnecessary and inexact to emphasise that MIHF "offers a unified interface" to MIH users. This is technically misleading.d462g5140Yes@ELach, Hong-YonF DisapproveGProducer^ Technical_14`20 and a service user at a SAP.d464g5138sapprovea gebb disapprovecaecjRemove the sentence.vADelete: "The specification of how the MIHF interfaces with the lower layers generally does not fall within the scope of this standard. Such functionality may already be specified as service access points (SAPs) within the standards that pertain to the respective link-layer technologies, such as IEEE 802.1, IEEE 802.3, IEEE 802.11, IEEE 802.16, 3GPP, and 3GPP2. This standard may contain recommendations to amend the existing access technology specific standards when modifications of the lowB3er-layer interfaces may enable or enhance the MIHF"!wAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_13`49a5.1.8cThe IEEE 802.21 information reduces the scanning required to discover and handover to another network. However it does not eliminate the need for the MN to scan prior to handing over to the network. It minimizes scanning, not eliminates it.d301g5301e;E Sood, KapilF DisapproveGGeneral Interest^ Technical_6`28a3.6cA"3.6 home network: Network managed by the operator with whom the subscriber has a business relationship (subscription)" - This is at adds with the conventional definition of a "home network" where the prime attributes are ease-of-usablity, lack-of-IT dept., one/two network nodes, etc.d267g5335jZRaname "Home Network" to "Home Subscriber Network" in this clause and throughout the draftTMarkedYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_6`28a3.6cA"3.6 home network: Network managed by the operator with whom the subscriber has a business relationship (subscription)" - This is at adds with the conventional definition of a "home network" where the prime attributes are ease-of-usablity, lack-of-IT dept., one/two network nodes, etc.d267g5335jZRaname "Home Network" to "Home Subscriber Network" in this clause and throughout the draftRMvcalculate{WcanWW4W5WOWWWvWwWWW'WGWWWWWWWWWW WcanbeaddedlaterifdefinitionisavailableVVVcandidateWiWkWWcandidatelinklistIWcandidatesOWcandiddateW W WGWWWcannotW&W'WWWWWWWWcapabilitiesWcapabilityWWfWWWcapacityWcapturedW W WWWcareWcarefully WWcarried WcarrierW2Wcarry WcaseWWWWWWWW Wcases+W,WWW WcategoryWWcause&W'WWWWWcell-idWgethetitleofthisannextomediaspecificmappingforEVchangethetypetolinkaddressVchangethissentenceasfollowsVchangethresholdcrossingdirectiontoenumeraedtypeaboveaVA SvdefineddefiningWWdefinitionWWWWW/W0W1W2W3W^WWWWWWWWWdelayWWdeleteWWWWWWW@WWWYWaWWWWW6WEWFWWWWdelete3.43Vdelete5.1.9Vdeletefromthatperspectivemihfoffersaunifiedinterface@Vdeletemihposnetworkentity3.19VdeletenetworksecurityVdeletenetworksecurityieVVVdeletesection5.1.7Vdeletesection6.5.6.2rdfschemapropoganda6Vdeletesectionsl1andl2fromthisannexEVdeletethereferenceYVdeletetheroamingpartnersWVdeletethestatementVVVdeletetheworddynamicallyVdeletethistermsapFVdeleteddeliveringWdepend}WdependentWdependingW Wdepends}Wdependson407mnhocommit'sactionsdependonlocalnodeo}VV{evcommenterWcommentsWWW/WWcommitWWWtWuWwWxWyWWW W WWWcommit's}Wcommunicate}WcompleteWWEWeWwWcompletedeWvWcompletion/commitmenwWcomputationWWWcomputedWconceptualAWconditions5WWconfidenceWWWconfigWWOWWWconfigurationOWWconfirmwWWWconformance&W'WWWWWconnectionWWWconnections0WconnectivityWWW0WuWconservationWconsiderW+W,WW WconsiderationsWconsideringWconsistentfWWuldW/W2WWcoverageWWcpc/Wcpich2WcrossedaWcrossingaWcsWcurrent0W5WWWWd7.1WdataW0W<WWdealWdealsWdecideWdecision<WT Dvthatthat'sWWtheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW&W'W,W/W0W1W2W3W5W<W@WAWEWOWWWYW]W^WeWfWiWkWlWmWtWuWvWwWWWWWWWWWWWWWWWWWWWWWWWWthetypeieroamingpartnerstypeieroamingpartnerWVtheirWthenGWWtheoreticalWthereWWWWWthereisnopointindoingthestandardifitisonlyadesiVthereforeWthese<WWWWthesetermsaredefinedinieeedisctionaryVtheyWGWWthisWWWWW@WiWuWwWWWWWW8WGj_23`34a5.5.1cAPlease clarify the relationship between the MIH_LINK_SAP and its primitives and actual SAPs like LSAP, MLME_SAP, CS_AP, C_SAP, M_SAP and their primitives. For an example, MIH_LINK_SAP specifies Link_Get_parameters primitive. Which primitive can be mapped to that Link_Get_parameters primitive from the actual SAPs like LSAP, MLME_SAP, CS_AP, C_SAP, M_SAP? Same question applies for all the primitives defined on MIH_LINK_SAP.d241g5361jPlease specify the relationship between the MIH_LINK_SAP and its primitives and actual SAPs like LSAP, MLME_SAP, CS_AP, C_SAP, M_SAP and their primitives.vZSAP descriptions are moved to Annex L which also has mapping between different primitives.wAgree{l) none needed 2007/12/1909/14/2007 03:17:04 EDTNoE Jee, JunghoonF DisapproveGProducer^ Technical_59`1a79`1a7cal_23`34a5.5.1c=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6|σ^|߃_|`|_vieeeWW,W<WWWWWWWWWWiesWWWietf{WifWWWWWWWWuWvWWWW W WWWWWWW WiftheaboveexplanationistrueitneedstobecapturedandV V VVVignoreWillustrativeWimminentWimplementation&W'W]WW'WWWWW WimplementationsAWimportantWW2WinWWWWWWWWWWWWWWWWWWWWWWWWW WWWW W&W'W/W1W2W5W<WAWOWWW]WiWlWmWwWWWWWWWWWWWWWW WWWW W&W'W@WEWGWIWJW:ƒ disapprove:ƒ[vdocument@down@effect@envisage@vevaluated@#fall@figures@5follows@_from^pget@|handoversieee@in{includinginfoinformation@interfaces@Ait@l15@line@Clisted@`managementmappingEzmechanisms@Emihy#mihf@Zmodify1need2I needs@newnormativeofPon3other@page%pico@picspleaserefertocontribution21-07-0375@plesaereferto21-07-0396-01-0000@plural@jpoamprimarily@provided@Xreason@references@\refersrel-5@representqc principle/ydeferred@deferredrefcmt497@)deferredseecmt497@oref@Q{off@-€marked€noyes@ KcA The description of the "Source Link Identifier" and "Target Link Identifier is confusing. For the case where the MN_HO_Complete message is sent to the new target PoS then source and target link identifier are one and the same (At least according to the description). d451g5151jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p7Remove the intended, since it is HO_Complete primitive.wAgree{k) done 2007/12/1909/16/2007 03:38:14 EDTYes s _Complete.=v wDisagree 2007/12/0709/16/2007 03:38:14 EDTMarkedYes KE Feder, PeretzF DisapproveGProducer^ Technical_132`47chnical_132`47cich is incorrect as both sides may generate the same transaction ID.d453g5149#5uvfallWWfdd/W2W3WfeatureW@Wfeatures/WfeelsWfieldWAWfieldsWfigureWWWWWWWWWW Wfigure1showstheplacementofthemihfwithinthemobilityVfigure3isjustanillustrativeexampleandit'squitediffVfigure8isan802.16sapdiagramVWWWWWW<WeWWEWWWWfortableb-13foraspecificrevisiontypeanddefineavenVformulaWWframesWfromWWW2W<W@WiWWWWEWWWfunctionWfunctionalitywWWfunctionsW}Wg0W1W2W<WuWWgenerallyWgetWgoWgoalWgoingWgprs2WgroupWgroup's,Wgsm2Wgsm/gprs3WhandleWhandoverWeWuWwWWhandoversW<WeWW`zvmanagementmanagerWmandatory5WWmannerWWWmanualWWmanyWmappedWWmappingWW5WWntWmechanismsWmediEWmediaEWmeetWmentionedEWmessageiWWWmessagesfWwWW}WmihWWWWWW@WfWiWwWWWW}WWWWmihfunctionsisusedinthepluralsenseofmihfunctionVmihfW<W@WiWWWWWmissingWmniWuWwWWW}WWWmnhocommitshouldbeusedonlyasalocalprimitiveandnowVmobileiWmobility<WWmodificationsWmoreWWWWmuchWmultipleWWmultipletypeielistedWVnamewWneedWWWwWWGWWneedmoretextVneedtochangethisacrossthedraftVneedtohavemorespecificinputsastowhatrequirementsarV@{@x@@.@9v?@ac@@j@PjgjZ@{j@{&@@j@[d@cO@@{yc8@P@#@vdGo@cAb^@@@@@@@@@@@@cAlAl3cAll3cAlcAl3cAl@j3cAlsFƒheubaumkarlf approveƒapprove 5ƒkiernanbriang approveƒ disapprove%@ƒemmelmannmarc disapproveƒ disapprove5ƒemmelmannmarc҃ disapproveƒ disapprove=Qƒt€@v802.21WWWWWWWWWWW802.21dealwithnetworksthatdonotfallwithinthescopeV802.21helpsinpowerconservationonmobiledevicesbyprovVWWWWWWWWW2W<W@WAWIWWWaWeWiWwWWWWWWWWWW(WWWW W WableWaboutWWaboveaWWWabstractWabstractionAWacceptWaccept21-07-0321-00-0000VaccessWWWWWWWWWWaccessibleuWaccomplishedwWaccount<WeWaccuratelyWackWack-req W WacknowledgementWW Wacknowledgment WacronymGWacronyms/W2WGWacrossWWWactionWW WactionsW0WuWWadaptionWaddWWrofcosVaddegatthestartingofnextlineVE&vdNo contribution available. This is not very different than some of the other flow diagrams in draft.wDisagree{l) none needed 2007/12/1909/14/2007 02:24:47 EDTYes 'E Koh, BenjaminF DisapproveGProducer^General_143a8.2.1cThere seems to be arbitrary decisions made regarding the MIH Protocol Acknowledgement operation. For example, why re-transmit only 2 times? Such variables are usually expressed in a MIB. What about the possibility of aggregated Ack messages?d231g5371jRestrict description of MIH Acknowledgement operation to the messages exchange. Implementation details should be left out or else in the Annexpsuperceded by comment #2vmprehensive mapping between 802.21 and 3GPP parametersd278g5324jReplace the column that provides the mapping between 802.21 and 3GPP technologies by a different table as defined in 21-07/321r0 a MIH_Link_Configure_Threshold specified both for SAP primitives (in section 7) and NIH messages in section 8.d280 EE Feder, PeretzF DisapproveGProducer^ Technical_128`57cqWhat does "current link identifier" refer to, the source or target link identifier (as specified in the request)?d457g5145jEither change "Current Link Identifier to "Source Link Identifier" or to "Target Link Identifier". Alternatively, remove "Current Link Identifier" and add both source and target link identifiers.pKind of funny though.14 EDTMarkedYes EE Feder, PeretzF DisapproveGProducer^ Technical_128`57cqWhat does "current link identifier" refer to, the source or target link identifier (as specified in the request)?d457g5145jEither change "Current Link Identifier to "Source Link Identifier" or to "Target Link Identifier". Alternatively, remove "Current Link Identifier" and add both source and target link identifiers.pKind of funny though.RTECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_208`48aDc.(Kenichi) cardinality should be minCardinalityd442g5160jreplace 1 with 1{k) done 2007/12/1909/16/2007 03:35:02 EDTNo UECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_193`27aB.2.8c+(Kenichi) SYSTEM_PARAMETERS is not defined.d441g5161j.Define SYSTEM_PARAMETERS. (21-07-0317-01-0000)v21-07-0317-01-0000wAgreeyRef 339{l) none needed 2007/12/1909/16/2007 03:35:02 EDTYesVECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_48`41a6.5.3c5(Kenichi) SUPPORTED_LCP is not defined as a datatype.d440g5162jDefine SUPPORTED_LCP.p- need to be defined in annex Bv"Please refer to 21-07-0191-00-0000wAgree{k) done 2007/12/1909/16/2007 03:35:02 EDTYes WECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_48`15a6.5.3cC(Kenichi) TYPE_IE_ROAMING_PARTNERS should be single ROAMING_PARTNERd439EHenderson, Gregory SF DisapproveGProducer^General_196`24a Table B14cANETWORK_TYPE_INCLUSION does not include values for 3GPP and 3GPP2d644g4958j$Define values for these two networksvu3GPP and 3GPP2 networks have been included in the table. Commenter to come back with any specific inputs if required.wDisagree{l) none needed 2007/12/1909/16/2007 23:51:48 EDTYesEHenderson, Gregory SF DisapproveGProducer^ Technical_196`8a Table B14cVNETWORK_TYPE_INCLUSION valid range data does not match same data in Tale B13 line 8-26d643g4959jCorrect table B14 to match B13p_An optional TYPE_EXTENSION field is added to table B-12 (under NETWORK_TYPE) for this purpose. vFor table B-13. For a specific Revision Type and define a Technology Standard specific field which could have feature specifc values. Please refer to contribution 21-07-0422-00-00000w Principle{k) done 2007/12/1909/16/2007 23:51:48 EDTYes referenced ;EOhba, YoshihiroF DisapproveGProducer^ Technical_198`43aB.2.9c)The default MIME_TYPE value is incorrect.d211g5391j|Change the second sentence of Definition column to: "If MIME_TYPE is omitted, MIME type "application/sparql-query" is used."wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes TYPE_IE_ROAMING_PARTNER ROAMING_PARTNERS -> OPERATOR_ID - p50 L22 Figure 19: The TYPE_IE_ROAMING_PARTNERS -> TYPE_IE_ROAMING_PARTNER and add additional "..." in a way to identify there can be multiple TYPE_IE listed. -p52 L62 Roaming Partners IE -> Roaming Partner IE and add additiona "..." to identify there can be multiple entries. - p192 L13 Delete the ROAMING_PARTNERS - p201 LB714 Bit 8: TYPE_IE_ROAMING_PARTNER (remove S). %w Principle{i) to do 2007/11/2909/16/2007 03:35:02 EDTMarked- p192 L13 Delete the ROAMING_PARTNERS - p201 LB714 Bit 8: TYPE_IE_ROAMING_PARTNER (remove S). %w Principle{i) to do 2007/11/2609/16/2007 03:35:02 EDTMarked  vAThe name of these Net_HO commands need to change. " The Network controller provides a list of candiddate network choices to MN. The MN indicates resources required on each of these candiddate networks. The Network controller then queries each of the candiddate networks for available resources and reports this information back to the MN. Thereafter the Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagreeyRef 260{l) none needed 2007/12/1909/14/2007 03:15:28 EDTYes !EGiesberts, Pieter-PaulF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d237g5365jsremove the stack marked as "Remote Entity" and remove the text "Local Entity" from the stack on the left-hand side.wAgreeyRef 347. (duplicated){l) none needed 2007/12/1909/14/2007 03:15:28 EDTYesYesm pAUpdated subclause 7, need to update 8 and annex 1. and TLV assignments. Note that the contribution was not directly applied. Modifications are: - include complete MIH event list in MIH_EVENT_ID - move the outer CHOICE from EVENT_CONFIGURATION_INFO to allow choice of the parameters. - remove the LINK_TYPE from the LINK_DETECT_CONFIG since the link type is already present in the subscription primitive. - Table C-2 assignment only need the Event Configuration Info List.vAAdopt contribution 21-07-0305-02-0000-Event-Subscribe-Update.doc with the following change: remove the LINK_TYPE from LINK_DETECT_CONFIG, since the Link Identifier parameter already provided the link type. Adopt contribution 21-07-0306-02-0000-Link-Detection-Update.doc with the following change: replace LINK_TYPE with LINK_TUPLE_ID for the LINK_DETECT_INFO, since the Link identifier is required at the MIH level in order for the MIH user to know which link it was reported from; the change i6ƒ>b 2007/12/1909/16/2007 03:08:31 EDTNo o ears to indicate that a Link Detect event is posted whenever a PoA is detected and has not already been posted in a previous Link Detect event. This is different that what was specified on page 40, lines 21-24.d428g5174 BELOW_THRESHOLD). Add REPORT_REASON enumerated type (PERIODIC, ABOVE_THRESHOLD_, BELOW_THRESHOLD) as well LINK_PARAM_REPORT will be a sequence of LINK_PARAM and REPORT_REASON. Delete on page 181, line 52 ".....when no threshold value has been crossed"Dw Principle 2007/11/1809/16/2007 03:08:31 EDTMarkedNobERajkumar, AjayF GProducer^ Technical_70`64cThe text appears to indicate that a Link Detect event is posted whenever a PoA is detected and has not already been posted in a previous Link Detect event. This is different that what was specified on page 40, lines 21-24.d428g51741ƒcypherdavid disapproveƒ disapproveupƒ$dERajkumar, AjayF GProducer^ Technical_44`4748c4Should not reference MN since this is a N2N message.d426g5176at L2 communication whould be handled by LINK_SAP (via NET_SAP).d427g5175jChange "For transport services over L2 the primitives are specified by the MIH_LINK_SAP" to "For transport services over L2, MIH_NET_SAP utilizes the primitives specified by the MIH_LINK_SAP"w Principle 2007/11/2809/16/2007 03:08:31 EDTNodERajkumar, AjayF GProducer^ Technical_44`4748c4Should not reference MN since this is a N2N message.d426g5176specified by the MIH_LINK_SAP" to "For transport services over L2, MIH_NET_SAP utilizes the primitives specified by the MIH_LINK_SAP"w Principle 2007/11/1809/16/2007 03:08:31 EDTNodERajkumar, AjayF GProducer^ Technical_44`4748c4Should not reference MN since this is a N2N message.d426g51766g5176U1bERajkumar, AjayF GProducer^ Technical_70`64cThe text appears to indicate that a Link Detect event is posted whenever a PoA is detected and has not already been posted in a previous Link Detect event. This is different that what was specified on page 40, lines 21-24.d428g5174jChange to "The Link Detected event is generated on the MN when the first PoA of an access network is detected. This event is not generated when subsequent PoAs of the same access network are discovered during the active connection on that link."wAgree{k) done whenever a PoA is detected and has not already been posted in a previous Link Detect event. This is different that what was specified on page 40, lines 21-24.d428g5174jChange to "The Link Detected event is generated on the MN when the first PoA of an access network is detected. This event is not generated when subsequent PoAs of the same access network are discovered during the active connection on that link."wAgree{k) doneisapprove Q{kdoneVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV VVVVVVV%V'V-V.V0V1V2V3V4V6V7V9V:VVVlWWWWW(WIWWWWWWW W W W#W$W%WAWWWWWWWlnoneneededVVVVV(VIVVVVVVV V V V#V$V%VAVVVVVVVneededWWWWW(WIWWWWW0W#vaddmihlinkactiontothetable5VaddsourcelinkactionsVVaddsummationtodelayformulaline38VaddthechannelrangefromnetworkleveltopoalevelaswelVaddthefollowingsentenceatendoffirstparagraphVaddthefollowingtoclarifyuVrstparagraphVVsWWWWuWaddressedWaddressesWWadmissionWadoptionWadvertiseWafteruWagainst WaggregateWagreedWagreedtexttobesuppliedValgorithm<W{WallW,W/Wallow0WallowedWallowsAWalreadyWWW WalsoWW2WfWWWalsorefertocontribution320-01VamendWamendments,WanWWWWWAWWWWWWWWWW W WandWWWWWWWWWWWWWWWWanyWWapplicableWWU$aERajkumar, AjayF GProducer^ Technical_71`3233czLINK_PARAM_REPORT can be generated at periodic intervals but there is no way to indicate this given the current parametersd429g5173jGChange THRESHOLD_CROSSING_DOWN to enumeration (up, down and no change).pAnnex B updated.vtly active interface crosses a configured threshold." to "For each specified parameter, this notification is generated either at a predefined regular interval determined by a user configurable timer or when it crosses a configured threshold."wAgree{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo aERajkumar, AjayF GProducer^ Technical_71`3233czLINK_PARAM_REPORT can be generated at periodic intervals but there is no way to indicate this given the current parametersd429g5173jGChange THRESHOLD_CROSSING_DOWN to enumeration (up, down and no change).pAnnex B updated.v{:aƒ{cypherdavidnz disapproveƒ| disapprove}:Jƒ}cDDoes "Current Link Identifier" refer to the original or target link?d397g5205jyChange "Current" to either "Source" or "Target" for bot the name and description, depending on which should be specified.p6Add "Target Link Action TLV" for MN_HO_Commit Request.vAdd sourcelinkActions Add tragetLinkActions in the MN_HO_Commit_Request In MN_HO_Commit_Confirm: Add SourceLinkIdentifier, TargetLinkIdentifier, StatusSourceLink, StatusTargetLink wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o `52 handover" and that it "may" send a response. How is the MIH User supposed to know when/if it is to send a response?d398g5204jThis appears to be related to the issue of which MIH User(s) receive which handover messages, who responds to theses indicationspMay change due to Cmt 407.wDisagree 2007/12/0709/16/2007 03:08:31 EDTMarkedNo ERajkumar, AjayF GProducer^ Technical_123`52 disapproveƒ[ disapprove\Xeƒ\a nwAgreeyRef 351 (Superceed){l) none needed 2007/12/1909/12/2007 08:16:53 EDTYes s t (i.e. with destination MIHF as the local MIHF). Otherwise, it would trigger an indication (and corresponding response), which we don't want.d400g5202j>Change "request is received" to "request message is received".wAgree{k) donee).vzDepends on 407...(MN_HO_Commit's actions depend on local node only) Clarify: These local actions are for local node only.w Principle 2007/12/0109/16/2007 03:08:31 EDTNo~ERajkumar, AjayF GProducer^ Technical_122`37cNeed to account for a locally generated MN_HO_Commit request (i.e. with destination MIHF as the local MIHF). Otherwise, it would trigger an indication (and corresponding response), which we don't want.d400g5202j>Change "request is received" to "request message is received".wAgree{k) done5202j>Change "request is received" to "request message is received".wAgree{k) doned407yjChange "may" to "shall" (i.e. always generates an indication when a request is received and always generates a confirm when a response is received, from peer MIHF).wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o completed the actions (so that we can send back their status). If the actions tear down the old link and bring up another, isn't that what a handover is all about?ed408g5194j{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo vERajkumar, AjayF GProducer^ Technical_120`12cAeThese lines state that "the MN may initiate a handover process and begin setting up an L2 connection" but, wasn't that the intent of the link actions? In order to send the response we must have completed the actions (so that we can send back their status). If the actions tear down the old link and bring up another, isn't that what a handover is all about?ed408g5194jis response.od409g5193v4} {doWWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW W"W$W)W,W-W.W:W;W>W?W@WAWBWCWDWEWHWKWLWMWNWOWPWQWRWSWTWXWZW^W`WaWbWcWdWeWfWhWiWjWkWmWnWoWpWrWsWtWuWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWNo oERajkumar, AjayF GProducer^ Technical_121`64cNeed to account for a locally generated MN_HO_Commit request (i.e. with destination MIHF as the local MIHF). Otherwise, it would trigger an indication (and corresponding response), which we don't want.d399g5203j>Change "request is received" to "request message is received".wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_122`42cStates that it "may" indicate that the "MN may have started a handover" and that it "may" send a response. How is the MIH User supposed to know when/if it is to send a response?d398g5204jThis appears to be related to the issue of which MIH User(s) receive which handover messages, who responds to theses indicationspMN_HO_Commit.indication is gonewDisagree{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_123`52123`52indication and the message]ERajkumar, AjayF GProducer^ Technical_128`22c"The "may" makes it sound optional.d392g5210jChange "may" to "shall" (i.e. always generates an indication when a request is received and always generates a confirm when a response is received, from peer MIHF).wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o ERajkumar, AjayF GProducer^ Technical_128`22c"The "may" makes it sound optional.d392g5210jChange "may" to "shall" (i.e. always generates an indication when a request is received and always generates a confirm when a response is received, from peer MIHF).wAgree{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo TMarkedNoERajkumar, AjayF GProducer^ Technical_128`13c[The description contains "This identifies the current link" for the source link identifier.d394g5208j_Change "This identifies the current link" to "This identifies the source link of the handover".j‚>JGProducer^ Technical_132`47cAAdditionally, the following is applicable to the above 4 comments. There is some inconsistency between N2N_HO messages and how they identify a given handover. For N2N_HO_Commit we identified the handover by MN MIHF ID while here we are using source and target link identifiersd452g5150jA=Either change N2N_HO_Commit to use source and target link identifiers (and always include it in N2N_HO_Complete) or replace source and target link identifiers in N2N_HO_Complete with MN MIHF ID. Alternatively, include MN MIHF ID along with source and target link identifiers in both N2N_HO_Commit and N2N_HO_Complete.=v wDisagree{l) none needed 2007/12/1909/16/2007 03:38:14 EDTYes KE Feder, PeretzF DisapproveGProducer^ Technical_132`47c132`47cbe in the response/confirm when originated from the target PoS#visapprove ‚soodkapil disapprove‚ disapproveS‚rE Cypher, DavidF DisapproveGGeneral Interest^ Technical_186`32c Consistency in naming is lackingd156g5446j*Add underscore between PACKET and TRANSFERwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes 2/1209/13/2007 13:56:26 EDTYes Identifier (HESSID for 802.11) as part of LINK_SCAN_RSPwAgree 2007/12/0709/16/2007 21:41:08 EDTMarkedYes an important for network selectiond623g4979j8Add "ACCESS_NETWORK_IDENTIFIER" as thee first parameter.vJAdd Access Network Identifier (HESSID for 802.11) as part of LINK_SCAN_RSPwAgree 2007/12/0709/16/2007 21:41:08 EDTMarkedYes or resource reservaton scheme to the same primitive)w Principle 2007/12/0109/16/2007 21:41:08 EDTMarkedYes6g4976jPlease see #309vby 339w Superceded 2007/11/1509/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_121`44BjTables K-1 and K-2 and the corresponding text in annex-K should be completed to allow clear and uniform interpretation and be made mandatory.vAThe mapping of QOS parameters does not relate to behavior prediction. Measurement examples provided by Annex K have nothing to do with interoperability. There different methods for using MAC layer measurements and making inferences on the current quality of service conditions as seen by the device. Annex K examples cannot be made mandatory since measurements provided by specs like 11k are not mandatorywDisagree{l) none needed 2007/12/1909/06/2007 13:47:55 EDTYes s zcvun-authenticatedWunderWunderlyingWunderstandWunified@WuniquelyWunsigned1WunsolicitedWuntiluW'W WuntilizeWWunusedWupW0WWWupdatekWWWWWupdatethesentencekVupdatetooneandonlyonetypeshallbespecifiedVWupdatingWWuponWtWupperW<WAWWurlW<WWWurltobeassignedneedstobeupdatedVuseWWWWWW+W,WWWWWWWuseanouitoidentifytheaccesstechnologyVuseclarifyingtextfromtgumappingdraftacchangedfromtVuselinktupleidinsteadVusetgumihcontribution11-2604rev2toupdatethereferencVusedWWWW&W'WiWwWWWWAWGWpW{WWWWWusefulWWusefulness+W,Wy0W&WWviaWCvl15WWl2W4WEWWl22WWl3W0W<WuWl62WWlaterWWWlayerWW5W<WAWOWW8WWWWlayersWW0WWWWWleastWWWWWleaveWWWWleavetableb-10VlegacyWlength1WlevelWWWWWWWWlike(WWlimitW W8WWWWWWlink'sWlink-layerWlinkmacsfWlinksWWWlistW,W2W<WlistedWWWlists2WllcWllcisspecificallyanieee802entityanditisvalidonlyVlocalwWlocally<WWlocated<WlongWlookWWlostWlow-confidenceWlowerWWWWlower-layerWmWmacW<WWmadeWWWmainWmakeWfWuWWmakingWmanagementW<WWX\vreasonWWWWaWreassemblyWreceiptiWtWreceiveuWreceived WreceiverWreceives'WAW W WreceivingWWkWrecognizeAWrecommendationsWWrecommendedWreconfigured'W WreducedWredundancyWWredundant&W'WWWWWWrefWreferWWWWWWWWWW6WVW\WWWWWWWWWWWWW W@WWWWWWWWWWWWWrefertotgudraftvivekorqiaobingtheremedyisintheedVrefertotgumihdraftfordetailsVreferenceWWWYWWWWWotherVremovethedefinitionofhigherlayersVrenameW2Wrenamemihnon-posnetworkentitytomihnon-pos3.21VrenewalWreplace2W@W reportaWrepresent2Wa table b-12c5Encoding/Decoding is not clear for SYSTEM INFORMATIONd627g4975jPlease see #309pSee 339vAdopt 21-07-0317-01-0000w PrincipleyRef 339{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^General_193a table b-12c-Encoding/Decoding is not clear for PARAMETERSd626g4976jPlease see #309pSee 339v21-07-0317-01-0000w PrincipleyRef 339{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes work without the detailed media dependant definitions?d628g4974jComplete the command, event and information defintions for each of the common MIH terms which need translation into media dependent native terms for each of the media identified.v%Do a more complete mapping in Annex-Lw Principle{h) defer to next round 2007/12/1309/16/2007 23:32:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^General_193-W{tounclearWwith%W€markedቃᐃᚃ%⋃̃/㘃W€W€W€W€W€W€marked⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃⋃ packet error rate now occur in both types. Additionally, throughput is defined differently; UNSIGNED_INT(2) in LINK_PARAM but UNSIGNED_INT(4) in QOS_LIST.jd456g5146j6Delete Throughput and Packet Error Rate from QoS list.OECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_111`48a 7.4.20.3.2c(Kenichi) IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address, and IP Address Informaiton Status should be list.d447g5155rce and target link identifier are one and the same (At least according to the description). d448g5154jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).p;Remove the "intended", since this is HO_Complete primitive.wAgree{k) done 2007/12/0709/16/2007 03:38:14 EDTMarkedYes OECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_111`48a 7.4.20.3.2c(Kenichi) IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address, and IP Address Informaiton Status should be list.d447g5155/16/2007 03:38:14 EDTYesa?M 2007/12/1909/16/2007 03:38:14 EDTYes s e description of the "Source Link Identifier" and "Target Link Identifier is confusing. For the case where the MN_HO_Complete message is sent to the new target PoS then source and target link identifier are one and the same (At least according to the description). d449g51532jChange description of "Source Link Identifier" to "Specifies the source link of the handover". Similarly, change description of "Target Link Identifier" to "Specifies the intendend target link of the handover).wAgree 2007/12/0109/16/2007 03:38:14 EDTMarkedYesME Feder, PeretzF DisapproveGProducer^ Technical_131`2cA The description of the "Source Link Identifier" and "Target Link Identifier is confusing. For the case where the MN_HO_Complete message is sent to the new target PoS then source and target link identifier are one and the same (At least according to the description). d449g5153cjaAdd a paragraph in this clause to state the security considerations for the IEEE 802.21 protocol.vDelete section 5.1.7w Principle{k) done 2007/12/1909/14/2007 23:15:41 EDTYesE Julka, VibhorF DisapproveGProducer^General_175`19cThis section is a duplicate of the information that is given in 6.5.5. Suggest we delete text on lines 19 through 47 in section B.1.2d299g5303j+Delete text on lines 19-47 in section B.1.2v}Sections 6.5.5 and section 8.5 address similar issue. Please update these section and remove any redundancy (refer to them). w Principle{k) done 2007/12/1909/14/2007 18:36:55 EDTNo 4/2007 18:36:55 EDTNo EvRemove "Current Link Identifier" and add both source and target link identifiers. (AC: Kind of funny that the request and the response for MIH_MN_HO_Complete has almost identical parameters)wAgree{k) done 2007/12/1909/16/2007 03:38:14 EDTYes FE Feder, PeretzF DisapproveGProducer^ Technical_180`46cAjIt appears that CoS values from the LINK_PARAM_TYPE of "general" were removed and QOS_LIST (see above comment), defined on page 186 line 26, was added to the list of LINK_PARAM_TYPEs. However, throughput and packet error rate now occur in both types. Additionally, throughput is defined differently; UNSIGNED_INT(2) in LINK_PARAM but UNSIGNED_INT(4) in QOS_LIST.jd456g5146j6Delete Throughput and Packet Error Rate from QoS list.wAgree{k) done 2007/12/1909/16/2007 03:38:14 EDTYes GE Feder, PeretzF DisapproveGProducer^ Technical_180`99dYes GvneedIWwWWW W W+W,WGWWWWWWneedmoretextfromnadagolmieVneedsomeclarificationforfirstpartrefertotgudraftfoVneedtochangethisacrossthedraftVneedtohavemorespecificinputsastowhatrequirementsarVneededpWvdownWWWWWWdraftWWWWW WWWWWW W W&W@WEWWWWWWWWWWWWWWWWdueWWduplicate Wduplication&W'WWWWWdynamicallyWeWWWW0W1W2W<WeWuWWWWegmihftomacormihftophy<VeachWlWmWW W W}WWWWearlier Wec/no2Wedge3WeditionAWeditor'sW^W WWWeditorialsWuirVenableWWWencouragesWendWWengine<WenhanceWenhancementsEWentireWentitiesWWW}WWentityWWWW<WWWWWWWentityremovemobilitymanagementfromtheabovesentenceVentriesWWenumeraedaWenumeratedaWWV tvtheWWWWWWW WWWWW W&W'W8WAWEWGWIWJW{W}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWthecapabilityalreadyexistsindraftintableb-13VtheconfigurationprocessisoutsidethescopeofthestandaVthecurrentdefinitionismoreclear0Vthedefinitionisintherepage193indraftd7.1Vftpg98subVthemihlinkactionspage102subclause7.4.17primitiveinVthemihsapprovidesprimitivesandproceduresastohowtoVtheqosisspecifiedforaccesslinkandisnotendtoendVthespecificationshouldcontainalltherequiredtextandr,Vthesuggesteddefinitionbelowisnotveryclear0VWWWWW8W5ERudolf, MarianF DisapproveGProducer^ Technical_286`51cParts of Annex K, specifically K.2 and K.3 should be mandatory. At least a subset of 4-5 QoS mappings froms access technology A to B must be mandated to make any notion of QoS preservation meaningful.d473g5129ing Code ? If yes, use the right name of the scrambling code identifier in the RRC specifications, cite it.vF21-07-0424-00-0000 OTHER_L2_ADDRESS can be combined with LINK_ADDRESSw Principle 2007/12/0709/16/2007 07:13:12 EDTMarkedNo5ERudolf, MarianF DisapproveGProducer^ Technical_286`51cParts of Annex K, specifically K.2 and K.3 should be mandatory. At least a subset of 4-5 QoS mappings froms access technology A to B must be mandated to make any notion of QoS preservation meaningful.d473g5129e it.vF21-07-0424-00-0000 OTHER_L2_ADDRESS can be combined with LINK_ADDRESSw Principle 2007/11/1809/16/2007 07:13:12 EDTMarkedNo4ERudolf, MarianF DisapproveGProducer^ Technical_177`27c[In table B.3 Data types for address, 3GPP identifiers are unclear and need to be corrected.d474g5128dentifiers for W-CDMA TDD and TD-SCDMA each (all of which reperesent UMTS technologies).pAThe values defined are deliberately made consistent with RADIUS network access server NAS-Port-Type definitions as specified by Internet Assigned Numbers Authority (IANA). I.e., once W-CDMA TDD, TD-SCDMA, etc. are added by IANA to its NAS-Port-Type, they will be added here.vModify the LINK_TYPE Definition as follows: 1: Wireless - GSM/GPRS 2: Wireless - EDGE 3-14: Reserved 23: Wireless - W-CDMA FDD w Principle{e) editor disagrees 2007/12/1209/16/2007 07:13:12 EDTNo 4ERudolf, MarianF DisapproveGProducer^ Technical_177`27c[In table B.3 Data types for address, 3GPP identifiers are unclear and need to be corrected.d474g512874g51283GProducer^ Editorial_177`55cJTable B.4 link type "UMTS" is meaningless, supposedly W-CDMA FDD is meant.d475g5127jChange UMTS to W-CDMA FDD. Introduce new identifiers for W-CDMA TDD and TD-SCDMA each (all of which reperesent UMTS technologies).pAThe values defined are deliberately made consistent with RADIUS network access server NAS-Port-Type definitions as specified by Internet Assigned Numbers Authority (IANA). I.e., once W-CDMA TDD, TD-SCDMA, etc. are added by IANA to its NAS-Port-Type, they will be added here.vModify the LINK_TYPE Definition as follows: 1: Wireless - GSM/GPRS 2: Wireless - EDGE 3-14: Reserved 23: Wireless - W-CDMA FDD w Principle{e) editor disagrees 2007/12/1909/16/2007 07:13:12 EDTNo it 4-255: reserved Acronyms could require definition in section 4 Table B-13 may also need to be updated. aw Principle 2007/11/1809/16/2007 07:13:12 EDTMarkedYes3ERudolf, MarianF Disapprove)jModify the second section of the paragraph to state that the protocol minimizes the scanning required to discover and select another network as a handover candidate.v21-07-0374-02-0000 w Supercededy Ref Cmt 331{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYes Yes s  N{itodoVinWinstructionsWjWjinprogressVVVVVVVVVV6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6V6VVVVVVogressogressogresses similar to ARFCN in GSM/W-CDMA. Or, delete it and re-use the existing access technology-specific identifiers like ARFCN.vIncrease the length to UNSIGNED_INT(2) Modify the Definition as follows: Channel identifier as defined in the specific link technology (e.g. SDO) w Principle 2007/11/1809/16/2007 07:13:12 EDTMarkedNo2ERudolf, MarianF DisapproveGProducer^ Technical_181`19c;LINK_PARAM_UMTS is sort of wrong and needs to be corrected.d476g5126 vneed2WZ Yvmodify1W3Wmodifythedefinitionasfollows1Vmodifythelinktypedefinitionasfollows3VmoreWWWWWW0WvWmostW2W'W Wmotivation+W,WmoveWWWmoveitemsathroughetoannex-lVmovethistexttobelowtheparameterstableVVmovedWmuchWmultipleOWWWmultipletypeielistedWVmustWn2nWWnadaWWWnaiWnameW^WwW W WWWnativeWnecessaryWneedWWWWW' 2vAThe LINK_PARAM_UMTS list does not represent the most important measurements required from the MN as specified in 3GPP 25.215 Rename the list as LINK_PARAM_WCDMA_FDD and replace the Description list by the following elements: Bit 0: CPICH RSCP Bit 1: PCCPCH RSCP Bit 2: UTRA carrier RSSI Bit 3: GSM carrier RSSI Bit 4: CPICH Ec/No Bit 5: Transport channel BLER Bit 6: UE transmitted power Bit 7-255: reserved Similarly, the LINK_PARAM_GSM list does not represent the most important measuBsrements required from the MN as specified in 3GPP 25.008 Merge the LINK_PARAM_GSM and LINK_PARAM_GPRS lists into a single one (e.g. LINK_PARAM_GSM_GPRS) and replace the list by the following elements: Bit 0: RxQual Bit 1: RxLev Bit 2: Mean BEP Bit 3: StDev BEP Bit 4-255: reserved Acronyms could require definition in section 4 Table B-13 may also need to be updated. aw Principle{k) done 2007/12/1909/16/2007 07:13:12 EDTYes '1jDefine an actual relationship between Channel_ID and operating frequencies similar to ARFCN in GSM/W-CDMA. Or, delete it and re-use the existing access technology-specific identifiers like ARFCN.vIncrease the length to UNSIGNED_INT(2) Modify the Definition as follows: Channel identifier as defined in the specific link technology (e.g. SDO) w Principle{k) done 2007/12/1909/16/2007 07:13:12 EDTNo ppend the text 'For 3GPP link type, power up lower layers and establish BPDP context' w Principle 2007/12/0709/16/2007 07:13:12 EDTMarkedYes 1ERudolf, MarianF DisapproveGProducer^ Technical_184`14cCHANNEL_ID, with respect to what is it defined ? Is this an abritrary frequency that is just "labelled" Channel ID, or is it actually tied to an actual frequency ? If yes, does this apply to all access technologies or just to 802.11 ?d477g5125*=1ERudolf, MarianF DisapproveGProducer^ Technical_184`14cCHANNEL_ID, with respect to what is it defined ? Is this an abritrary frequency that is just "labelled" Channel ID, or is it actually tied to an actual frequency ? If yes, does this apply to all access technologies or just to 802.11 ?d477g5125 append the text 'Not valid on 3GPP link type' 2. Change table B-5 Link Actions LINK_POWER_UP description column to append the text 'For 3GPP link type, power up lower layers and establish BPDP context' w Principle{i) to do 2007/12/1209/16/2007 07:13:12 EDTYes 1ERudolf, MarianF DisapproveGProducer^ Technical_184`14cCHANNEL_ID, with respect to what is it defined ? Is this an abritrary frequency that is just "labelled" Channel ID, or is it actually tied to an actual frequency ? If yes, does this apply to all access technologies or just to 802.11 ?d477g5125j{vthetextdescriptiondoesnotsayanythingaboutdirectioniVthetypeieroamingpartnerstypeieroamingpartnerWVtheusecaseforthisisnotclearhowwouldtheuserusethVtheuseofshallandmaywithinthedraft802.21isaspertVtheirWWthemWWthenWW^W W WGWWWW WtheoreticalWthereWWWW WW5WOWWWwWWWWWWWWthereisagreementwiththisprinciplefurtherworkrequiredwVthereisnopointindoingthestandardifitisonlyadesiV WthesetermsaredefinedinieeedisctionaryVthesetwoparametersareoptionalandlinkswhichdontsuppoVtheyWWWWGWWWthisWWWWWWWWWWWWW WW@WiWuWwWWWWWWWWWWWWW8W3wprinciple0123467OWY[\]^_acfgiklmnotuwxy}⌃⣃⤃⦃⧃⫃Ⰳⷃ⽃⿃ÃăŃʃ˃̓փ؃كރ'6@AEM{}㉃㑃㓃㗃㜃㮃㯃㱃㲃㵃㺃㻃ƒă҃Ӄ׃܃݃ scope/unresolvableWqWWWsupercededᐃᾃ/8G⡃⢃⨃$*㣃㬃㾃Ѓ?.cWhat is the value added of Annex J ? Ideally, this section should contain an outline of the L3 transport-solution (a.k.a. MIPSHOP etc) if one exists one day. These requirements to the IETF process are meaningless from IEEE's perspective.d480g5122jeRemove Annex J and insert some references like RFCs if possibly into the normative reference section.{k) done 2007/12/1909/16/2007 07:13:12 EDTNo /ERudolf, MarianF DisapproveGProducer^ Technical_194`38cNetwork type and revision presentation for Wireless - UMTS is wrong. For example, there is no MIMO/OFDM in Rel-7. Then, any MS can be Rel-5 compliant without implementing HSDPA. Similar for Rel-6.d479g5123jxDistinguish between basic W-CDMA features, but remove any reference to releases. 0 - R99 only. 1-HSDPA. 2-HSUPA. 3-MBMS&vD5jRecommend to make at least K.2 and K.3 mandatory, eventually moving these out of the Annex to the main part of the specification. Or, choose a subset of 4-5 QoS parameters that must map from A to B, and leave the rest FYI only.vAcMeasurements available in the respective technologies are not even mandatory therefore can not make the mapping mandatory. Measurement examples provided by Annex K have nothing to do with interoperability. There different methods for using MAC layer measurements and making inferences on the current quality of service conditions as seen by the device. cwDisagree{l) none needed 2007/12/1909/16/2007 07:13:12 EDTYes 6ERudolf, MarianF DisapproveGProducer^ Technical_31`1a5.6.2cAbsence of a media-dependent SAP for GSM/EGPRS. There is only a MIH_3GLINK_SAP, but nothing is defined for GSM/EGPRS cellular, even though both seem to be in scope for 802.21 as part of 3GPP access technologies.d472g5130ZcThere are two places where the MIH_Link_Up is used. Neither of which are correct in name or in placement. MIH_Link_Up.indication is from MIHF to MIHF user, not MAC-WLAN to MIHF or PoA-WLAN to PoS-WLAN.d180g5422j@Expand the block to properly include the link and MIH primitiveswAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes [E Cypher, DavidF DisapproveGGeneral Interest^ Technical_272`40cSWhy does a MIH_MN_HO_Commit Request message produce a MIH_Net_HO_Commit.indication?d179g5423j%Change to MIH_MN_HO_Commit.indicationwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes \E Cypher, DavidF DisapproveGGeneral Interest^ Technical_270`24cThere are two places where the MIH_Link_Up is used. Neither of which are correct in name or in placement. MIH_Link_Up.indication is from MIHF to MIHF user, not MAC-WLAN to MIHF or PoA-WLAN to PoS-WLAN.d178g5424178g5424178g5424v802.21 helps in power conservation on mobile devices by providing information about wireless networks which resilts in reduced scanning to discover wireless networks.wDisagree{l) none needed 2007/12/1909/14/2007 08:30:59 EDTYess!?ERudolf, MarianF DisapproveGProducer^ Editorial_31`33a5.6.2cMLME_SAP, C-SAP, MIH_3GLINK_SAP, LSAP, CS_SAP are not shown in Figure 11 page 30. Figure 11 page 30 is misleading with respect to the description of page 30 and 31.d506g5096state 3. No assumptions are made in this standard regarding the transport of MIH messages over 3GPP and 3GPP2 access links at L2. If the MN cannot reach the MIH PoS via the lower layer (i.e. L2) transport mechanisms, then higher layer (i.e. L3) tranB!sport mechanisms shall be used. "w Principle 2007/11/1809/16/2007 12:18:13 EDTMarkedYesERudolf, MarianF DisapproveGProducer^ Editorial_31`33a5.6.2cMLME_SAP, C-SAP, MIH_3GLINK_SAP, LSAP, CS_SAP are not shown in Figure 11 page 30. Figure 11 page 30 is misleading with respect to the description of page 30 and 31.d506g5096he MIH messages in data frames. Transport of MIH messages over IEEE 802.11 and IEEE 802.16 links is recommended through . 109/16/2007 12:18:13 EDTYes salling exchanges through data frames of Ethertype XYZ even in 802.11 State 3 and that the action frames to carry MIH signalling in State 1 are a specific tool to optimize MIH discovery a.k.a MIH IS before authentication and association.d507g5095jAcPlease state clearly if MIH signalling exchanges using data frames of Ethertype TBD is an option for 802.11 or if it is not. Clearly state to what extent the 2nd available option of using management frames is possible (a.k.a MIH IS only and so on). Alternatively, insert wording here ruling out the possibility of using data frames in 802.11 to carry MIH.cvl vand,W/W0W2W5W<WAWEWWW]WaWfWkWuWwWWWWWWWWWWWWWW WW W'W(W+W,WAWEWpW}WWWWWWWWWWWWWWWWWWW W WWandaddadditionatoidentifytherecanbemultipleentriesWVandaddadditionalinawaytoidentifytherecanbeWVannex5WWEWWannex-lWWWannex-ldoesexactlythatVanotherWWanyWW&W'WWWWWWWWanythingWapWappend0WapplicableWWWWWWvvevaluatedWevaluationWevenW5W WeventW<W+W,WWeventsWW<WWeverythingWexactlyWexaminedWexample<WWWWWWWexamples5WWexceptWOWexchangeWW&W'WWWWWWexchangedWexclusiveAWexecutingiWexhibitWexisting/WWWexistsAWWexpectedWWWexplanationWWW W WWWexplicitWWexplicitlyWexposed@WextensionsWextensivelyWfaOWfacilitatingWWfailedeWfailureWfairlyWWfairlyWWWw&vw-cdma/W3WwaitingWwasWWWwayWWWWWWWwaysWwcdma2WwellWWWW WaWW W WGWWWWWwerevWwfaWwhatWWpWWwhatisietypeandinformationelementpVwhenWWWWW&W'WaWWWWWAWWWWWwhentheinformationoriginatesatlowerlayersoftheprotoVwhenthemihtransportisreliabletheacknowledgementmechaVwheneverWwhereWWwherein WwhichWWWWWWWWAWkWWWWWWwhileWWWwhoseWwhyWWwidely/reaily(WWWWWW W WwithinWWWWWwork WWwouldWWWWWyetWyoshiWyoshiandsubirwilladdressthisVyouWzeroW&*EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_174`21aB.1.1c"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in order of significance." Increasing or decreasing order of significance?d576g5026jy"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in increasing order of significance."vAlso look at comment 384 and changes made therein. Changes to be made on top of change specified in comment 384 Plesae refer to 21-07-0396-01-0000w Principle{k) doneMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in order of significance." Increasing or decreasing order of significance?d576g5026jy"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in increasing order of significance."vAlso look at comment 384 and changes made therein. Changes to be made on top of change specified in comment 384 Plesae refer to 21-07-0396-01-0000w Principle{k) donerest%? 2007/12/1909/16/2007 15:56:25 EDTYes cal_174`21aB.1.1c"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in order of significance." Increasing or decreasing order of significance?d576g5026jy"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in increasing order of significance."er of significance."v# Plesae refer to 21-07-0396-01-0000w Principle 2007/11/1809/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_174`21aB.1.1c"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in order of significance." Increasing or decreasing order of significance?d576g5026jy"Each bit of a BITMAP(N) value [N=8*i, i=1, 2, &] is encoded as an N/ 8-octet value in increasing order of significance."Ãd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_69a7.3.6cAThere is a bit of a dichotomy in the definition of this primitive. "Time Interval" is defined as "Time Interval (in milliseconds) in which the link is expected to go down. The link connectivity is expected to be available at least for the time specified.", and yet "A Link_Going_Down event implies that a Link_Down is imminent within a certain time interval." Some parts of the primitive state that the link will be valid for Time Interval, while other parts imply that the link can go down anyB time within Time Interval. I pity the system that assumes that the link will be valid for Time Interval, only to have it yanked away earlyyd556g5046hat the link will be valid for Time Interval, while other parts imply that the link can go down anyB time within Time Interval. I pity the system that assumes that the link will be valid for Time Interval, only to have it yanked away earlyyd556g5046 cA`Applies to all technology specific reference models (up to 5.5.5): As the adaption of the MIH functionality to a specific technology is not within the scope of 802.21, these subclauses should be moved into an informational annex. A normative reference model should be defined by the by the corresponding group responsible for the underlying technology.`d41g5561vAY" As the adaption of the MIH functionality to a specific technology is not within the scope of 802.21" The adoption part is not within scope of 802.21. But 802.21 needs to specify what is the normative way for these standard technologies to interface with 802.2 1 and this needs to be included in a normative way in the current specification. YwDisagree{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYes EEmmelmann, MarcF DisapproveGAcademic^ Technical_27`45a5.5.5ca5.5.5c9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23~3EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_10`43a4c"Layer 2 (MAC and LLC)"d549g5053j"Layer 2 (MAC and/or LLC)"{k) done 2007/12/1909/16/2007 15:56:25 EDTYessYes3EChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_6`64a3.15c"As an example, the IEEE 802.11 Lower Layers are the MAC Sublayer and the PHY and the 3GPP Lower Layers are the MAC and UMTS layers."d547g5055j"For example, the IEEE 802.11 Lower Layers are the MAC Sublayer and the PHY, while the 3GPP Lower Layers are the MAC and UMTS layers."{k) done 2007/12/1909/16/2007 15:56:25 EDTYessrkedYes"ta5.6.2.6cWhat is "existing" and what is "new" is relative to the development stage of this standard and the referenced 3GPP/3GPP2 standards.d543g5059jAPReplace "The existing service primitives as defined in 3GPP/3GPP2 specification may be directly mapped to MIHF services, and hence no new primitives need to be defined in the 3GPP/3GPP2 specification." by "Primitives of this SAP are specified in the 3GPP and 3GPP2 specifications." Also, add references to the particular specifications.Ppsuperceded by changes from 472wAgree{l) none needed 2007/12/1909/16/2007 15:32:58 EDTNo o npreferenceWHWWWreferenced/WreferencesW2Wrefinement^WreflectWregistration*WregulatoryWrelatedWrelatedtocmt410VrelationWremainsWremoveWWWKWLWMWNWAWWremovetheintendedsinceitishocompleteprimitiveKVLVMVremovetheintendedsincethisishocompleteprimitiveNVremovedW WW#W)W-RWWmWremoved6.2.3Vremovedmentioningofarq Vremovedmihscanalsofixedsomeinconsistenciesintable5RVremovedtheexamples)Vremovedthex-refVVVHWreplacedreferencetovariableoctetswith8octetsinthefHVreplacementWrepresentWWWrepresentationWWWrequestWW Wrequired2W W6WreservedWAWresolutionWWW[WWWWWWWWWresourceOWresources WTV{resolution%WroundWWW/WtoWWWW/W/W/WjWjWjWjWjWjWjWjWkWkWkWkWkWkWlWmWmWnWoWoWoWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWqWᛃᜃᝃឃៃ᠃ᡃᢃᣃᤃ᥃ᦃᧃᨃᩃ᪃᫃ᬃᭃᮃᯃᰃÃăŃƃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃  %/01234CDEFGHIJKLMNOPQRSTUX[\]^_`abefghijklmnopqrstuvwxyz{|}~ ⁃₃⃃℃⅃Ↄ⇃∃≃⊃DcMIH_N2N_HO_Commit does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d539g5063jcAdd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit.vCPlease refer to contribution 21-07-0320-02-0000-Resource_DefinitionwAgreeyRef 351 (Duplicated){l) none needed 2007/12/1909/16/2007 15:23:06 EDTYes ENatarajan, Kadathur SF DisapproveGProducer^GeneralcMIH event subscription should allow the subscriber to set certain conditions or qualifiers. With that only events meeting those conditions or qualifiers will be notified to the subscriber.d538g5064jJInvestigate if this capability is needed and the best ways to implement itvAdopt contribution 21-07-0305-02-0000-Event-Subscribe-Update.doc with the following change: remove the LINK_TYPE from LINK_DETECT_CONFIG, since the Link Identifier parameter already provided the link type.w PrincipleOFESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_121`41a7.4.23cLTarget PoA is already included in Target Link Identifier. This is redundant.d618g4984jRemovewAgree{k) done 2007/12/1909/16/2007 21:41:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_124`35a7.4.24.1.2 and otherscSeveral locations where "MAC address" is used instead of a genric link id or address. MAC is a 802 term, should use a genreal term, which is already defined.d617g4985j correct itp Done in 621va) Target PoA of MIH_N2N_HO_Commit, MIH_Net_HO_Commit (done) ( MIH_MN_HO_Commit TargetPoA deleted in Cmt 619) b) Old/New Access Router of (waiting email) MIH_Link_UP, MIH_Link_Down, MIH_Link_HO_Imminent, MIH_Link_Handover_CompletewAgreeyRef 621{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes s s  vaddWWEWWWaWeWfWuWWWWWWWWWWAWIWWWWWaddareferenceVaddastatusresultthehandovercompleteindicationtoaccoeVaddaccessnetworkidentifierhessidfor802.11aspartoflVaddanotherieforthisVaddavailableadmissioncapacityforsupportednumberofcosVaddcandidatelinklistintherequestmessageinsection8.6.IVaddclarifyingtextfromtgudraftvivekorqiaobingtheresVaddegatthestartingofnextlineVaddlinkmacsandmbbhandoversupporttomihcapabilitydiscovfVilitydiscovfVfVfVÃb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@mnopqrstEMyles, Andrew FF DisapproveGProducer^ Technical_3`1a1.3cAuThe figure caption indicates that "Figure 1 shows the placement of the MIHF within the mobility management protocol stack of an MN or network entity". However, the protocols listed upper layers are not mobility management protocols. The intent of the figure (based on the caption) appears to be to describe the control plane, but the figure itself describes the data plane.ud74g5528on indicates that "Figure 1 shows the placement of the MIHF within the mobility management protocol stack of an MN or network entity". However, the protocols listed upper layers are not mobility management protocols. The intent of the figure (based on the caption) appears to be to describe the control plane, but the figure itself describes the data plane.ud74g5528Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@ÃePÃe@㙃㚃㛃㜃㝃㞃㟃 `IcAMConsistency: The MIH_N2N_HO_Query_resources.request and the MIH_N2N_HO_Query_resources.indication contain a CandidateLinkList as an optional parameter. However the MIH_N2N_HO_Query_Resources request message does not have this TLV. How can this information be received in the indication, if it is not contained in the request message?Md197g5405j?Either add TLV to message, or remove parameter from primitives.pupdated section 8.vLAdd CandidateLinkList in the request message in section 8.6.3.13 on page 165wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYess EEmmelmann, MarcF DisapproveGAcademic^ Editorial_17`36a5.3.4c%missing comma after last word in lined37g5565j"and its representation,"{k) done 2007/12/1909/10/2007 07:08:58 EDTNoohe internet). wDisagree 2007/11/1809/10/2007 07:08:58 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Editorial_17`36a5.3.4c%missing comma after last word in lined37g5565j"and its representation,"{k) done 2007/11/1809/10/2007 07:08:58 EDTMarkedNofvdifficult(W+W,WWWdifficulttoenvisageusecasesandusefulnessofthisevent+V,VdirectionWIWaWWdirectionsWdisagreeWWdisagreewithremovingthesectionVdiscardAWdiscoverWWfWWdiscoveringWdiscoveryWdisctionaryWdiscussedWdistinguishWdl/WdoWW5WWWWdoamorecompletemappinginannex-lVdonotdeletethissectionVdocWWWWW_vfiguresWfiniteWfirstWWWW'WAWGWW W WflagWflexibility/Wflow&WfollowingWWW0W2WuWWWWAWWWWWWWWWW5W<WeWWWEWWWWWWWWWWWWW W Wfortableb-13foraspecificrevisiontypeanddefineavenVformWformulaWWfound WframesWfromWWWWW2W<W@WiWWWWEWWWWWWWWWfunctionWfunctionalitywWWW WfunctionsW}Wg0W1W2W<WuWWgenerallyWgetWgoWgoalWgoingWWWWgprs2WgroupWgroup's,Wgsm2Wgsm/gprs3WhandleWhandoverWWWeWuWwWWhandoversW<WeWWYes just an illustrative example and it's quite difficult to include the above suggestion in this example. This example has no bearing on other deployment scenarios (which may include MIH Ref Points going across the internet). wDisagree 2007/11/2609/10/2007 07:08:58 EDTMarkedYesloud with corresponding reference points.ivshownWWshowsWsidewWWsignalingWsimilarWWWWWsimilarly2WsimplificationWsimplyWsinceWW&W'WuWWWWWWWWWsingle2WsmaeGWsmaeascomment432GVsowW WsomeW&W+W,WWsomethingWsourceDWEWW'W W WsourcelinkactionsWWsourcelinkidentifierWWWspacesWspecWspecifcWspecificWWWWW1W]WWWEWWWWWWspecificapplicationlevelservicesareoutofthescopeVspecificallyWspecificationW,WAW]WWWspecificationsWW,WspecifiedWWWWW2WWWWW}WWWWWspecifiesWWWspecifyAWWWspecifyingWspecsWspeedW9vFigure 8 is an 802.16 SAP diagram. MIH_LINK_SAP is an abstract SAP and it maps to C_SAP and M_SAP in case of 802.16 network. There is no need to show MIH_LINK_SAP in this figure.wDisagree{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYessh the SAP is gray shaded and hence illustrated to be part of 802.21.Rd40g5562jUse the name MIH_LINK_SAP. Possibly include any "adaptation" layer / SAP and state (if appropriate) that no additional protocol enhancements are required but that existing service primitves can directly mapped to the MIH_LINK_SAP.v$Plesae refer to contribution 414-02 w Superceded 2007/11/1809/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_27`37a5.5.4cjC_SAP and M_SAP provide services defined by MIH_LINK_SAP but the MIH_LINK_SAP is not illustrated in Fig. 8d39g5563jInclude MIH_LINK_SAP in Fig. 88EEmmelmann, MarcF DisapproveGAcademic^ Technical_27`37a5.5.4cjC_SAP and M_SAP provide services defined by MIH_LINK_SAP but the MIH_LINK_SAP is not illustrated in Fig. 8d39g5563jInclude MIH_LINK_SAP in Fig. 8pecific SAP which is also the case for Fig. 9 in which the SAP is gray shaded and hence illustrated to be part of 802.21.Rd40g5562jUse the name MIH_LINK_SAP. Possibly include any "adaptation" layer / SAP and state (if appropriate) that no additional protocol enhancements are required but that existing service primitves can directly mapped to the MIH_LINK_SAP.v$Plesae refer to contribution 414-02 w Superceded 2007/11/2609/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_27`37a5.5.4cjC_SAP and M_SAP provide services defined by MIH_LINK_SAP but the MIH_LINK_SAP is not illustrated in Fig. 8d39g5563jInclude MIH_LINK_SAP in Fig. 8Ov1wirelessgsm/gprs3V1.1W1.3W10^W102W105WW11W11-2604W11kW12W13.1W134W136<W137<W14W15AW150W16W165IW178vW180^W181aW182W186^W19<WWW193W2WWWW/W0W1W2W3W<WWWW'WAW W2wirelessedge3V20W/W2007WW21/W<W21-05/335,W21-05/350,W21-07-0191-00-0000VW21-07-0302-00-0000WMWW21-07-0302-01-0000-sWWWWWWWWWWW21-07-0305-02-000021-07-0305-02-0000-eWWW21-07-0306-02-0000-lWWW21-07-0308-01WW21-07-0317-01-0000WᜃUW21-07-0422-00-00000W21-07-0424-00-0000421-07-0430-00-0000W21-07-0430-00-0000-lW210W22/W227,WWEW(/zERajkumar, AjayF GProducer^ Technical_122`21cOThe "Current Link Identifier" is inconsistent with the other handover messages.d404g5198jIChange "Current Link" to "Source Link" for both the name and description.wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNoequest message to the destination MIHF only when the destination is not local.vby 407w Superceded{i) to do 2007/12/0909/16/2007 03:08:31 EDTNo zERajkumar, AjayF GProducer^ Technical_122`21cOThe "Current Link Identifier" is inconsistent with the other handover messages.d404g5198jIChange "Current Link" to "Source Link" for both the name and description.wAgree{k) done 2007/12/0909/16/2007 03:08:31 EDTNoAgree{k) done 2007/12/0909/16/2007 03:08:31 EDTNoooo_HO_Commit.request message to the destination MIHF only when the destination is not local.v407w Superceded 2007/12/052007/12/05WtE Cypher, DavidF DisapproveGGeneral Interest^General_179`25cLBits 3, 4, and 5 are not in the same meaning order as for the MIH_EVENT_LISTd154g5448j"Could they be for easy of mapping?p(Make it the same order as MIH_EVENT_LISTwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes uE Cypher, DavidF DisapproveGGeneral Interest^ Technical_175`54cVThe number of octets (27) is not correct using the numbers contained on the next page.d153g5449jChange 27 to 29 and 26 to 28wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes terest^ Technical_175`54cVThe number of octets (27) is not correct using the numbers contained on the next page.d153g5449jChange 27 to 29 and 26 to 28wAgree{k) done 2007/12/1209/13/2007 13:56:26 EDTYes idF DisapproveGGeneral Interest^General_179`25cLBits 3, 4, and 5 are not in the same meaning order as for the MIH_EVENT_LISTd154g5448`pE Cypher, DavidF DisapproveGGeneral Interest^ Technical_199`7crThere is no INFORMATION_ELEMENT defined. However it may be a consistency problem and should be IE_TYPE on page 196d158g5444jSpecify INFORMATION_ELEMENTvcWhat is IE_TYPE and INFORMATION_ELEMENT IE_TYPE is used by IE Reporting template No change needed.wDisagree{l) none needed 2007/12/1909/13/2007 13:56:26 EDTYes and should be IE_TYPE on page 196d158g5444jSpecify INFORMATION_ELEMENTvcWhat is IE_TYPE and INFORMATION_ELEMENT IE_TYPE is used by IE Reporting template No change needed.wDisagree{l) none needed 2007/12/1209/13/2007 13:56:26 EDTYesTOjIf the intention is to support a mechanism to provide handover candidates by location, state clearly that mechanism is supported but the algorithm for deciding what information to provide is out of scope.pA"MIIS defines a unified mechanism to the higher layer entities to provide handover candidate information in a heterogeneous network environment by a given geographical location. However, the algorithm for deciding what information to provide is out of scope."vAdd this to next paragraphwAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYes sbE Cypher, DavidF DisapproveGGeneral Interest^ Technical_50`33a653crFigure 19 shows an expanded view of the second network (Operator_2). However the expanded view contains Operator_1d130g5472jChange Operator_1 to Operator_2wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes E Cypher, DavidF DisapproveGGeneral Interest^ Technical_44`20a64311cATable 5 does not include the MIH_Link_Actions as a command. Throughout the document there appears to be a problem differentiating between MIH_Scan and MIH_Link_Actions. If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses.d129g5473j]If both are needed then clearly include both in all relevant, tables, TLVs, IEs, and clauses.v/MIH_Scan is deleted by other comment. (Cmt 444)wOut of Scope/UnresolvableyRef 444. (Superceded){l) none needed 2007/12/1909/13/2007 13:56:26 EDTYes ist.d131g5471VPcThere are two media-dependent SAPs, i.e.: MIH_LINK_SAP and MIH_NET_SAP. Annex L provides a mapping of the associated service primitives to a set of technologies, but only for MIH_LINK_SAP. Why is there no corresponding mapping for MIH_NET_SAP ?d55g5547jA\If a mapping of 802.21 service primitives to a specific technology is provided, it should be complete. Either delete all references to a specific technology until a complete mapping is done by the corresponding group (and then add a corresponding annex as an amandment to 802.21) or indicate that there is no mapping for certain service primitives.\vThe MIH_NET_SAP is not media dependent. Hence there is no mapping required between MIH_NET SAP and other media specific technology.w Principle{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYes s vdecisionsWWdeclinedWdecreasingWWdefault'W WdefineW^WWWWdefinedWWWWW&W'W/W1W@W^WWW{WWWWWW5Ã5Ã5Ã6Ã6 Ã60Ã6@Ã6PÃ6`Ã6pÃ6 Ã6 Ã6 Ã7 Ã7 Ã70Ã7@Ã7PÃ7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCFE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_50f QOS parameters by different vendors. Preventing unpredictable behavior will require vendor - specific solutions which will complicate testing and delay market acceptability.d26g5576jTables K-1 and K-2 and the corresponding text in annex-K should be completed to allow clear and uniform interpretation and be made mandatory.vAThe mapping of QOS parameters does not relate to behavior prediction. Measurement examples provided by Annex K have nothing to do with interoperability. There different methods for using MAC layer measurements and making inferences on the current quality of service conditions as seen by the device. Annex K examples cannot be made mandatory since measurements provided by specs like 11k are not mandatorywDisagree 2007/11/1809/06/2007 13:47:55 EDTMarkedYesE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_50`vlineWWWWWW<W^WaWWEWWline-13Wline-13poacontainer1pg53makethisoptionalVline-14WWline-36WlinesWlinkWWWWWWWWWWWWWWW WWW/W0W1W2W3W4W<WDWEW^WaWlWmWuWvWWWWWWW8WWWWWWWWWWWlink'sWlink-layerWlinkmacsfWlinksWWWWlistWWWWWWW,W2W<WOW^WkWlWmWvWWWW W WWWWWWlower-layerWmWmacW5W<WWmadeWWWWmainWmakeWWW5WfWuWWWWW Wmakeannex-lnormativeVmaking5WWWmanagementW<WWF36jEither introduce at least a formal definition for a GSM/EGPRS media-specific SAP here, or remove GSM/EGPRS from the scope of 802.21 when talking about 3GPP technologies.v/Please refer to contribution 21-07-0414-02-0000w Principle{k) done 2007/12/1909/16/2007 07:13:12 EDTYes ess 2007/12/0809/16/2007 07:13:12 EDTYessic SAP here, or remove GSM/EGPRS from the scope of 802.21 when talking about 3GPP technologies.v/Please refer to contribution 21-07-0414-02-0000w Principle 2007/11/26ependent SAP for GSM/EGPRS. There is only a MIH_3GLINK_SAP, but nothing is defined for GSM/EGPRS cellular, even though both seem to be in scope for 802.21 as part of 3GPP access technologies.d472g5130jEither introduce at least a formal definition for a GSM/EGPRS media-specific SAP here, or remove GSM/EGPRS from the scope of 802.21 when talking about 3GPP technologies.v/Please refer to contribution 21-07-0414-02-0000w Principle 2007/11/18z#gvmechanismsWWmediEWmediaWWEWWmedia-dependentWWmedia-specificWWmeetWmentionedEWmerge2WmessageiWWW'WAWIW W Wmessage-id'W WmessagesW&W'WfWwWWWWW}WWWW W WmethodOWmethods5WOWWmichael/stephenWmichael/stephentoprovideexplanationVmihWWWWWWWWWWWWWWWWW@WEWfWiWkWtWwWxWWAW}WWWWWWWWWWWWW W WmihfunctionsisusedinthepluralsenseofmihfunctionVmihlinkhoimminentmihlinkhandovercompleteVmihlinkupmihlinkdownVmihmnhocommitcommandnowforlocalonlyxVmihnmssaphasbeendeletedVmihscanisdeletedbyothercommentcmt444V/9ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Editorial_170`59a8.6.4.2cMIH_Get_Information response change the table entry from "(Info Response Binary List TLV)" to "(Info Response Binary Data List TLV)"d616g4986j correct itwAgree{k) done 2007/12/1909/16/2007 21:41:08 EDTMarkedESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_87`31a7.4.4.cAA general comment related to event-subscription, link-detect and network commit to be used for network guided handovers. As a concept, the network PoS may not be aware or interested in the PoA specifics for handover selection and decision but only the network identifiers are sufficient to make the decisions. The attached usecase provides more information. Specification changes to support this are individually submitted. Note that these changes are useful even if applied individually to eacBh of the primitivesd615g4987j-Please see the contribution #305, 306 and 307mERajkumar, AjayF GProducer^ Technical_111`4563cASince available resources are on a per candidate link basis there must be the same number of entries in the LIST(LINK_POA_LIST) as there are in LIST(QOS_LIST), i.e. there must be a one-to-one relationship. In fact, the IP configuration method and server addresses should also be on a per candidate basis thus they should be lists as well (however, care is needed to map the server addresses to the IP configuration methods since not all will be present)d417g5185js since not all will be present)d417g5185j+\ 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`48a6.5.5.2cWhy is it necessary that this container should have atleast one PoA container? It should be possible to identify the access network and its associated information without knowing the specifics of the PoA present in that access network.d603g4999jClarify or removevLine-13 PoA Container #1 (pg 53) ..........make this optional Remove " An Access Network Container shall contain at least one PoA Container and may contain one or more Vendor Specific Network IEs: " w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_41`11a6.3.5cBWhat is the difference between Link-Up and Link-Handover-Complete?d602g5000jClarifyp,clarified by changes from 21-07-0430-00-0000v21-07-0430-00-0000w Principle{k) done 2007/12/192007/12/022007/12/02}vbasisIWbeWWWWWWWWWWWWWWWWWW WW&W'W,W2W4WOWWWaWuWwWWWWWWWWWWWWWWW WW W'W(W)W@WAWEWGW{WWWWWWWWWWWW WbearingWbeenWW7WaWuWWWW Wbefore WuWWbehaviorWWWbehindWbeing WWbelow0WaWWWWbep2WbetterWWbetweenAWWWAWWWbinary<WWWbitWW/W2WWWW'WW W W Wbit8typeieroamingpartnerremovesWVbitsWWbler2WbodyWbothWEWWbreakuWbroadcastWWbroadcastedWbroadcastsWbtw WbulletWWK cBis for illustrative purposes only and shall not constrain implementations" and "If the MN cannot reach the MIH PoS via the lower layer (L2) transport mechanisms, then higher layer (L3) transport mechanisms shall be used." Other shalls are at a considerable level of detail and express how a particular action is to be taken, but not whether the procedure of which the action is a part is mandatory for a claim of conformance. There is at least one "shall" statement that media specific pCrocedures (where defined) would take precedence, since there is no way of specifying a unique reference document for each specific media that makes it impossible to know what should be implemented now and what in the future as media specific documentation changes. There are 433 instances of the word "may", the use of this word is not defined within the standard but appears to indicate (as usual) an implementation option. The provision of 433 explicit implementation options appears eLJ^ 08/24/2007 10:31:14 EDTYes E Jeffree, TonyF DisapproveGProducer^General_350cAIt is entirely unclear what it means to claim conformance to this standard. There is no conformance clause. There is no PICS (Protocol Implementation Conformance Statement). There are 216 instances of the word "shall" but a number of these are meta comments on the nature of the standard itself, including statements that restrict the impact of the standard such as "The architectural placement of any MIHF shall be left for the 3GPP2 standards development organization (SDO). Figure 10 gure 10 ess this duplicate retransmitted message if it has already done so. If a destination MIH node receives an MIH protocol message with no ACK-Req bit set then no action is taken with respect to the acknowledgement functionality. " WITH "The destination MIH node shall respond with an acknowledgement message for duplicate MIH messages (messages with same transaction-ID) that have thBK  cAW"The source MIH node may at most make two retransmission attempts in addition to the first attempt for an MIH protocol message with the same Message-ID and the same Transaction-ID." What's special about "two"? Why this embedded magic number? This depends on the properties of the link, and couples the protocol to assumptions about the medium.Wd2g5600j-Make this number a property of the link type.vAReplace "The source MIH node may at most make two retransmission attempts in addition to the first attempt for an MIH protocol message with the same Message-ID and the same Transaction-ID." With The source MIH node shall retransmit an MIH protocol message with ACK-Req bit set until it receives an acknowledgment or the number of retransmissions reaches its maximum value. The maximum number of retransmissions can be reconfigured depending on implementation. The default value of maximum B%number of retransmissions is two (2).w Principle{k) done 2007/12/19vcellsWWcellular<WcertainWchangeWWWWWWWWWWWWW WWWW W0WAWDWOW]W^WaWilWmWtwWWWWWWWWW W WEWGWpWWWWWWWWWchangeasfollowsVVAVVVchangeasfollowsonpg83line27VchangeavailableresourcesetdescriptionfromlVmVchangecandiddatepoatocandiddatepointofattachmentGVchangecurrentlinkidentifiertosourcelinkidentifierDVchangefrommacaddresstolinkaddressVchangeittorp1rp2VchangeitwithlinkaddressVchangelinkactionstolinkactionVchangemihftomihuserVchangereferenceconnectiontoreferencepointVchangesentenceasfollowsVchangesentencestoasfollowsVtoenumeraedtypeaboveaV`. EStephens, Adrian PF DisapproveGProducer^ Technical_144a8.2.1cIt is not clear whether there is some limit on the number of unacknowledged (outstanding) messages. This has implications for the duplicate detection buffer size at the receiver.d4g5598j/Either negotiate a window size, or set it to 1.pgroup disagrees with commentv, No limit on number of acknowledged messageswDisagree{l) none needed 2007/12/1908/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_144`29a8.2.1ca8.2.1cith commentv, No limit on number of acknowledged messageswDisagree{l) none needed 2007/12/0508/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_144`29a8.2.1ca8.2.1ca8.2.1c11/1808/24/2007 10:31:14 EDTMarkedYes/j Please see the contribution #308pSuperceed by 624vPlease refer to 21-07-0308-01 (Also refer to contribution 320-01 which has changes for resource reservaton scheme to the same primitive) NOTE to Vivek: Original resolution (in commentary -07) was Superceeded same as comments 26, 286, 588 and 590w PrincipleyRef 624 {l) none needed 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_122`27a7.4.24cLTarget PoA is already included in Target Link Identifier. This is redundant.d619g4983jRemovewAgreeyRef 618 (duplicate){k) done 2007/12/1909/16/2007 21:41:08 EDTYes s s ters have crossed a threshold for the **best** link the mobile node's L2 mobility manager can find thus indicating that MIHF should consider roaming to another network, then that would be an appropriate use of this primitive.d95g5507jClarify the text.3(vofWWWWWWWWWWWWW&W'W,W5WAWEWOW\W]WaWiWkWlWmWtWuWwWWWWWWWWWWWWWWW WWWW W&W'W(W+W,W@WAWEWGW{WWWWWWWWWWWWWWWWWWWWW W W WWoffers@WokWWoktokeepitVolduWold/newWonWWWWW0W5WIW^WaWkWuW}WWWW WWW W'WIWWWWWWWWWWWWW W WW hvsameWlWmWW'W W WsapWWWWFWWWWWFWWWWWWFWWWWWWWWWFWWWWWvbycomment105Vbycomment35Vbycomment40Vbycomment88Vbycomments328and643/VbytgusubmissionVcWVcWWVcWWVcWWVcWWVcWWVcWWWcWWWVcWWcWWytgusubmissionVcWW cAIt should be made clear that in the case that the operation is not successful (i.e. STATUS is not set to success) that the remaining non essential TLVs should not be present (in the case of MIH messages from a remote entity this can save on resource usage on the airlink). Suggest we add text to the Response Link Event List column to clarify that this is not included if the status indicates failure. This is a global comment (applies to numerous places in the specification). If comment is acBMcepted NW can bring in explicit text changes to be made for remaing sections.;d281g5321jbAdd text "This is not included if STATUS is not set to code 0 (success)" to the description columnvAll primitivies in section 7 would need to be examined carefully for this behavior. This is applicable for MIH Protocol messages.wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTYes EDTYes s 342g5260j3remove all definition and mentioning of MIH_NMS_SAPr?EMyles, Andrew FF DisapproveGProducer^ Technical_71`13a7.3.9cAThe text states that a Link_Parameters_Report indicates changes in link parameters that have crossed specific thresholds. However, it is unclear as to when this report is generated and for the purpose it's being generated. Is this report supposed to be generated whenever link parameters have crossed a threshold even when there may be another PoA in the current network for which the mobile node could perform an L2 transition assuming the PoA would facilitate a link wherein the parameters wo. Is this report supposed to be generated whenever link parameters have crossed a threshold even when there may be another PoA in the current network for which the mobile node could perform an L2 transition assuming the PoA would facilitate a link wherein the parameters woÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@vMEMyles, Andrew FF DisapproveGProducer^ Technical_70`32a7.3.8cr in the mobile node should consume this report and it should not be sent up to MIHF. If the report is supposed to indicate that link parameters have crossed a threshold for the **best** link the mobile node's L2 mobility manager can find thus indicating that MIHF should consider roaming to another network, then that would be an appropriate use of this primitive.d95g5507jClarify the text.p- text from Vivek emailvNeed some clarification for first part. (Refer to TGu draft for MIH mapping and add relevant text from there). OK for second part in draft and dont need to add any clarification. (L2 manager can also be on the netwok side...) w Principle{i) to do 2007/12/0709/11/2007 17:46:47 EDTMarkedYes EMyles, Andrew FF DisapproveGProducer^ Technical_70`32a7.3.8cuPÃu`ÃupÃuÃuÃuÃv dDTcaecvthedefinitionofatermlinkswitchhandoverinthissectioVthedraftusescell-idindifferentplacestorepresentpoaVtheentitiesarenotreallynumberedthesearejustbulletsVtheentitycanidentifyiftheactionswerecompletedviathvVtheideawastoobtainthisinformationbeforemakingtheraVthelinkparamumtslistdoesnotrepresentthemostimporta2VthemacconvergencegatewayfunctionasdefinedbytguproviVVthemappingofqosparametersdoesnotrelatetobehaviorprVthemihgetlinkparametersprimitiveinthedraftpg98subVthemihlinkactionspage102subclause7.4.17primitiveinVthemihnetsapisnotmediadependenthencethereisnomapVthemihsapprovidesprimitivesandproceduresastohowtoVthemihfdoesknowthetransportaddressVthemnmaynothaveafqdnVthenameofthesenethocommandsneedtochangeV V VVVotveryclear0VSvaddthisinsection8.2VaddthistonextparagraphVaddtragetlinkactionsinthemnhocommitrequestVVaddedWWWWWWaddingWaddition'W WadditionaWWadditionalWWWWWaddressWWW W W4WkWuWWWWWaddressesWadmissionWadoptWWWWWWWadopt21-07-0317-01-0000Vadoptcontribution21-07-0305-02-0000-edocwiththefollowiVVVadoptcontribution21-07-0306-02-0000-ldocwithmodificatioVVadoptcontribution305-2withmodificationVadoptionWadvertiseWafteruWagainst WaggregateWagreedWWagreedtexttobesuppliedbynadagolmieVagreementwWalgorithm<W{WallWWW W,W/WOWWWallprimitiviesinsection7wouldneedtobeexaminedcarefVall-zerosWallow0WWSvprovidedWWWWWWW5WAWOWWWWprovidesWWWWWWW W WWWWprovidingWWprovisioningAWputWqiaobing WW^WmWtWWWWqiaobingtofxthisandprovideexplanationVqiaoboing WqosWW^WWWqosisanimportantaspectofmihandthat'swhymihprovideVVquality5WWWqueriesW W WWWqueryWiWkWWWWWqueryresourceeportflWqueue(WquiteWradioWrange^WWrateWWWrdf<WWW6Wre-registerWreachWreaches'W WreadW^W WreadabilityWrealWreallyWWWeEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_50`57a6.5.4cI assume that Information Element definitions are a normative part of the standard. Therefore they should not be included in an annex, which is generally intended for additional information.d314g5288jKIf annex A is normative, make it a clause in the body of the specification.wDisagree{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYessI assume that Information Element definitions are a normative part of the standard. Therefore they should not be included in an annex, which is generally intended for additional information.d314g5288jKIf annex A is normative, make it a clause in the body of the specification.wDisagree{l) none needed 2007/11/2809/14/2007 23:15:41 EDTMarkedYese the radio connection has been made this information can be esaily obtained.wDisagree 2007/11/1409/11/2007 17:46:47 EDTYesEMyles, Andrew FJEMyles, Andrew FF DisapproveGProducer^ Technical_50`1a6.5.3 802.11 networks this is not the correct information for the following reasons: 1. The mobile node should not care about the location of the PoA. The mobile should only care about whether RF coverage is obtainable at a specific location. 2. Many operators will be unwilling to provide actual location (e.g., latitude and longitude) for a PoA. As such, there will be no location information in many MIIS databases.d80g5522jChange the location information such that it is providing the RF coverage area of the network and not the location of specific PoAs. Note that this is not just a comment about Figure 19, but has ramifications for other clauses in the document.v by comment 88w Superceded{l) none needed 2007/12/1409/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_50`1a6.5.31a6.5.3ical_50`1a6.5.3cl_50`1a6.5.3cvrequest@resoponse@rf@sameQsapsaps@saying@3secton@ishown@7spell@state@table0ttgu@Tthatthethedefinitionofatermlinkswitchhandoverinthissectio@Vthenetworkcontrollerprovidesalistofcandiddatenetwork@thetextdescriptiondoesnotsayanythingaboutdirectioni@thereisworkbeingcarriedoutbysecuritygrouptoaddress@jthisYEOto2{zun-authenticated@user@ww-cdma@$will@&w@agreec principle0ydeferred@deferredrefcmt497@)deferredseecmt497@oref@Qref397@a{disagrees@4do!done)=eeditordisagreesWeditorjinprogress6k OQ>M=kdone;lls@#vreferences,WrefersWreflectWWregardingWregisterWregistrationWWregistrationrequestcodedependingontherequestcodetheVrel-5/Wrel-6/Wrel-7/Wrel-8/Wrel-99/rel-4/WrelateWrelatedWrelevantWreliableWreliesWremainingWremedywWremotewWWWremotely<Wremove,WWWWWWWEWWWWWremove802.15fromfigure1andfrompage4line-14VVremoveapinparenthesisVremoveipconfigstatusfromisquerybutleaveitforotherVremovesection8.2.3.1VremovethedefinitionofhigherlayersVremovingWrenameW2Wrenamemihnon-posnetworkentitytomihnon-pos3.21VrenewalWreplace2W@WW replacebullet5withtheproposedbulletsandaddsometextVreportaWreportingpWreports Wrepresent2WW pDeleted the Scan Response Set in section 7. Need to modify Annex B LINK_ACTION_RSP to SEQUENCE (LINK_ID, LINK_AC_RESULT_CODE, CHOICE(NULL, LIST(LINK_SCAN_RSP))). Check subclause 8.wAgree{k) done 2007/12/1909/04/2007 16:19:39 EDTYes s tion suggest that multiple links can be controlled. However the response contains Link Actions Response of type Link Actions Response which is not a list. Also, the Scan Response Set contains a list of MAC address and signal strength. This has to be linked to the link_id specified in the Link BActions Response.d18g5584joChange the types to list for action request and response. Include Scan response as part of the action response.his has to be linked to the link_id specified in the Link BActions Response.d18g5584joChange the types to list for action request and response. Include Scan response as part of the action response.Ãe Ãe0Ãe@Ãe@ v23/W3WEW23wirelessw-cdmafdd3V25/W25.0082W25.2152W25.306/W26W/W^W27/WW28-63/W286W29W2988{W3W/W2WOWW3-143W3-14reserved3V3.1W3.16W3.18W3.19W3.21W3.43W3.44AW3.44serviceprimitiveconceptualabstractiondescribingtheAV305-2W320-01WW328/W34W35W36WW<W38W384WWWWWWWWWW4WWWW392DWEWEWEWWWWW7WWWW:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCÃCÃCÃT`[5pvfollowsWWW/W1W3WAW^WWWWWWforWWWWWWWWWWWWWWWWWWWW0W5W<WEWOWeWkWlWmWxWyW}WWWWWW W W'WEWWWWWWWWWWWWWWW W Wfortableb-13foraspecificrevisiontypeanddefineatecVformWWformatWformats&W'WWWWWformulaWWforwarding0Wfound WfqdnWWfragmentationWframeAWframesWfromWWWWWWWWWWW2W<W@WWW WfunctionsW}WfundamentalAWfurtherWwW(WfxWg0W1W2W<WuWWWgatewayWWgenerallyWWgeneratedWgenericWWCvlistedWWlists2WllcWllcisspecificallyanieee802entityanditisvalidonlyVlocalwWxWyW}Wlocally<WWlocated<WlocationWWWlogicalWlongWlongerWlookWWWlostW Wlow-confidenceWWWlowerW0WWWWlower-layerWmWmacWWW5W<WWmachineWmadeWWWWWWmainWmakeWWWW0W5WfWnWoWuWWW'WJWWW Wmakeannex-lnormativeVmakethisoptionalnVoVmakethisoptionalintheresponseJVmaking5WWWmanage(WmanagementWWW<WW@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23Ã32Ã3 1Ã300Ã23JE Barr, John RF DisapproveGUser^General_124a7.4.24cMIH_N2N_HO_Commit does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d122g5480jcAdd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit.pSame as cmt 351.vDPlease refer to contribution 21-07-0320-02-0000-Resource_Definition., p208) Remove reference to table B-10, line 36 (p208) Remove Table B-10.vLeave Table B-10w Principle 2007/12/0709/12/2007 17:02:42 EDTMarkedNo E Barr, John RF DisapproveGUser^General_124a7.4.24cMIH_N2N_HO_Commit does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d122g5480jcAdd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit.pSame as cmt 351.vDPlease refer to contribution 21-07-0320-02-0000-Resource_Definition. cAThe contents of Table B-13 attempts to define Access Technology-specific elements. The information contained in these tables is dated and inaccurate. For instance, the IEEE 802.11 definition does not even incude IEEE 802.11g. It will be impossible for IEEE 802.21 to keep this table current with IEEE 802 amendments, let alone other SDO's such as 3GPP. IEEE 802.21 should provide a generic container that can be defined by the SDO that is responsible for the Access Technology rather than tryinBg to keep this data current. IEEE 802.21 can work with the other SDO's to update the container information as new amendments and protocol versions are produced.d328g5274j}Provide a generic container that will allow Access Technology SDO's be responsible for their own Network Type Representation.v/ Use an OUI to identify the access technology. wDisagree{l) none needed 2007/12/1909/14/2007 23:15:41 EDTNo EMontemurro, MichaelF DisapproveGGeneral Interest E Julka, VibhorF DisapproveGProducer^General_164`14a8.6.3.12cWSuggest alternate wording for improved readability and usage description of the messaged298g5304jReplace text on lines 14-15 with "This message is used by MIHF in the network to respond to an MIH_MN_HO_Candidate_Query request message from a remote MIHF on the MN.wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^General_163`41a8.6.3.11a8.6.3.11er^General_164`14a8.6.3.12cWSuggest alternate wording for improved readability and usage description of the messaged298g5304jReplace text on lines 14-15 with "This message is used by MIHF in the network to respond to an MIH_MN_HO_Candidate_Query request message from a remote MIHF on the MN.wAgree{k) done 2007/12/0709/14/2007 18:36:55 EDTMarkedNo E Julka, VibhorF DisapproveGProducer^General_163`41a8.6.3.11ov21-07-0374-02-0000w Principley deferred.{k) done 2007/12/1909/14/2007 23:44:58 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_200`3aB2.11cjMIFH-ID can be different depending on the access technology. For example, a GSM device could use its IMSI.d330g5272jDefine a separate Registration ID that is used for the lifetime of the registration and create a new MIFH-ID element as a TLV which defines the ID of the entity. The tag should encode MIHF coding (NAI, GRUU, FQDN, IMSI, MIN, PIN), LengthvA8Page 150, secton 8.3.1: Change as follows: "MIHF Identifier (MIHF ID) is an identifier that is required to uniquely identify MIHF entity for delivering the MIH services." Add the following sentence at end of first paragraph: "For example, MIHF-ID may be an FQDN or NAI of the sender of the registration request"8w Principle{k) done 2007/12/1909/14/2007 23:15:41 EDTNo EMontemurro, MichaelF Disapprove~vcontainW&W'W,WWWWWWcontainerWWWWcontainsuWcontextW0WcontributionWWWWWWWWWWWWW6WWWWWWWWWWWW W&W@WWWWWWWWWWcontributions,WcontributonMWWcontrolWcontrollerW W WWWconventionWconvergenceWWcopy WcornerWcorrespondingwWWcosWWWcosisbasedongenericitudefinedclassesVcouldW/W2WW@WcoverageWWcovers&W'WWWWWcpc/Wcpich2WcreatedWcrossedaWcrossingaWcsWcurrent0W5WDWEW@WWWWWWdealWWWdealsWdecWWWdecideWdecidedWdecision<W W4gvdeploymentWWderived^WdescribeWWWWdescribes&W'WWWWWdescribingAWdescriptionW&W'W/W0W2WlWmWWWWWWWdescriptionsWdesirableWdestinationWW WdetailsvW+W,WWdetectWWWdetermineWdeterminedWWdeterminingWdevelopingwWdevice5WWdevicesWdhcpOWdiagramWWWWdiagrams&WdifferenciatorWdifferent5WWW&WAWWWÃ)PVÃ)`UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23Ã32Ã3 1Ã3004E Kim, EunahF DisapproveGGeneral Interest^ Technical_32`11cNMS is used for network management and is to be a stand-alone system. It means that having MIH_NMS_SAP for the interface with the NMS doesn't seem to be appropriate.d640g4962jDelete section 5.6.3.2wAgree{k) done 2007/12/197 23:46:35 EDTMarkedYesE Kim, EunahF DisapproveGGeneral Interest^ Technical_32`11cNMS is used for network management and is to be a stand-alone system. It means that having MIH_NMS_SAP for the interface with the NMS doesn't seem to be appropriate.d640g4962jDelete section 5.6.3.2wAgree{k) done 2007/12/01MarkedYesE Kim, EunahF DisapproveGGeneral Interest^ Technical_32`11cNMS is used for network management and is to be a stand-alone system. It means that having MIH_NMS_SAP for the interface with the NMS doesn't seem to be appropriate.d640g4962jDelete section 5.6.3.2wAgree{k) done 2007/12/01pdecidingWdecisionWWdecisionwsareveredinadhocVdeclinedWdeferWdefer2tonextroundVdeferedWdefined3WVWWWWWdefinesW37kvsectonWsecurityW WWWWWWWsecuriy)Wsecuriyissueswouldbehandledbynewgroup)VseeWvWMWWseems(Wseen5WWselectionWWsemanticsWsendWsenderWWsendingAWsendsWsenseWWsentWWW WsentenceWWWkWWW{W}WWsentencesWseparateWseparately@Wsequence^WaWserver'sWWserviceWW5W@WAWWWWWWWservicesWWWWWsetlWmWW'W W WshallWWWWWWW'WWW W WWshouldWWW,WwWW WEWshowWW Wshowthebitorderinginthefigure V VYvthereisworkbeingcarriedoutbysecuritygrouptoaddress VthereafterW W WWWthereforeW&W'W5WWWWWthereinWWtheseWWWWW&W'W<W]W}WWWWW WWWW WWWWWWWW WthesearepartofservicemanagementcategoryandgroupfeelVthesearepartofservicemanagementcategoryandnotcommanVthesetermsaredefinedinieeedisctionaryVthesetwoparametersareoptionalandlinkswhichdontsuppoVtheyWWW&W'WWWWGWWWWWWthisWWWWWWWWWWWWWWWWWWWW W WWWW W@W]WiWlWmWnWoWuWwWWWWWWWWWWWWW" cATable B.4 "Threshold" which is used extensively for link configurations, looks like there is no real mapping relationship to any of the real-life measurements indicated by LINK_PARAM_TYPE for a specific access technology. One example, if LINK_PARAM_TYPE indicates LINK_PARAM_UMTS for use, let's say with RSCP or CPICH_Ec/Io, the 802.21 THRESHOLD sets a value in the range of 0...65535. However, CPICH_RSCP in W-CDMA would be a reported and measured value in the range -120 to -25 dBm (TS 25.133B). How does the 802.21 THRESHOLD value map to the CPICH_RSCP measurement? Another example, TrCh BLER configurable as a type in 802.21 which in 3G is reported as 1 out of 64 values log10(measurement in the range of 0.00 to 1.0). Would this fit the 0...65535 range ? Moreover, I am almost afraid that the current draft is in a similar situation w.r.t other access technologies. For example, how would THRESHOLD map to the 802.11 Beacon RSSI ? Or is this described somewhere else in the draft and "vallowedWallowsAWalmostEWalongWalreadyWWW&W'WOWWWWWWWWWW WalsoWWWW2WfWWWWWalsolookatcomment384andchangesmadethereinVVamendWamendments,WanWWWWWWAW^WWWWWWWW'WAWWWWWWWWW W WWandWWWWWWWWWWWWWWWWWWWWWWWÃ9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPF- 7cBecurity associations, and which MIH components dependent on these being setup. In addition, 802.21 needs to state the working assumptions (and description thereof) how 802.21 would work in presence of 3GPP-based security mechanisms. The assumption that security in the sense of encryption is self-contained in the MAC may be true for IEEE 802, but not necessarily for 3GPP cellular. Technically, even the AAA necessary to setup MAC encryption is beyond the link layer (a.k.a. EAP etc.). In 3GPPC W-CDMA, encryption for the user plane is done in the RLC with few exceptions, which qualifies as a link layer. However, in GPRS/EDGE, this would be done in the LLC in the SGSN sitting on top of the RLC/MAC stack in the BSS. Does this still qualify as link layer ?d471g5131jIÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6,|preasonWWreceivedWreceives WAWrecommendation9WrefWrefaddedinclause7V6VVline 62, subclause 7.3.1.2.4. Clause 7 is a *service specification*, not a protocol specification. It defines a set of abstract primitives used by layer entities within a given device to intercommunicate. Internal implementation details are not a proper subject for the conformance requirements of a standard. It is not necessary for a conformant device to use internal laB>yering as defined in this (or any) standard; indeed, there may not be any defined or exposed interfaces corresponding to the service primitives defined here. Thus, while this clause may be useful in defining the information manipulated within a system, conformance to this clause is not necessary for interoperability.,d12g5590jjDelete all "shall" statements and conformance requirements for this clause and all service specifications.v!David to provide some explanationwDisagreedGGeneral Interest^ Technical_187`41aB2.6cNTable B-9 should also include PoA location information such as the WWAN CellIDd329g5273j-Add WWAN CellID to the list of entries on B-9pUsed the CELL_ID data type.vThe draft uses Cell-ID in different places to represent PoA location. Use Cell-ID as a way to represent PoA location. Make this change in draft. Make changes to table 8 and table B-9.w Principle{k) done 2007/12/1909/14/2007 23:15:41 EDTNo 09/16/2007 23:51:48 EDTYesata does not match same data in Tale B13 line 8-26d643g4959jCorrect table B14 to match B13pQiaobing, Please verifyvFor table B-13. For a specific Revision Type and define a Technology Standard specific field which could have feature specifc values. Please refer to contribution 21-07-0422-00-00000w Principle{f) pass off to other editor 2007/12/1209/16/2007 23:51:48 EDTYesAgree 2007/11/1809/16/2007 23:51:48 EDTMarkedYes09/16/2007 12:18:13 EDTYesERudolf, MarianF DisapproveGProducer^ Technical_62`17a7.2.3.1cMIH_Event_Subscribe and _Unsubscribe are listed part of Service Management category, but should be part of the Even Service category. This change may affect other sections as well (6.2.1 for example)d510g5092jAI propose to make MIH_Event_Subscribe and _Unsubscribe part of the Event Service rather than part of the generic Service management (like Discovery and Registration with MIH). The reason is that MIH_Event_Subscribe is an integral part of the MIH event notifications mechanism and can anyway not exist on its own when MIH Event Service is not implemented in the MIH entity. General MIH procedures would always start with MIH discovery, followed by optional MIH registration. Subsequently (changeBd now), if an MIH entity has ES implemented, then ES starts with a subscription to events XYZ followed by the "reports" it gets back locally or from a remote peer.QEKwak, Joseph AF DisapproveGGeneral Interest^ Technical_290`36aKcsport services over L3, we can use existing NSAP(Network SAP) and/or TSAP(Transport SAP), depending on the decision of MISHOP WG. As these SAPs are located under the MIHF, integration of MIH_NET_SAP and MIH_LINK_SAP would be a good solution.$d638g4964jIntegrate MIH_NET_SAP and MIH_LINK_SAP into MIH_LOWER_SAP (it can include NSAP and/or TSAP etc) and apply it to all related sections.vby comment 105w Superceded{l) none needed 2007/12/1409/16/2007 23:46:35 EDTYesEKwak, Joseph AF DisapproveGGeneral Interest^ Technical_290`36aKc`36aKc. It causes some duplication of SAPs for the transport services over L2 aÃR sÃR0rÃR@qÃRPpÃR`oÃRpnÃRmÃRlÃRkÃSjÃS iÃS0hÃS@gÃSPfÃS`eÃSpdÃScÃSbÃSaÃT`ÃT _ÃT0^ÃT@]ÃTP\ÃT`[doENatarajan, Kadathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g5067jlRemove the stack marked as "Remote Entity". Remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1909/16/2007 15:23:06 EDTYes athur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g5067jlRemove the stack marked as "Remote Entity". Remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 344. (duplicated){l) none needed 2007/12/1409/16/2007 15:23:06 EDTYes ess of MIH_Net_HO_Candidate_Query command are unclear.d537g5065jQRemove all definitions and avoid mentioning of MIH_Net_HO_Candidate_Query commandw SupercededyRef 238 2007/11/1409/16/2007 15:23:06 EDTYesENatarajan, Kadathur SF DisapproveGProducer^General_42* 0cAVLINK_POWER_UP ambiguous with EGPRS/W-CDMA ? With EGPRS for example, what does establish L2 link mean ? The MN would register with the SGSN to connect to GPRS, but before it actually allocated a PDP context, nothing can be transmitted. A thing like just establishing an RLC/MAC connection doesn't exist for EGPRS. Same logic applies to W-CDMA.Vd478g5124jDefine the link establishment as PDP context activation in the case of 3GPP access technologies (even though this excedes L2, it is the only thing that makes sense).plInstead of "3GPP link type", use "UMTS link type". In order to be consistent with the link type definitions.vkedNo0ERudolf, MarianF DisapproveGProducer^ Technical_184`56cT vtable0W2WWWWWWWtake<WWtakeoutwfaspecifiedparameters/valuesVtakenW WtargetWWEWWtargetpoaofmihn2nhocommitmihnethocommitdonemihmVtargetlinkidentifierWWtargetpoaWWWtechWtechnologiesWW5WWWWtechnologyW1WWWWWWWtemplatepWtendency&W'WWWWWtermFWWWWtermsWtextWWWW W&W'W,W0WWWWWWWWWWWWWtextwillbeupdatedappropriately Vs>jCorrect definition, by replacing "specify the information to be exchanged and the format of the information exchanges" with "specify the interactions between the service user and provider".wAgree{k) done 2007/12/1909/16/2007 06:10:15 EDTYessthe 2 LSB are not used for IE type/ID. Note: LSB is used to allow more efficient computing to allow the masked LSB to be used as desired numeric value withouth shifting. Subsequently, Annex A Table A-1 needs adjustment of tBhe IE ID values.wDeferred 2007/11/1509/16/2007 06:10:15 EDTYes>ELach, Hong-YonF DisapproveGProducer^ Technical_29`22cSub-clause 5.6.1: A serv ice primitive describes an interaction (not limited to the information transfer) between a service provider and a service user at a SAP.d464g5138dÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@#venvisage+W,WequipmentWequivalentWerrorWesailyWessentialWesssWestablish0WestablishedWuWetcWW4Ã5Ã5 Ã50Ã5@Ã5PÃ5`Ã5pÃ5Ã5Ã5Ã6Ã6 Ã60Ã6@Ã6PÃ6`Ã6pÃ6 Ã6 Ã6 Ã7 Ã7 Ã70Ã7@Ã7PÃ7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCÃe0$ivuserWAWiWkWtWWWWuser/subscriberWusers@WWWusesWusing5W}WWutilizationWutra2WvalidW0W^W8WWvalueWWWWW^WaW'W{W WvaluesW^WvendorWWvendorspecificiescanbeusedtospecifythisVverify WkWlWmWtWWWversion@WAWversions/WAWverticalWvery0W&WWviaWvWvivekW W^WmW WWWWvivekorqiaobingpleaseverifymV)ZÃ) YÃ)0XÃ)@WÃ)PVÃ)`UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23ÃT@]A8ELevy, Joseph SF DisapproveGProducer^GeneralcQoS is a critical aspect of MIH, but there are very few normative requirements regarding the use of QoS measures and their uses.d590g5012jProvide additional normative requirements related to the use of QoS in MIH. e.g. - make some; if not all, of the QoS examples of Annex K and related material normative.pThe group disagreed on 588vDuplicate comment as 588w Supercededydeferred{l) none needed 2007/12/1409/16/2007 17:59:40 EDTYes ELevy, Joseph SF DisapproveGProducer^GeneralcGeneralcive.pThe group disagreed on 588vDuplicate comment as 588w Supercededydeferred{l) none needed 2007/11/2609/16/2007 17:59:40 EDTMarkedYes ELevy, Joseph SF DisapproveGProducer^Generalc8{l) none needed 2007/12/1909/15/2007 00:19:40 EDTYesE Kim, YonghoF DisapproveGProducer^ Technical_145`8a8.2.2.1cA What if a source node can not receive any answer even it sent a REQ? and also what if a destination node can not give any response even if it receives a REQ? Therefore, I suggest all states except INIT should have transition to INIT when the transaction time expires. d336g5266jVMake transition to INIT in all states when the transaction time expires, page 145-146.psuperceded by comment #11vFPlease refer to contribution 21-07-0302-01-0000-StateMachineSBCommentswAgree{k) done 2007/12/1909/15/2007 00:02:11 EDTYes E Kim, YonghoF DisapproveGProducer^ Technical_138`13a7.5.1.1a7.5.1.1a7.5.1.1 dynamic information. Refer to contribution, 21-07-0315-00-0000-Dynamic_Information_Support_d337g5265jDDiscuss contribution, 21-07-0315-00-0000-Dynamic_Information_Supportw Principlezvtriggered&W'WWWWWtrueW]W W WWWtrying(WttheWtupleWWWtwoWW'WW WtypeWWWWW WW/W0W3WWW^WaWWpWWtypeieroamingpartnerstypeieroamingpartnerWVtypesWue2Wul/Wumts/W2WÃ7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCÃCÃCdb dmylesandrewfpprovevcommandsarenotsentfrommihftomihusersVcommands/messagesW W WWWcommentWWWGWWWWWWcommentnolongerapplicableduetothestatemachineclauseVcommentaryWWWWWpvgetWgoWWWgoalWgoingWWWWWWgolmieWWgprs2Wgroup WWWWW W)Wgroup's,Wgsm2Wgsm/gprs3WhandleWhandledW)WhandoverWWWWWeWkWuWwW W WWWWWhandoversW<WeWWI vbeWWWWWWWWW WW W'W(W)W@WAWEWGW{WWWWWWWWWWWWWWW WbearingWbeenWW7WaWuWWWW Wbefore WuWWbehaviorWWWbehindWbeing WWbelow0WaWWWWbep2WbetterWWbetweenAWWWAWWWbinary<WWWbitWW/W2WWWW'WW W W Wbit8typeieroamingpartnerremovesWVbitsWWbler2WbodyWbothWEWWbreakuWbroadcastWWbroadcastedWbroadcastsWbtw WbulletW s other editor 2007/12/0709/14/2007 23:15:41 EDTMarkedYes 15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Editorial Editorial Editorial)vMStick with Reference Points. This needs to be done throughout the document. wDisagree{l) none needed 2007/12/1909/16/2007 15:56:25 EDTYes EChaplin, Clint FF DisapproveGGeneral Interest^ Technical_20`8a5.4.2cIn Figure 2, you have numbered the communication links according to the classification scheme starting on line 21 of this page. You might alsoi want to number the entities according to the table starting at line 8d550g5052jQNumber the entities in Figure 2, according to the list starting on page 20 line 8vSThe entities are not really numbered. These are just bullets on page 20, line 8....wDisagree{l) none needed 2007/12/1909/16/2007 15:56:25 EDTYes s s <sE Cypher, DavidF DisapproveGGeneral Interest^ Technical_179`43c'There is no bit for Link_Action commandd155g5447jAdd bit for link action commandwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes sE Cypher, DavidF DisapproveGGeneral Interest^ Technical_179`43c'There is no bit for Link_Action commandd155g5447jAdd bit for link action commandwAgree{k) done 2007/12/1209/13/2007 13:56:26 EDTYes /13/2007 13:56:26 EDTMarkedYes ÃZP ÃZ`ÃZpÃZÃZÃZÃaÃa Ãa0Ãa@ÃaPÃa`ÃapÃaÃaÃaÃbÃb Ãb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@ZESreemanthula, SrinviasF DisapproveGGeneral Interest^General_7`5a3.16c@"MIH protocol entities" is not defined and not appropriate here.d593g5009j"MIH Network entities"vChange: 3.16 MIH discovery protocol A protocol for discovering MIH protocol entities. To 3.16 MIH discovery protocol A protocol for discovering MIH entities.w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^General_5`7a2c#Where are the normative references?d592g5010j Add them.psuperceded by 497vby 497w SupercededyRef Cmt 497 (duplicated){l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes ELevy, Joseph SF DisapproveGProducer^ Technical_33`1cThere are very few (8) "shalls" in section 6.0 MIHF Services and the "shalls" that are present tend to limit the use of the specification instead of specifying required specified performance.d591g50111g5011591g5011.hyRef 114. (duplicated){l) none needed 2007/12/1909/16/2007 15:23:06 EDTYesremove the LINK_TYPE from LINK_DETECT_CONFIG, since the Link Identifier parameter already provided the link type. Adopt contribution 21-07-0306-02-0000-Link-Detection-Update.doc with the following change: replace LINK_TYPE with LINK_TUPLE_ID for the LINK_DETECT_INFO, since the Link identifier is required at the MIH level in order for the MIH user to know which link it was reported from; the change iB[n section 7.3.8.3 is not applicable due to updates in Cmt 428. (Please read editor's note)Iw PrincipleyRef 114. (duplicated){l) none needed 2007/12/1409/16/2007 15:23:06 EDTYes DTYesENatarajan, Kadathur SF DisapproveGProducer^GeneralcMIH event subscription should allow the subscriber to set certain conditions or qualifiers. With that only events meeting those conditions or qualifiers will be notified to the subscriber.d538g5064riber.BELach, Hong-YonF DisapproveGProducer^ Technical_8`27cSub-clause 3.40: A "protocol data unit" (PDU) refers to a packet produced by a protocol for exchange between the protocol's peer entities. The upper-layer user data exchanges between layers at a SAP is referred to as a "service data unit" (SDU).d460g5142jCorrect definition of "protocol data unit". A possible definition is: "Packet produced by a protocol for exchange between the protocol's peer entities."wAgree{k) done 2007/12/1909/16/2007 06:10:15 EDTYesCE Feder, PeretzF DisapproveGProducer^ Technical_127`32c[The description contains "This identifies the current link" for the source link identifier.d459g5143j_Change "This identifies the current link" to "This identifies the source link of the handover".wAgree{k) done 2007/12/1909/16/2007 03:42:16 EDTYes DE Feder, PeretzF DisapproveGProducer^ Technical_129`33_129`33129`33Zg5250j!suggest to move 8.2.2 to an annexpGsuperceeded by comment#116 where group disagreed to move 8.2.2 to annexwDisagree{l) none needed 2007/12/1909/15/2007 22:08:13 EDTNo E Xie, QiaobingF DisapproveGUser^ Technical_124a7.4.24cMIH_N2N_HO_Commit currently does not allow the option of requesting resource reservation at the HO target. This could become a limiting factor in some cases.d351g5251jcadd the option that HO resource reservation can be requested at the recipient of MIH_N2N_HO_Commit.p Done in 277vCPlease refer to contribution 21-07-0320-02-0000-Resource_DefinitionwAgreeyRef 277.{l) none needed 2007/12/1909/15/2007 22:08:13 EDTYes E Xie, QiaobingF DisapproveGUser^GeneralcMIH event subscription should allow the subscriber to set certain conditions to qualify the events, so that only those events that meet the conditions will be reported.d350g5252dOE Xie, QiaobingF DisapproveGUser^ Technical_31cA8MIH_NET_SAP specifies the interface between an MIHF implementation and various local transport stacks on the same device. However, it is unclear what compatability benefits standardizing this interface will bring to the implementation. In the contrary, it would impose needless constraints to the implementation.8d341g5261j3remove all definition and mentioning of MIH_NET_SAPpduplicate with 105wAgreey Ref Cmt 105{l) none needed 2007/12/1909/15/2007 22:08:13 EDTYesE Chin, Kevin AFApproveGGeneral Interest^General_48cMisc comments in .USR file.d340g5262p5Channel Range clarification and example added to B-12v+- reject the tech - accept the 2 editorials{k) done 2007/12/1909/15/2007 18:28:36 EDTNo E Kim, YonghoF DisapproveGProducer^ Technical_193`2aB.2.8 be defined. Refer to contribution , 21-07-0317-00-0000-System_Information_IEd339g5263g5263_IEXEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_32`50a5.7.2cHow does the MN know that it cannot obtain service? I would assume that discovery of L3 service is out of scope of IEEE 802.21.d309g5293jGState that discovery of MIH PoS over L3 is out of scope of IEEE 802.21.vThis is already in the draftw Principle{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYessbe addressed by a the Security group.w Principle 2007/11/2609/14/2007 23:15:41 EDTMarkedYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_32`50a5.7.2cHow does the MN know that it cannot obtain service? I would assume that discovery of L3 service is out of scope of IEEE 802.21.d309g5293jGState that discovery of MIH PoS over L3 is out of scope of IEEE 802.21.vThis is already in the draftw Principle{l) none needed 2007/11/2609/14/2007 23:15:41 EDTMarkedYes?j`There needs to be some form of ensuring that the MN is authorized to obtain the MIH information.v+This will be handled in the Security group.w Principle{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYessher the MN in authorised to obtain that information.d304g5298j`There needs to be some form of ensuring that the MN is authorized to obtain the MIH information.v+This will be handled in the Security group.w Principle 2007/11/2609/14/2007 23:15:41 EDTMarkedYes EDTMarkedYesPJjClarify whether this is a mistake (i.e., add optional to TLV) or it is the function of the remote MIHF to always return the value of the DeviceStatesResponseList, even if one was not requested (add text stating this).v#Make this optional in the response.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes KE Cypher, DavidF DisapproveGGeneral Interest^ Technical_204`59c3Consistency: There is no MIH_N2N_HO_Candidate_Queryd195g5407j$Change to MIH_N2N_HO_Query_ResourceswAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s s edgements." to the end of sentence ending with "&.by the source MIH node."vG Please refer to contribution 21-07-0302-01-0000-StateMachineSBCommentsw Principle 2007/11/3009/14/2007 18:36:55 EDTMarkedYes EDTMarkedYes E Jette, AlanF DisapproveGProducer^ Technical_31cMIH_NET_SAP is used to interface between the MIHF implementation and the transport stacks on a device. This Service Access Point seems unnecessary, adds unneeded constraints on the implementation, and will likely not be tested (validated).d258g5344j$remove MIH_NET_SAP from the standardpduplicate with 105wAgreey Same as 105{l) none needed 2007/12/1909/14/2007 14:42:22 EDTYes E Jette, AlanF DisapproveGProducer^ Editorial_2`12c^Word "han-dovers" is split across 2 lines and the hyphenation appears to be in wrong position.d257g5345jCorrectp+link break set automatically by Framemaker.{l) none needed 2007/12/1909/14/2007 14:42:22 EDTNoE Jette, AlanF DisapproveGProducer^ Editorial_276cAPage XV: The Table of Contents items H.9.1 and H.9.2 wrap around.d256g5346jIf possible, correct{k) done 2007/12/1909/14/2007 14:42:22 EDTMarked:42:22 EDTMarkedRn AvAThis field allows implementations to recognize different versions. Add the following: " This field is used to specify the version of MIH protocol used. 0: Not to be used 1: First Version 2 - 15: (Reserved) The version number will be incremented only when a fundamental incompatibility exists between a new revision and the prior edition of the standard. An MIH node that receives an MIH message with a higher version number than it supports will discard the frame without indication to the sBending MIH node. "w Principle{k) done 2007/12/1909/13/2007 16:03:47 EDTYes BEOhba, YoshihiroF DisapproveGProducer^ Technical_82`37a 7.4.2.1.2cKIt is better to include a list of link identifiers in MIH_Register.request.d204g5398jMAdopt 21-07-0226-00-0000-MIH_Registartion_Nits. This is just an optimization.wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes CEOhba, YoshihiroF DisapproveGProducerGProducerGProduceron field20GE Cole, Terry LF DisapproveGGeneral Interest^General_6a3.1cAI blieve the use of acronyms in the abbreivation to be confusing.d199g5403j Spell out PoAvchange "candiddate PoA" to "candiddate Point of Attachment" Spell out other acronyms in this section as well. Acronyms need to be spelt out the first time they are used, the acronym can then be used subsequently.wAgree{k) done 2007/12/1909/13/2007 15:42:30 EDTNoHE Cole, Terry LF DisapproveGGeneral Interest^General_6`32a3.7cAI blieve the use of acronyms in the abbreivation to be confusing.d198g5404j+Spell out MN and PoA in the definition 3.7.wAgree{k) done 2007/12/1909/13/2007 15:42:30 EDTNoIE Cypher, DavidF DisapproveGGeneral Interest^ Technical_113`53a742112c742112ca742112c13`53`imE Cypher, DavidF DisapproveGGeneral Interest^ Technical_203`9cThe heading of this clause is missing definitions. Why was this draft put forward to Sponsor ballot if it is a known fact that there are missing definitions?d161g5441jRemovep/NETWORK_SECURITY is removed from other comment.wAgree{l) none needed 2007/12/1909/13/2007 13:56:26 EDTYesnE Cypher, DavidF DisapproveGGeneral Interest^ Technical_200`50cNo bit for MIH_Link_Action(s)d160g5442j#Add bit for MIH link action commandwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes 13:56:26 EDTYesnE Cypher, DavidF DisapproveGGeneral Interest^ Technical_200`50cNo bit for MIH_Link_Action(s)d160g5442j#Add bit for MIH link action commandwAgree{k) done 2007/12/1209/13/2007 13:56:26 EDTYes /13/2007 13:56:26 EDTMarkedYes F DisapproveGGeneral Interest^ Technical_200`50cNo bit for MIH_Link_Action(s)E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_71`14a7391cSentence is missing punctuationd136g5466j Add periodwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTMarkedIHF? There seems to be some confusion on whether the local and remote MIHFs are paired or whether the MIHF user is registered with its local or remote MIHF.d137g5465jClarify the function of the Register feature (i.e., does it pair local and remote MIHFs or does it pair MIHF Users with local or remote MIHFs?)vChange as follows on pg 83 line 27 " Registration request code. Depending on the request code, the MIH User can choose to either register or re-register with the remote MIHF "wAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedYes E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_71`14a7391cSentence is missing punctuationd136g5466j Add periodwAgree{k) done 2007/12/0709/13/2007 13:56:26 EDTMarkedePENoens, Richard HF DisapproveGProducer^ Technical_150`60a8.4.1cBMIH Protocol header is of fixed length, as indicated in figure 27.d103g5499jJChange figure 26 to show MIH Protocol Header has fixed length of 8 octets.psuperceeded by comment #454wAgree{k) done 2007/12/1909/11/2007 17:47:21 EDTYes ENoens, Richard HF DisapproveGProducer^ Technical_106a7.4.19cMThe Purpose and usefulness of MIH_Net_HO_Candidate_Query command are unclear.d102g5500jREither remove the MIH_Net_HO_Candidate_Query command or better describe its usage.vs usage.vupercededy Ref Cmt 238{l) none needed 2007/12/0709/11/2007 17:47:21 EDTMarkedYes 11/2007 17:47:21 EDTMarkedYesrUEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cThere should be a way to indicate that the network itself is mobile. For example, consider a network on a ship, airplane or bus.d85g5517jAdd this capability.vLThe use case for this is not clear. How would the user use this information?wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the country and regulatory domain in which the network is operating.d84g5518jAdd this capability.pY- added country code - regulatory domain can be encoded inside the operator ID IE string vAdd another IE for this.w Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYes r^ Technical_52`48a6.5.5.2cVThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the 802.11u HESSID.d83g5519jAdd this capability.HEMyles, Andrew FF DisapproveGProducer^ Technical_6`57a3c.3cAThe reference model for 802.11 is incorrect. The model shows that MIHF is connected to the MLME SAP. In 802.11, primitives are provided to the SME and the MIHF should have its interface to the SME. The SME is responsible for layer 2 transition between APs and should not provide, for example, a link-down indication everytime the STA re-associates to a new AP. Rather the MIHF should only receive a link-down indication when the STA become disassociated from the ESS (or is about to become disaBossociated from the ESS). This is because MIH is concerned about roaming between networks and NOT L2 transition.]d76g5526j:Correct the figure and the resulting reference model text.v4Incorporate the new reference diagram from TGu draftw Principle 2007/11/2609/11/2007 17:46:47 EDTMarkedYesEMyles, Andrew FF DisapproveGProducer^ Technical_6`57a3cS//EHeubaum, Karl FFApproveGProducer^ Editorial_32`33a5.7.2cSThere's an extra period at the beginning of ".There are two kinds of transport...".d66g5536j/Change to "There are two kinds of transport..."pSame as Cmt 44{k) done 2007/12/1909/11/2007 11:55:31 EDTNoProducer^ Editorial_32`33a5.7.2cSThere's an extra period at the beginning of ".There are two kinds of transport...".d66g5536j/Change to "There are two kinds of transport..."pSame as Cmt 44{k) done 2007/12/0709/11/2007 11:55:31 EDTNooucer^ Editorial_32`33a5.7.2cSThere's an extra period at the beginning of ".There are two kinds of transport...".d66g5536j/Change to "There are two kinds of transport..."pSame as Cmt 44{k) done 2007/12/0109/11/2007 11:55:31 EDTMarkedNoorkedNoperiod missing at the end of "...layer 3 handover".d65g5537j Change to "...layer 3 handover."o "...layer 3 handover."EEmmelmann, MarcF DisapproveGAcademic^ Editorial_32`33a5.7.2c"Sentence starts with a period (.).d44g5558jDelete leading period{k) done 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_31`41a5.6.2.6cThere is no need to make an exception for 3GPP and 3GPP2 and specify for this technology a speperate SAP. The correct interface would be MIH_LINK_SAP.d43g5559jDelete section 5.6.2.6v]Do not delete this section. Please make changes as per contribution 21-07-0414-02-0000-3GSAP w Principle{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYes ss5E Seifert, RichF DisapproveGGeneral Interest^ Technical_149`16a8.2.3.4cThe MIH protocol relies on the underlying mechanisms (I.e., the lower layers) to provide fragmentation and reassembly. However, many such underlying technologies do not provide this function, e.g. IEEE 802.3.d16g5586jThe type is a choice, thus containing only one elementd17g5585j?Define Device States Response List as LIST (DEVICE_STATES_RSP) wAgree 2007/12/0109/04/2007 16:19:39 EDTMarkedYesE Seifert, RichF DisapproveGGeneral Interest^ Technical_149`16a8.2.3.4cThe MIH protocol relies on the underlying mechanisms (I.e., the lower layers) to provide fragmentation and reassembly. However, many such underlying technologies do not provide this function, e.g. IEEE 802.3.d16g5586jg 'jvAA Protocol Implementation Conformance Statement (PICS) Proforma cannot contain any information that is not already present in normative text. Therefore including a PICS Proforma would be redundant. Duplication of information within a standard has a tendency to cause inconsistencies. A PICS Proforma covers only conformance, not interoperability. Clause 8 describes the formats of messages used to exchange information. The description of when these messages are used are defined in claB-use 7 since they are triggered by primitives.wDisagreey$Ref cmt 488. superceeded by Cmt 10.{l) none needed 2007/12/1909/16/2007 07:13:12 EDTYes rYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_38`63a6.3.4.1cbDefine "link synchronous events" rather than saying what they are not and just providing examples.d600g5002jNeeds a definitionp,clarified by changes from 21-07-0430-00-0000wDisagree{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYeskedYeskedYes∃≃⊃⍃⎃⏃␃⒃⩃⪃⭃ⳃⶃ⸃⹃⼃⾃ǃȃ׃ۃ܃݃߃ #%.0279:;<=>?BCDFGHIJKLNOPQRSTUVWXYZ[\]^_`abcdefghijklmnoqrstuvwxyz|〃ぃゃッ㄃ㅃ㈃㊃㋃㌃㎃㏃㕃㖃㙃㤃㦃㧃㫃㷃ɃуԃՃփكڃۃ\uESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_41`3a6.3.5cA`Desciption on Link_handover_imminent and its MIH counterpart indicate that the L2 somehow decides that handover is necessary. This goes against the very first MIH design principle set forth in section 5.2.1. Who makes handover decisions? Is this event equivalent to a parameter change if configured or a predictive event that the link may be down soon?`d601g5001jClarifyp"change made per 21-07-0430-00-0000v/Please refer to contribution 21-07-0430-00-0000w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_38`63a6.3.4.1cbDefine "link synchronous events" rather than saying what they are not and just providing examples.d600g5002jNeeds a definitionp,clarified by changes from 21-07-0430-00-0000wDisagree{l) none needed 2007/12/0209/16/2007 21:41:08 EDTMarkedYesYes+>EColban, Erik AF DisapproveGUser^ Technical_31`45 Technical_31`45_31`45ǃǃǃǃǃǃǃǃǃǃǃǃǃ̓̓̓̓΃΃΃΃σσσσσσσσσЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃЃ҃ӃӃԃԃԃԃՃՃՃՃՃՃՃՃՃՃՃՃՃՃՃփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփփcdefghijklmnoqrstuvwxyz|〃ぃゃッ㄃ㅃ㈃㊃㋃㌃㎃㏃㕃㖃㙃㤃㦃㧃㫃㷃ɃуԃՃփكڃۃsE0ERudolf, MarianF DisapproveGProducer^ Technical_184`56c features and does not provide the flexibility to indicate all existing combinations, as defined in 3GPP 25.306. Modify the Wireless UMTS Network Description as follows: Network: Wireless W-CDMA FDD Link Type: 23 Revision: (Revision) Bit 0: Rel-99/Rel-4 Bit 1: Rel-5 Bit 2: Rel-6 Bit 3: Rel-7 Bit 4: Rel-8 Bit 5-19: (Reserved) (Features) Bit 20: HSDPA Bit 21: HSUPA Bit 22: MIMO DL Bit 23: MIMO Bit 25: DL HOM Bit 26: UL HOM BBQit 27: CPC Bit 28-63: (Reserved) Acronyms could require definition in section 4 ?w Superceded{l) none needed 2007/12/1209/16/2007 07:13:12 EDTNo 0ERudolf, MarianF DisapproveGProducer^ Technical_184`56c4`56cg5274j}Provide a generic container that will allow Access Technology SDO's be responsible for their own Network Type Representation.v/ Use an OUI to identify the access technology. wDisagree 2007/11/18agree 2007/11/18w0ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_143`9a8.1cw...using the MIH protocol messages specified in this section. Is that a correct reference? or should it be a subclause.d222g5380jyChange 'section' to 'sub-clause' as used in other places. ( Another reference is in page 217 line 58 RDF Schema content.)v changed 'section' to 'subclause'ld comply.pAgreed, but since text in the body may still change and hence the order in which the annexes are referenced may change too. Will do this in the last version.{h) defer to next round 2007/12/1309/13/2007 16:42:41 EDTNo 0ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_143`9a8.1cw...using the MIH protocol messages specified in this section. Is that a correct reference? or should it be a subclause.d222g5380jyChange 'section' to 'sub-clause' as used in other places. ( Another reference is in page 217 line 58 RDF Schema content.)v changed 'section' to 'subclause'subclause'WXEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_34`44a6.2.5cHow does registration provide authorization to access services? All registration does is place the peers in a state where they can exchange information.d310g5292jIncorporate a security method during the registration process to provide authorisation or remove this sentence from the draft because there is no authorization.v/This will be addressed by a the Security group.w Principle{l) none needed 2007/12/19o, MichaelF DisapproveGGeneral Interest^ Technical_34`44a6.2.5cHow does registration provide authorization to access services? All registration does is place the peers in a state where they can exchange information.d310g5292jIncorporate a security method during the registration process to provide authorisation or remove this sentence from the draft because there is no authorization.v/This will be addressed by a the Security group.w Principle{l) none needed 2007/11/26{lnoneneededVVV VVVneededWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW#W&W'W(W+W/W5W7W8W=WGWIWJWUW[W\W]W_WlWqWvWxWyW}WWWWWWWWWWWWWWWWWWccWSuggest alternate wording for improved readability and usage description of the messaged297g5305jReplace text on lines 41-43 with "This message is used by a MIHF on the MN to communicate to a MIHF in the network, of an intent to initiate handover"wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^General_163`11a8.6.3.10cWSuggest alternate wording for improved readability and usage description of the messaged296g5306jReplace text on lines 11-12 with "This message is used by MIHF on the MN to respond to an MIH_Net_HO_Candidate_Query request message from a remote MIHF in the networkwAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^General_162`55a8.6.3.9cWSuggest alternate wording for improved readability and usage description of the messaged295g5307295g5307295g5307`OE Sood, KapilF DisapproveGGeneral Interest^ Technical_7`42a3.26cIClause 5 is supposed to be general 802.21 architecture description. However, in multiple locations in this clause, there are references to more specific events in this specification, while there are other sentences that are too generic. Eg. Generic description of handovers in 5.1.2, generic QoS descriptions in 5.1.4, and so on.Id269g5333jRecommend re-writing Clause 5 much like that written for IEEE 802.11. This Clause should be very precise in its scope, and should be the "executive summary" of functions defined in this standardwDisagreey deferred. 2007/11/2609/14/2007 16:50:16 EDTYesE Sood, KapilF DisapproveGGeneral Interest^ Technical_7`42a3.26c^ Technical_7`42a3.26cLZ lcAThe location used in the information model is for the PoA. For 802.11 networks this is not the correct information for the following reasons: 1. The mobile node should not care about the location of the PoA. The mobile should only care about whether RF coverage is obtainable at a specific location. 2. Many operators will be unwilling to provide actual location (e.g., latitude and longitude) for a PoA. As such, there will be no location information in many MIIS databases.d80g5522jChange the location information such that it is providing the RF coverage area of the network and not the location of specific PoAs. Note that this is not just a comment about Figure 19, but has ramifications for other clauses in the document.v by comment 88w SupercededyRef 88{l) none needed 2007/12/1909/11/2007 17:46:47 EDTMarkedYes 50`1a6.5.3c[jDe-emphasize MIHF Discovery as separate MIH service management function. Remove 6.2.3 and possibly merge the discussion into general MIH protocol discussion in subclause 8.p}- no longer talks about MIHF discovery as a service in 6.2.1 - removed 6.2.3 - merged old 6.2.3 material into section 8.2.3.5w Principle{k) done 2007/12/1909/15/2007 22:08:13 EDTNo ]+_+E Koh, BenjaminF DisapproveGProducer^General_40a6.3.5cEThere is a lack of a positive predictive MIH event MIH_Link_Going_Up.d227g5375j?Introduce a "MIH_Link_Going_Up" type positive predictive event.vvDifficult to envisage use cases and usefulness of this event. Need some motivation and other details to consider this.wDisagree{l) none needed 2007/12/1909/14/2007 02:24:47 EDTYes ,E Koh, BenjaminF DisapproveGProducer^General_39a6.3.4.1cBThere is a lack of a positive predictive link event Link_Going_Up.d226g5376j;Introduce a "Link_Going_Up" type positive predictive event.vvDifficult to envisage use cases and usefulness of this event. Need some motivation and other details to consider this.wDisagreeyRef 227. (duplicated){l) none needed 2007/12/1909/14/2007 02:24:47 EDTYes 0a6.3.5cEThere is a lack of a positive predictive MIH event MIH_Link_Going_Up.d227g5375ing_Up.d227g5375H:EOhba, YoshihiroF DisapproveGProducer^ Technical_199`56aB.2.10.2c)The default MIME_TYPE value is incorrect.d212g5390jsChange the second sentence of Definition column to: "If MIME_TYPE is omitted, MIME type "application/xml" is used."wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTNo oMIME_TYPE value is incorrect.d212g5390jsChange the second sentence of Definition column to: "If MIME_TYPE is omitted, MIME type "application/xml" is used."wAgree{k) done 2007/11/1809/13/2007 16:03:47 EDTMarkedNo6W=j@GA@cRvAC^nD@E@jF@G@IcA2J@jL@N@Oj~QjAS`WEZc\j_wccfwjc?k@Xlpm@o@`uQ*pl59WlanguageWWlast/WWWlayerWWWlayersWleftWlessWWWlineWlinkWWW W0WWWW WlWoWzWWWWWWWlinkbreaksetautomaticallybyframemaker VlistWWOWWW^W WtWWWlocalxW}WWlocationWWlogicalWlongerWW(WWWWWWWWWWlongetWmYWmacW WWWWWWWWzWmihfW$WW2WWmiisW-WmiisdefinesaunifiedmechanismtothehigherlayerentitieVmissing6WmnWWmobileWmodification6WmodifiedW(Wmodifiedfig11tobemoreconsistentwithtextVmoreWWmoveWn2nnWoWnameWnaming6Wnas-port-type3WnecessarilyWneed6WVW2WWW[g5488jBinvestigate if this capability is needed and how to best implementpSuperceed by 615.vAdopt contribution 21-07-0305-02-0000-Event-Subscribe-Update.doc with the following change: remove the LINK_TYPE from LINK_DETECT_CONFIG, since the Link Identifier parameter already provided the link type.w PrincipleyRef 615.{l) none needed 2007/12/1909/12/2007 02:37:36 EDTYes ist.doc Issue#1{l) none needed 2007/12/0709/12/2007 02:37:36 EDTMarkedYes should allow the subscriber to set certain conditions or qualifiers. With that only events meet those conditions or qualifiers will be notified to the subscriber.d114g5488jBinvestigate if this capability is needed and how to best implementpSuperceed by 615.w Supercededy621-07-0361-00-0000-SB Comment Issues List.doc Issue#1{l) none needed 2007/12/0109/12/2007 02:37:36 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_144a8.2.2cThe ACK mechanism is Optional to use and since the State diagrams arre applicable only in this optional case move this section to the Annex.d524g5078jMove section 8.2.2 to Annexpgroup disagrees with commentwDisagree{l) none needed 2007/12/1909/16/2007 13:58:33 EDTYes E Gupta, VivekF DisapproveGGeneral Interest^ Technical_141a7.6caMIH_NMS_SAP tries to provide details of specific implementation which adds no value to this spec.d523g5079jdDelete all references to MIH_NMS_SAP from the spec. Delete references to Network management as well.wAgreeyRef 106 (duplicate){l) none needed 2007/12/1909/16/2007 13:58:33 EDTYes E Gupta, VivekF DisapproveGGeneral Interest^ Technical_137a7.5caMIH_NET_SAP tries to provide details of specific implementation which adds no value to this spec.d522g508022g5080522g5080this spec.d523g5079 }{jinprogresskWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWG YpupdatedaWmWWWIWqWWWupdatedfig7tomatchthediagramintgudraftVupdatedforresponseandconfirmprimitivesmVupdatedinsubclause7checkedinsubclause8Vupdatedsection8IVupdatedsubclause7needtoupdate8andannex1andtlvassVupdatedtheelementsinsteadofbitmapsit'senumerated2Vupdates2WOWupdatesformihmnhoqueryresourceresponseandmihn2nhoOVurlWuse0WWWW-WzWWusemakinguserextensionstomiisschema-VusemihlinkactionszVzVzVzVzVzV EDTMarkedNoEMeylemans, MarcFApproveGProducer^ Editorial_43a6.4.2cFig 18 - Local and remote 'stack' are not represented symmetrically. Remote MIHF does not 'sit' between Remote Lower Layers and Remote MIH Userd373g5229jlSwitch location of Remote MIHF and Remote Lower Layers in Fig 18 to make it symmetrical to the Local 'stack'{k) done 2007/12/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_41`41a6.4.1c/2 sentences (line 41 and 52) say the same thingd372g5230jDelete one of the 2 sentences{k) done 2007/12/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ EditorialaN/AcThroughout whole document - Incorrect use of 'indefinite articles' like 'a' and 'an'. E.g. the document uses 'an MN' or 'an MIHF' or 'an MIH PoS', this should be corrected to 'a MN', 'a MIHF' and 'a MIH PoS'd371g5231j5Correct use of 'a' and 'an' throughout the whole specp"an MN, an MIH, an HIF are correct.c.EMeylemans, MarcFApproveGProducer^ Editorial_5`1a2c#No normative references are listed.d366g5236jJList all normative references or if there are none, then indicate as such.{k) done 2007/12/1909/16/2007 02:47:09 EDTNoEMccann, StephenF DisapproveGProducer^ Technical_6`10a3.2cpWouldn't it be useful to reference previously defined definitions for these terms, rather than re-defining them.d365g5237jhNormative references should be considered such as the base standards of the media specific technologies.vby 497w SupercededyRef 497{l) none needed 2007/12/1909/16/2007 01:46:33 EDTYes EMccann, StephenF DisapproveGProducer^ Technical_5`8a2c;Are there really no normative references for this standard?d364g5238jhNormative references should be considered such as the base standards of the media specific technologies.psuperceded by 497vby 497w Supercededy Ref Cmt 497{l) none needed 2007/12/19E Xie, QiaobingF DisapproveGUser^General_316cAnnex M.6 seems redundant and not adding much value because similar materials have been covered in the example call flows in Annex H and Information Service examples ind357g5245j remove M.6wAgree{k) done 2007/12/1909/15/2007 22:08:13 EDTYes E Xie, QiaobingF DisapproveGUser^General_282c,Annex J does not add much value to the spec.d356g5246356g5246dedydeferred{l) none needed 2007/12/0509/16/2007 01:46:33 EDTYes E Xie, QiaobingF DisapproveGUser^General_316cAnnex M.6 seems redundant and not adding much value because similar materials have been covered in the example call flows in Annex H and Information Service examples ind357g5245j remove M.6wAgree{k) done 2007/12/0509/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^General_282c,Annex J does not add much value to the spec.d356g5246356g5246356g5246u` EStephens, Adrian PF DisapproveGProducer^ Technical_151`15a8.4.1.1cI haven't yet found any statement about conventions regarding endianness of frame format drawings. Are the ver(4) bits the least significant or the most significant of the first octet.d5g5597ave no normative definition.'d6g5596jI recommend a conventions subclause before B.1.1 that defines unambigously: 1. The ordering of bits in an octet (most or least significant is B0?) 2. The ordering of octets in a multi-octet integer (is the lowest numbered octet least or most significant?)vby 576w Superceded{l) none needed 2007/12/1208/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_151`15a8.4.1.1cI haven't yet found any statement about conventions regarding endianness of frame format drawings. Are the ver(4) bits the least significant or the most significant of the first octet.d5g55975g5597reENatarajan, Kadathur SF DisapproveGProducer^ Technical_63cA[MIH_NMS_SAP defines the interface between an MIHF implementation and a local Network Management System stack. Depending on the nature of the device, this local NMS stack may vary or may not even exist. Standardizing this interface brings no benefit to the implementation.To the contrary, it would impose needless constraints to the implementation.[d534g5068j3remove all definition and mentioning of MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/1909/16/2007 15:23:06 EDTYes n exist. Standardizing this interface brings no benefit to the implementation.To the contrary, it would impose needless constraints to the implementation.[d534g5068j3remove all definition and mentioning of MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/1409/16/2007 15:23:06 EDTYes s s nYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_282aAnnex JcHDelete Annex J as it is redundant and not required in the specification.d519g5083jDelete Annex JwAgree{k) done 2007/12/1909/16/2007 13:58:33 EDTYes E Gupta, VivekF DisapproveGGeneral Interest^ Technical_224aAnnex FcHDelete Annex F as it is redundant and not required in the specification.d518g5084jDelete Annex FwDisagree{l) none needed 2007/12/1909/16/2007 13:58:33 EDTYes E Gupta, VivekF DisapproveGGeneral Interest^ Technical_221aAnnex EczMove References (Bibliography) to section 2 Normative References. Why is this buried at the end instead of being in front.d517g5085juMove all normative references to section2. Consider moving this part to somewhere earlier in draft and delete Annex Ete Annex Ete Annex EhEMontemurro, MichaelF DisapproveGGeneral Interest^ Editorial_153`14a8.6cIt is very difficult to cross-reference the sections where TLV items are defined from where they are specified in the protocol messages.d322g5280jxIn the tables that define protocol messages. Include a reference to a clause where the data type, list, etc. is defined.pX- data type section is updated for better organization. See if this issue still remains.{h) defer to next round 2007/12/1909/14/2007 23:15:41 EDTMarkedYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_170`16a8.6.4.1c:The text states that there "should" be at least one query.d321g5281jWI believe there has to be at least one query. Therefore the statement should be "shall"v4Update to: One and only one type shall be specified.w PrincipleyRef 563, Ref 326{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYes:41 EDTMarkedYes  disapprove„S< cATable 14: IP is not a transport protocol. Simply stating that one should use an IP-based transport is to unspecific as it allows to use any (even a self-written, non standardized) transport protocol to be used. Be more specific regarding allowable transport protocols or be precise and state that an IP-based network architecture is assumed. But in the latter case, the title of the third column is not correct.d60g5542j&Clarify or rephrase / be more precise.psuperceded by comment #59vRemove section 8.2.3.1w PrincipleyRef Cmt 59. (superceded){k) done 2007/12/1909/10/2007 07:08:58 EDTYes /10/2007 07:08:58 EDTMarkedrotocols or be precise and state that an IP-based network architecture is assumed. But in the latter case, the title of the third column is not correct.d60g5542j&Clarify or rephrase / be more precise.psuperceded by comment #59v by comment 59w Superceded{k) done 2007/11/3009/10/2007 07:08:58 EDTMarked\j@Expand the block to properly include the link and MIH primitiveswAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes ]E Cypher, DavidF DisapproveGGeneral Interest^ Editorial_268`34c$Consistency PoS, POS, Pos, Pos, etc.d177g5425jChange Pos to PoSwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes ^E Cypher, DavidF DisapproveGGeneral Interest^General_267`36cnFNA is used, which is correct for the original RFC 4068. However the newest draft RFC 4068 changed FNA to UNA.d176g5426jXIf this annex is going to contain h.7.2 on PMIPv6, then it should update its FMIPv6 datawAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes _E Cypher, DavidF DisapproveGGeneral Interest^ Technical_267`54cuThe Link_Action.request is sent to MAC_WiMAX, however the corresponding Link_Down.indication comes from the MAC_WLAN.d175g5427j#Change to arrive from the MAC-WiMAX MAC-WiMAX MAC-WiMAX MAC-WiMAX cAThis is with regard to the functional architecture (Fig. 4) that shows the MIH-LINK-SAP as being the only interface between MIHF and Link Layer, and the fact that MIH-LINK-SAP primitives are defined. It is unlikely for implementors of separate access technologies to implement the MIH-LINK-SAP defined in this document. It is more likely that the MIHF implementor will implement a mapping function that maps existing native primitives provided by each link layer to the MIH-LINK-SAP primitives.B The document also provide no provision for error reporting if a particular MIH-LINK-SAP primitive cannot be mapped using any natively available primitives.d245g5357jqvrel-5/Wrel-6/Wrel-7/Wrel-8/Wrel-99/rel-4/WrelateWrelatedWkWrelevantWreliableWreliesWremainingWremedywWWremotewWWWremotely<WremoveWW,WEWWWWWWWWEWWWWWWWremove802.15fromfigure1andfrompage4line-14VVremoveapinparenthesisVremovecurrentlinkidentifierandaddbothsourceandtargeEVremoveipconfigstatusfromisquerybutleaveitforotherVremovesection8.2.3.1VVremovethedefinitionofhigherlayersVremovingWrenameW2Wrenamemihnon-posnetworkentitytomihnon-pos3.21VrenewalWreplaceW2W@WW' replacebullet5withtheproposedbulletsandaddsometextVreportaWreportedWreportingpWreportsW W WWWrepresent2W^WWjEJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_15`36a5.1.7ctWhat is the relationship between this and what is already/is being specified in 802.1 for the provision of security?d252g5350jShow the relationship.vSection 5.1.7 has been deletedw Principle{l) none needed 2007/12/1909/14/2007 08:30:59 EDTYesswhat is already/is being specified in 802.1 for the provision of security?d252g5350jShow the relationship.vSection 5.1.7 has been deletedw Principle{l) none needed 2007/11/2609/14/2007 08:30:59 EDTMarkedYesEJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_15`16a5.1.5ceSounds like you are attempting to re-define mechanisms that already exist in IEEE Std 802.1AB - LLDP.d251g5351jTEither use 802.1AB to achieve this result or demonstrate why 802.1AB isn't suitable.v802.21 deal with networks that do not fall within the scope of IEEE 802 (such as 3GPP/3GPP2). 802.1AB CANNOT handle these other networks.{l) none needed 2007/12/1909/14/2007 08:30:59 EDTYesst in IEEE Std 802.1AB - LLDP.d251g5351jTEither use 802.1AB to achieve this result or demonstrate why 802.1AB isn't suitable.v802.21 deal with networks that do not fall within the scope of IEEE 802 (such as 3GPP/3GPP2). 802.1AB CANNOT handle these other networks.{l) none needed 2007/11/2609/14/2007 08:30:59 EDTYesv802.21-specific,W802.3W83W88W95<W98<WWaWWWWWWWWWWWWWWWWW&W'W2W<W@WAWIWWW^WaWeWiWlWmWwWWWWWWWWWWW WW W(WAWWWWWWWWWW WWalistofavailableresourceforeachlinklVmVaprotocolimplementationconformancestatementpicsproform&V'VVVVVatargetpoaofmihn2nhocommitmihnethocommitdonemihVaccount<WeWaccuratelyWackWack-reqW W Wack-rspWacknowledged WacknowledgementWWW WacknowledgmentW WacronymGWacronyms/W2WGWacrossWWWactionWW WactionsW0WuW}WWadaptionWaddWWSME Julka, VibhorF DisapproveGProducer^ Technical_44`19a 6.4.3.1.1t successful (i.e. STATUS is not set to success) that the remaining non essential TLVs should not be present (in the case of MIH messages from a remote entity this can save on resource usage on the airlink). Suggest we add text to the Response Link Event List column to clarify that this is not included if the status indicates failure. This is a global comment (applies to numerous places in the specification). If comment is acBMcepted NW can bring in explicit text changes to be made for remaing sections.;d281g5321jbAdd text "This is not included if STATUS is not set to code 0 (success)" to the description columnvAll primitivies in section 7 would need to be examined carefully for this behavior. This is applicable for MIH Protocol messages.wAgree 2007/12/0109/14/2007 18:36:55 EDTMarkedYesE Julka, VibhorF DisapproveGProducer^ Technical_44`19a 6.4.3.1.1AupinWWWWWWWinthisdraftwewillstillkeepitthiswaysothatwewon'VincludeWincompatibilityAWinconsistenciesRWinconsistencyxWincrementedAWindependentWindicates WWindication{W|WWAWWindications WinfoWWinformationWWWOWWWinformative9Winitiated WWinsideWinsteadW0W2WWWinsteadof3gpplinktypeuseumtslinktypeinordertobe0VinsteadusemacaddressinnethocommitforconsistencyforVintWintendedKWLWMWNWinterestedWinternet3W3WW2WAWWWWWit'sWitemsWWits3W2WWkenichiiWjWkenichiiswillmodifythefigurebasedthisrevisioniVjVkeptnWoWknow2WWknows2WlWl126Wl17Wl2Wl246Wl346Wl386WVvthenetworkcontrollerprovidesalistofcandiddatenetworkV V VVVthenetworkmihfentitymayhavefqdnasit'sidentifierVtheqosisspecifiedforaccesslinkandisnotendtoendVthequeryresourceeportflisnotalistVthespecificationshouldcontainalltherequiredtextandr,Vthesuggesteddefinitionbelowisnotveryclear0VthetermshallaspertheieeestandardsstylemanualdatedV' UcA)Figure 22: The state diagram in Figure does not match the description in the text. More specifically, the state diagram does not show that retransmission shall happen only twice. Note that the IEEE SA has ruled that state diagrams are normative, which means that the state diagram must be correct.)d568g5034j6Update the state diagram to match the text descriptionpjsuperceded by comment #11 - See Alice email for additional concern about BITMAP(9) on page15 of contri 302v21-07-0302-00-0000w Principle{k) done 2007/12/1909/16/2007 15:56:25 EDTYess veb^„bjeffreetonya disapprove disapprove8 disapprove9/P9kwakjosepha 8 disapprove:;;approve disapprove<: ERudolf, MarianF DisapproveGProducer^ Technical_34`31a6.2.5cAHow does an MIH entity determine if a pairing request from another MiH entity is to be admitted or not authentication-wise ? For example, there doesn't seem to be any link level indication for the MIH entity to check or have reported back if the underlying link has been authenticated or associated such that at least implicitly "authentication" can be deduced from the link status for wireless links. Then, in the specific case of L2 MIH over Ethernet, is any PoA trying to contact another oneted or not authentication-wise ? For example, there doesn't seem to be any link level indication for the MIH entity to check or have reported back if the underlying link has been authenticated or associated such that at least implicitly "authentication" can be deduced from the link status for wireless links. Then, in the specific case of L2 MIH over Ethernet, is any PoA trying to contact another one @c} j"cAkCvA@pj@F@jA.!@ j?jj@H@Dp@cAj@c@@)!"@$@%jA&jAC}'@jB(@gj)@m+cY,vA.c/vA0@cAsvA*1@j2@'vA3@G4@j5@j6jD7@FcBmjA-C9@:@c<jvB=@-cA*jA$>@sju?@@@j?A@vAvAGc H@JcAK@Y L@aM@ j`N@OcRjVc~W@Yj[cB]cA|^G_@U`d&+E Xie, QiaobingF DisapproveGUser^General_42`5a6.4.1c_Figure 16 is confusing by showing two unrelated stacks. Showing one stack would be good enough.d347g5255joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.wAgreeqdyRef 105{l) none needed 2007/12/1909/16/2007 23:46:35 EDTMarkedYes AP provides transport services over the data plane on the local node and MIH_LINK_SAP specifies the interface between the MIHF and lower layers. When transport services over L2 are used, MIH_NET_SAP becomes equal to MIH_LINK_SAP and is mapped to the real media dependent SAP such as LSAP or MLME_SAP that doesn't belong to data plane. It causes some duplication of SAPs for the transport services over L2 aB6nd also shows the inconsistency for the role of MIH_NET_SAP. For transport services over L3, we can use existing NSAP(Network SAP) and/or TSAP(Transport SAP), depending on the decision of MISHOP WG. As these SAPs are located under the MIHF, integration of MIH_NET_SAP and MIH_LINK_SAP would be a good solution.$d638g4964jIntegrate MIH_NET_SAP and MIH_LINK_SAP into MIH_LOWER_SAP (it can include NSAP and/or TSAP etc) and apply it to all related sections.vby comment 105w Superceded(9 cARThe actual adaptation of the MIH_LINK_SAP was previously stated not to be within the scope of 802.21 but within the scope of the underlying technology. Nevertheless, Section 5.5.5 introduces MIH_3GLINK_SAP as an MIH specific SAP which is also the case for Fig. 9 in which the SAP is gray shaded and hence illustrated to be part of 802.21.Rd40g5562jUse the name MIH_LINK_SAP. Possibly include any "adaptation" layer / SAP and state (if appropriate) that no additional protocol enhancements are required but that existing service primitves can directly mapped to the MIH_LINK_SAP.v$Plesae refer to contribution 414-02 w Superceded{l) none needed 2007/12/1909/10/2007 07:08:58 EDTYes sYwDisagree 2007/11/2609/10/2007 07:08:58 EDTMarkedYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_27`45a5.5.5ceAvcurrentlinkidentifieWd7.1WdataW WWW0W<WWWdatatypeOWdatedWWdealWWWdealsWdecWWWdecidekWWdecidedWdecision<W WW W WourceIdentifer may be included if required wherever appropriate.vby 397w Superceded{j) in progress 2007/12/0709/16/2007 13:58:33 EDTMarkedYes ress 2007/12/0509/16/2007 13:58:33 EDTYessN implicitly know which link is currently being used.d525g5077jDelete CurrentLinkIdentifier from all MIH Handover primitives. A SourceIdentifer may be included if required wherever appropriate.vby 397w Superceded{j) in progress 2007/12/0109/16/2007 13:58:33 EDTMarkedYes, 2007/12/1909/10/2007 07:08:58 EDTNoEEmmelmann, MarcF DisapproveGAcademic^ Technical_32`41a5.7.2cAbThe three items make a normative assumtion or even standardize how MIH messages should be carried via a SPECIFIC technology. This is not within the scope of the standard. Apart from this, listing only a few technologies includes always the danger of missing other current or upcoming technologies. The nice thing about .21 is its technology independence.bd45g5557jIDelete the three items or (preferably) move them to an informative annex.pdeleted the 3 itemswAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYes ssGE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_186`42aB.2.5cQThis is the maximum data transfer rate, not the maximum information transfer rated528g5074jReplace "information" by "data"{k) done 2007/12/19provided for both cases.d529g5073jpDiscuss specific solution aspects for both for single radio/dual radio case and provide solution for both cases.wDisagree 2007/11/2609/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_186`42aB.2.5cQThis is the maximum data transfer rate, not the maximum information transfer rated528g5074jReplace "information" by "data"{k) done 2007/11/26oth cases.wDisagree 2007/11/2609/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_186`42aB.2.5cQThis is the maximum data transfer rate, not the maximum information transfer rated528g5074jReplace "information" by "data"{k) done 2007/11/26iERajkumar, AjayF GProducer^ Technical_131`57cReference to wrong messaged388g5214j)Change N2N_HO_Complete to MN_HO_Complete.wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_131`64cZResource retention should be included in the message only when the original PoS is sendingd387g5215jA#Include "Resource Retention" only when the message is sent in the direction from the original to target PoS. This means that it should be in the request/indication when this message is originated from the original PoS and should be in the response/confirm when originated from the target PoS#v#v from the original to target PoS. This means that it should be in the request/indication when this message is originated from the original PoS and should be in the response/confirm when originated from the target PoS#v} &jAFirst, introduce something like a PICS somewhere in the Annex, that groups MIH functionality in blocks (Services, Primitive Categories, Transport options) such that an actual protocol-conformance statement can be based on it. Then, as a function of access technology combinations implemented on a MN, define sets of comformant functionality groupings. One example, a MN that has both Ethernet and 802.11 (like a laptop), MIH used for session continutity, must support L2 MIH transport (but doesBn't need L3 option), it must support both IS and ES (but CS is optional), it must support the following list of media-specific SAPs XYZ and the following list of local and remote primitives XYZ. Another example, a MN that has both 802.11 and EGPRS, must support L3 IP trasnport option (but doesn't need L2), must support the following SAPs and the following list of primitives. Or, define above minimum MIH protocol sets per access technology if supported in the MN. Like, any MN that has an 8047@j3remove all definition and mentioning of MIH_NET_SAPpduplicate with 105vby 105w Supercededy Ref Cmt 105{l) none needed 2007/12/1909/16/2007 15:23:06 EDTYesEVan Leeuwen, Richard MF DisapproveGProducer^ Technical_203`9aB.2.17c+Definition for NETWORK_SECURITY is missing.d532g5070j(Add the definition for NETWORK_SECURITY.vHDelete NETWORK_SECURITY_IE Can be added later if definition is availablew Principle{k) done 2007/12/1909/16/2007 14:02:28 EDTYes EVan Leeuwen, Richard MF DisapproveGProducer^ Technical_150`61a8.4.1cFigure 26 shows the MIH protocol header has a variable length, however Figure 27 shows the MIH protocol header has a fixed length of 8 octets.d531g5071jFCorrect Figure 26, showing the MIH protocol header has a fixed length.psuperceded by comment #454wAgree{k) done 2007/12/1909/16/2007 14:02:28 EDTYes s s % cBossociated from the ESS). This is because MIH is concerned about roaming between networks and NOT L2 transition.]d76g5526j:Correct the figure and the resulting reference model text.p3- updated fig. 7 to match the diagram in TGu draft v4Incorporate the new reference diagram from TGu draftw Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYes s am from TGu draftw Principle{c) instructions unclear 2007/12/0509/11/2007 17:46:47 EDTMarkedYes {vchannel1W2WWcharacterizeWchargeiWchoice^WchoicesW W WWWchoosekWWclarificationWclarifiedW@WclarifiesWclarifyWWWuW}WWclarifythisaslinkauthenticationVclarifyingWWclassWclassesWWclassificationWclauseW&W'WWWWWWWWWclearW0WWcloselyWcmtWWWWWWco-locatedWcodeWcodesWWWcodingWcolumnW0WcombinationWcombinations/Wcombined4Wcombines/WcomeWcommandWiWxWyWWcommandsWWW W WWWWjvvplesaereferto21-07-0396-01-0000VVVVplesaerefertocontribution414-02VplrWT {noneWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WWWWWWWW#W&W'W(W+W/W5W7W8W=WGWIWJWUW[W\W]W_WlWqWvWxWyW}WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWW W!W"W#W$W&W(W)W*W+W,W5W8WmWpWWWWWWWWWWWWWWWWW/ ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_39`15a6.3.4.1c6Failure to transmit data is not same as the lost data.d599g5003jSuggest rewriting this section.p/cleaned up the language to remove the confusionv 21-07-0433w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_39`30a6.3.4.1cIt is incorrect to say that the transmission status can be verified on by higher layer timeouts. Currently, all link layers provide indications for successful transmission of the frames in the L2 buffer.d598g5004j correct itp/cleaned up the language to remove the confusionv 21-07-0433w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYes s s -emmelmannmarc, disapprove„. disapprove/!„/emmelmannmarc. disapprove„0 disapprove1zH„1emmelmannmarc0 disapprove vADisagree with removing the section. 1) It is never agreed upon to limit MIHF to only control planes (as shown in Figure 1, Figure 4, Figure 5, etc). 2) Even though most media types already have their own native mechanism for similar indication, this MIH link primitive is a generic primitive. The value for having a generic link primitive that can be mapped to a media-dependent one is well established (the reason behind 802.21 MIH_Link_SAP definition). wDisagree{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_72`1a7.3.10cA.This seems to assume a nonexistent packet identifier common at both higher layers and link layers. TCP/IP layer uses its own sequence numbers which are not visible to MAC layers while MAC layer uses its own sequence numbers for link acknowledgements. What packet identifier is supposed to be used here?.d610g499210g4992approve„ cALines 38-52: The statistical parameters listed on these lines are not descriptive of any channel per se. These statistics are representative of a channel operating at a specific link data rate. That is these parameters can only characterize a channel as a function of a given operating rate. The entire channel is characterized by the set of these parameters for all available link data rates for the particular media. This complicated scenario is true for any set of digital transmission paramBeters which will always be rate dependent. There is a significant advantage and simplification possible if linke are characterized by analog parmeters like SNR or RSNI.d631g4971jEither correct this list to indicate that these statistics are only valid on a given channel at a given operating data rate, or simplify the approach to use analog parameters to characterize a link.pBy 21-07-375-01v*Agreed. Text to be supplied by Nada GolmiewAgree{k) done 2007/12/19YesEMeylemans, MarcFApproveGProducer^ Editorial_96`22a 7.4.12.1.2c!missing bracket in UNSIGNED_INT2)d375g5227j-add missing opening bracket - UNSIGNED_INT(2)p same as 221wAgree{k) done 2007/12/1909/16/2007 02:47:09 EDTNo o 2/0709/16/2007 02:47:09 EDTMarkedNo vpleaserefertocontribution21-07-0375Vpleaserefertocontribution21-07-0414-02-00006Vpleaserefertocontribution21-07-0430-00-0000Vpleaserefertocontribution21-07-0430-00-0000-lVpleaserefertoresolutionof429\VpleaserefertotgudraftcontributionVpleaseseecontributon21-07-0302-00-0000MVVpleaseverifykVlVplesaeWWWWW ppageWWWpagenumberinthetextisstructuredanddoesnotstartfroVpage15WparagraphWWparamnWoWparameterWWparameterdeletedincmt619VparametersWOWgWWparamtersWpartnersWWWWtersWOWgWWparamtersWpartnersWWWWWWWWrepresent1specialcaseVperiodicallyWphraseWphrases<WpleaseW_WWpleaseaddcostothe4abbrevationsandacronymsVpleasecheckagain_VVpoaWWWWWpoasyteminformationieisdefinedatpage48l59VpointWposWpossWpossibility2WpossibleWpresenceWprimitiveWWprimitives@WpriorAWprobably WWprobablyshoulddoadraftreviewalso VprobingWproblem(WproposedWWprotocolWAWprovideWqiaobingW 2WNWDT^ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`49a6.5.5.2cMIH Event Subscription, as defined, has limited capability for practical uses. It should be possible for event subscription to set parameters for individual events that are being subscribed for. The parameters will be correspondingly be applicable only for that specific event. As an example, link-detect may result in inefficiency due to reporting of not so relevant networks. It should be possible to subscribe to see only specific network identifiers.d606g4996j Please see the contribution #305vby 615w Superceded 2007/12/0109/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`49a6.5.5.2c615w Superceded 2007/12/0109/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`49a6.5.5.2cqESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_72`54a7.3.11cAWhy would the link layers(MAC) make handover decisions? Even for intra-technology handovers, there must be logical entities outside of MAC that make these decisions, e.g. SME in 802.11. Presently, there are no interefaces defined between MIHF and these logical entities.d612g4990jDiscuss.{l) none needed 2007/12/0709/16/2007 21:41:08 EDTMarkedYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_72`54a7.3.11cAWhy would the link layers(MAC) make handover decisions? Even for intra-technology handovers, there must be logical entities outside of MAC that make these decisions, e.g. SME in 802.11. Presently, there are no interefaces defined between MIHF and these logical entities.d612g4990jDiscuss.pprove 2007/12/0109/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveDisapprove|3ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_125`16a7.4.24.2.2 and otherscSeveral locations where "MAC address" is used instead of a genric link id or address. MAC is a 802 term, should use a genreal term, which is already defined.d621g4981j correct itpPChanged in section 7. Annex C table update PoA TLV: MAC_ADDRESS -> LINK_TUPLE_IDvmTarget PoA of MIH_N2N_HO_Commit, MIH_Net_HO_Commit (done) ( MIH_MN_HO_Commit TargetPoA deleted in Cmt 619)wAgree{k) done 2007/12/1909/16/2007 21:41:08 EDTYes s , which is already defined.d621g4981j correct itpPChanged in section 7. Annex C table update PoA TLV: MAC_ADDRESS -> LINK_TUPLE_IDvmTarget PoA of MIH_N2N_HO_Commit, MIH_Net_HO_Commit (done) ( MIH_MN_HO_Commit TargetPoA deleted in Cmt 619)wAgree{k) done 2007/12/0709/16/2007 21:41:08 EDTMarkedYes rk identifiers.d620g4982bout the PoA specifics. Should include network identifiers.d620g4982:^v21-07-0317-01-0000-sW21-07-0320-02-0000 W21-07-0320-02-0000-rWWWW21-07-0321-00-0000W21-07-0373-01-0000@W21-07-0374-02-0000Ã21-07-0375W21-07-0396-01-0000WWWW21-07-0414-02-00006W21-07-0414-02-0000-3W21-07-0422-00-00000W21-07-0424-00-0000421-07-0430-00-0000W21-07-0430-00-0000-lW21-07-0433᷃22/W227,WWÃ'phÃ'gÃ'fÃ'eÃ(dÃ( cÃ(0bÃ(@aÃ(P`Ã(`_Ã(p^Ã(]Ã(\Ã([Ã)ZÃ) YÃ)0XÃ)@WÃ)PVÃ)`UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23Ã32Ã3 1Ã300nDEOhba, YoshihiroF DisapproveGProducer^ Technical_80`57a 7.4.1.3.1c>Supported IS Query Parameter Type List should not be optional.d202g5400jRemove "(Optional)" from Supported IS Query Parameter Type in MIH_Capability_Discover.{response,confirm} primitives and MIH_Capability_Discover response message.wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes s DisapproveGProducer^ Technical_80`57a 7.4.1.3.1c>Supported IS Query Parameter Type List should not be optional.d202g5400jRemove "(Optional)" from Supported IS Query Parameter Type in MIH_Capability_Discover.{response,confirm} primitives and MIH_Capability_Discover response message.wAgree{k) done 2007/12/0709/13/2007 16:03:47 EDTMarkedYes opt 21-07-0226-00-0000-MIH_Registartion_Nits. This is just an optimization.wAgree{k) done 2007/11/1809/13/2007 16:03:47 EDTMarkedYes vnewWW Wnewly WnextWWnmsWnoWW]WaWWW&WpWWWWWW W WnochangeneededpVnochangerequiredthisistrueinprinciplebutthesearei]Vnocontributionavailable&Vnolimitonnumberofacknowledgedmessages VnolistofiesprovidedVnodeiW}WW'WAW W Wnon-posWnon-zeroWWWnorWnormativeWWWWWWWWWWWWWW/W0W2W5WAWOW]WuWwWWWWWWW&W(W8WAWWWWWWWWWWWW WnoteWWW^W WWWnothing5WWnullsWnumberWWWAW W WnumberedWobjectivesWobtainWobtainedWobtainsWofWWWWWWWWQvrfWrfc{WroamingWWroamingpartnersieroamingpartnerieWVroamingpartnersoperatoridWVrouterWOWrp1Wrp2Wrscp2WrsnWrspWrssi2Wrxlev2Wrxqual2WsWWsafeguard WsameWWWpnumberWAWnumbers3WWobservdWoccurrenciesOWoctetsHWofWWWWW WWW0W2WEWWW^WWWWWWWWWWWW WWAWOWWWWWWWWWWoldWWold/new WonWWW WWWWWonce3W WoneWonlyWW WxW}WWAWWWonlyanmihfcapablenetworkentityshallrespondwithamihVoperation WoperatorWoptimizationWoptionalWgWoptionalparametersaddedtonethocandidatequeryresponsegVorWnWoWWorder0WW/WtWorganizationWotherWmWoutWWWouterWover Woverview$Wp103Wp103l17VpacketWpacketsWpageWWWWWWWWW0 vableWabortkWaboutWWaboveWaW W WWWWWWabstractWabstractionAWac WEWWacceptWWaccept21-07-0321-00-0000Vacceptthe2editorialsVacceptedWaccessWWWWWOWWWWWWWWaccessibleuWaccomplishWaccomplishedwWaccount<WeWaccuratelyWackWack-reqW'W W Wack-rspWacknowledged WacknowledgementWWW WacknowledgmentW'W WacronymGWacronyms/W2WGWacrossWWWactionWvWW WactionsW0WuWvW}WWadaptionWaddWW disapprove€`S€ disapprove`€natarajankadathurs disapprove€1G€ disapprove1€natarajankadathurs disapprove€t€ {editorWWWgroup%WhWWW/WhdefertonextroundVVV/ViWitodo!V!V!V!V!V!V!V!Vi!WWitodo!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!V!VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVsVtVuVwVxVyVV Vin6W<WVWWW3W6WWWinputWinstructionsgWWj6W<WVWWW3W6WWWjinprogressWccnFNA is used, which is correct for the original RFC 4068. However the newest draft RFC 4068 changed FNA to UNA.d171g5431jXIf this annex is going to contain h.7.2 on PMIPv6, then it should update its FMIPv6 datawAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes dE Cypher, DavidF DisapproveGGeneral Interest^ Technical_257`19cpTwo blocks have the same "Handover Completion and Candidate PoS becomes new serving PoS" What is the difference?d170g5432jMerge the two blocks into onewAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes eE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_256`19c!There is no MIN_MN_Commit.requestd169g5433jMIH_MN_HO_Commit.requestwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes fE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_252`19c!There is no MIN_MN_Commit.requestd168g5434jMIH_MN_HO_Commit.requestit.requestit.requestit.requestw?ESreemanthula, SrinviasF DisapproveGGeneral Interest^General_68`44a7.3.6.2cIs this a wish list or does any Link layer actually support or intend to support this functionality? The parameters "Time interval" and "Confidence level" are based on vendor specific implementations.d608g4994jDiscuss.v7/12/0709/16/2007 21:41:08 EDTMarkedYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^General_68`44a7.3.6.2cIs this a wish list or does any Link layer actually support or intend to support this functionality? The parameters "Time interval" and "Confidence level" are based on vendor specific implementations.d608g4994jDiscuss.v insufficient for network selection.d609g4993j+Please see the contribution #306 - CHANGE#1pFinished in Cmt 615vby 614. Same resolution appliesw Superceded{l) none needed 2007/12/0109/16/2007 21:41:08 EDTYeswESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_70`27a7.3.8cJJust providing MAC addresses of PoA is insufficient for network selection.d609g4993j+Please see the contribution #306 - CHANGE#1pFinished in Cmt 615, the user/subscriber of this event). MIHF and link layer just pass and return it and do not need to understand the syntax and semantics. 2) Consider adding a primitive to show explicitly that this packet identifier is passed along with the outbound data from the upper layer. w Principle{j) in progress/Typo on page 72 line 6, "form" should be "from" 2007/12/0709/16/2007 21:41:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_70`27a7.3.8cJJust providing MAC addresses of PoA is insufficient for network selection.d609g4993j+Please see the contribution #306 - CHANGE#1pFinished in Cmt 615o be used here?.d610g4992jRemove Packet IdentifiervyppdfWperWWpercentageWpercentagetypewon'tbeabletorepresent1specialcaseVperformanceWperiodicallyWpersistentWphraseWplacedWplease_WWpleasecheckagain_VVpoaWWWWWWpoasyteminformationieisdefinedatpage48l59VpoasWpointWposWpossWpossibleWpredictiveWpresenceWpresentWprimitiveWKWLWMWNWW WprimitivesmWprincipleWpriorAWprobably WWprobablyshoulddoadraftreviewalso VprobingWproblem(W^WpropertiesWproposedWWWprotocolWAWWprovideWWWWWWWWWWWWWWdeWWW 2W3WqiaobingithinkitwillbebetterifyoucanupdatethiscoVqiaobingthemihfalwaysknowsaboutthestatusanddescript2V8jreplace "may not" with "need not" or wording with similar intent - e.g. "... reliable, the MIFH may choose not to use the acknowledgement mechanism"vm"When the MIH transport is reliable, the acknowledgement mechanism is optional based on carrier requirements.wAgree{k) done 2007/12/1908/24/2007 10:31:14 EDTNo E Bajko, GaborF DisapproveGProducer^General_193`24aB-12c;Parameters DCD, UCD, SIB, system_parameters are not definedd648g4954jdefinevEPlease refer to contribution 21-07-0317-01-0000-System_Information_IEw Principle{k) done 2007/12/1909/17/2007 18:08:47 EDTYesE Bajko, GaborF DisapproveGProducer^General_186cTable B-8, supported_LCP values was present in version 6.0 It disappeared from version 7.0 without a comment to remove it!!!!!!!!!!!!!!!!!!!!!! why? should be put backd647g4955jput back the textp3Change the type from UNSIGNED_INT(1) to enumerated.wAgree{k) done 2007/12/192] E Golmie, NadaF DisapproveGGovernment/Military^ Technical_98cAThe request contains DeviceStatesRequest parameter of type DEVICE_STATES_REQ. The type is a bitmap allowing to request different state information. However the response contains Device States Response List of type DEVICE_STATES_RSP. The type is a choice, thus containing only one elementd17g5585j?Define Device States Response List as LIST (DEVICE_STATES_RSP) wAgree{k) done 2007/12/1909/04/2007 16:19:39 EDTYes s Device States Response List of type DEVICE_STATES_RSP. The type is a choice, thus containing only one elementd17g5585j?Define Device States Response List as LIST (DEVICE_STATES_RSP) wAgree{k) done 2007/12/0709/04/2007 16:19:39 EDTMarkedYes *j$Get rid of this type by removing it.vpRemove IP_CONFIG_STATUS from IS query, but leave it for other cases (CS). This is already the case in the draft.w Principle{l) none needed 2007/12/1909/12/2007 17:19:19 EDTNo emporary statuses? If the information is outdated, that may cause trouble.d125g5477j$Get rid of this type by removing it.JhE Bajko, GaborF DisapproveGProducer^ Technical_210`21aB.2.7cAA STA with IPv6 interface does not need to know whether the link supports stateless, stateful or manual configuration. Configuration always starts with stateless and may continue with stateful or may fall back to require manual in case no unique interface ID generation was possible.d124g5478j;Remove bits 11, 12 and 13 from IP_CONFIG_METHODS type name.pthe idea for having this information is to enable a way of optimization where the STA no longer need to do this typical step-by-step probing and as a result the IP configuration at the target after a HO can be sped up. wDisagree{e) editor disagrees)Resolution changed from Agree to Disagree 2007/12/1909/12/2007 17:10:19 EDTNo E Bajko, GaborF DisapproveGProducer^ Technical_208`3ab.2.6ree{e) editor disagrees)Resolution changed from Agree to Disagree 2007/12/0709/12/2007 17:10:19 EDTMarkedNo l {kdone;V<V=V>V?V@VAVBVCVDVEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVnVoVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVWWWWWW"W#W$W)W+W,WAWWWWWWWWWWWWWWWWWWlnoneneededVVVVVVVVVVVOE Kim, YonghoF DisapproveGProducer^ Technical_148`13a8.2.2cThere is no transaction state diagram for broadcast MIH_Capability_Discover message. Refer to contribution, 21-07-0316-00-0000-MIH_Capability_Discoveryd338g5264jODiscuss contribution, 21-07-0316-00-0000-MIH_Capability_Discovery and adopt it.psuperceded by comment #11vFPlease refer to contribution 21-07-0302-01-0000-StateMachineSBCommentswAgree{k) done 2007/12/1909/15/2007 00:21:32 EDTYes s chineSBCommentswAgree{k) done 2007/12/0709/15/2007 00:21:32 EDTMarkedYes |ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_121`44a7.4.23 and othersc9There is no LINK_ACTIONS datatype, it must be LINK_ACTIONd625g4977j correct itwAgreeyRef 141{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_118`34a7.4.22cNetwork in most cases does not care about the specifics of link actions. The link action set should be optional. In worst case, the parametes inside must be optional for this case.d624g4978j Please see the contribution #308pDAdd the Target Network Info TLV and List of Target Network Info TLV.vPlease refer to 21-07-0308-01 (Also refer to contribution 320-01 which has changes for resource reservaton scheme to the same primitive)w Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_184`22aTable B4 case.d624g497809/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_187aB.2.5cWill the different COS_ID be represented consistently across different link types? If not, then maybe a linkType should be added along with COS_ID to clarify the class of service identifier explicitly for that link typed527g5075jClarify if COS-ID are consistently represented across all links or are they on a per link basis. If on a per link basis add, the linkType to COS_ID.v+COS is based on generic ITU defined classeswDisagree{l) none needed 2007/12/1909/16/2007 13:58:33 EDTYes s s oveGGeneral Interest^ Editorial_111`16a 7.4.20.3.2c6Font of parameters in list needs to be made consistentd526g5076jGFix the font. This is there is several other places in draft. Fix this.{k) done 2007/12/0709/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_108a7.4.20"3ERudolf, MarianF Disapprovest does not represent the most important measurements required from the MN as specified in 3GPP 25.215 Rename the list as LINK_PARAM_WCDMA_FDD and replace the Description list by the following elements: Bit 0: CPICH RSCP Bit 1: PCCPCH RSCP Bit 2: UTRA carrier RSSI Bit 3: GSM carrier RSSI Bit 4: CPICH Ec/No Bit 5: Transport channel BLER Bit 6: UE transmitted power Bit 7-255: reserved Similarly, the LINK_PARAM_GSM list does not represent the most important measuBsrements required from the MN as specified in 3GPP 25.008 Merge the LINK_PARAM_GSM and LINK_PARAM_GPRS lists into a single one (e.g. LINK_PARAM_GSM_GPRS) and replace the list by the following elements: Bit 0: RxQual Bit 1: RxLev Bit 2: Mean BEP Bit 3: StDev BEP Bit 4-255: reserved Acronyms could require definition in section 4 Table B-13 may also need to be updated. aw Principle{i) to do 2007/12/1209/16/2007 07:13:12 EDTYes 3ERudolf, MarianF Disapprove GcQOS_LIST is not a link parameter type, Single values have been used for specifying the setting/getting of individual parameters. QOS_LIST is a collection of parameters containing value not types.d455g5147jsIt is not clear what the intent was for this change. Perhaps it was supposed to be a new type called QOS_LIST_TYPE.vSmae as comment 432w Superceded{l) none needed 2007/12/1909/16/2007 03:38:14 EDTYes ed 2007/12/1209/16/2007 03:38:14 EDTYes s none needed 2007/12/0709/16/2007 03:38:14 EDTMarkedYes SCE Sood, KapilF DisapproveGGeneral Interest^ Technical_26`26a5.5.3cAThe MIHF Scope function block is incorrectly placed in contect of the 802.11 architecture diagram. To quote 802.11-2007 Clause 10.1 "The exact functions of the SME are not specified in this standard, but in general this entity can be viewed as being responsible for such functions as the gathering of layer-dependent status from the various layer management entities (LMEs), and similarly setting the value of layer-specific parameters." All MLME functions are genarated 802.11 SME, and as suchg of layer-dependent status from the various layer management entities (LMEs), and similarly setting the value of layer-specific parameters." All MLME functions are genarated 802.11 SME, and as suchnd as suchHE Feder, PeretzF DisapproveGProducer^ Technical_150`60c'MIH header is a fixed length (8 bytes).d454g5148j5Remove reference to "variable octets" from the figurepMreplaced reference to ''(variable octets)" with "(8 octets)" in the figure 26wAgree{k) done 2007/12/1909/16/2007 03:38:14 EDTYes IE Feder, PeretzF DisapproveGProducer^ Technical_150`40ctransaction ID is "unique among all the pending transactions between a given pair of the sender and receiver" which is incorrect as both sides may generate the same transaction ID.d453g5149jChange to "unique, on a per direction basis, among all the pending transactions between a given pair of the sender and receiver".pgroup disagreedv$Dont need on "a per direction basis"wDisagree{l) none needed 2007/12/1909/16/2007 03:38:14 EDTYes JE Feder, PeretzF DisapproveDisapproveDisapprove09/16/2007 03:38:14 EDTMarkedYes JE Feder, PeretzF Disapprove%g5217j-Change valid range to 0: success, 1: failure.wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo ERajkumar, AjayF GProducer^ Technical_174`20c What does [N=8*i, i=1,2,&] mean?d384g5218jChange description to "A BITMAP(N), where N must be a multiple of 8, is made up of an N/8 octet values where Bit 0 is the most significant bit of the first octet"wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo 5}pemailWemphasized Wemphasizedthattheuserhasfullcontrolovertheamountof Vemty^WenableWencodedWendWWendsWenhancement*WentirelyWentitiesWentityWWWenumeratedW2WenvironmentWestablishedWetc3WeventWtWWWexampleWW WDTMarkedYes vpexamples)WexistsAWexpectedWexperimentalWexplicitWextend4WextensionWextensions-WfaOWfieldWAWfigW*WWfig12ismeanttoshowtheregistrationflowsomeenhanceme*VfigureHWfinalWfinishedWfinishedincmt615VfirstAWWfixWfixtheparameternamealsoVfixedRWxWfixedinconsistencyxVflow*WfollowingW WAWWWWforWWWWOWmWWWWW WW4WWWWWWforgetWforumWframeAWframemaker WframesWfromWWWWWW WW#W(W+W9WWWWWmWWWfull WfunctionWfundamentalAWfunnyEWfurthurWg4Wgeneral Wgenerated WWWWWWWgreedtoremovetheversionfieldandagreedtoadAV6ryjadd missing "list" to the namewAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes page 173, Table A-1: TYPE_IE_LIST_SUPPORTED_LCPd149g5453jadd missing "list" to the namewAgree{i) to do 2007/12/1209/13/2007 13:56:26 EDTYes o do 2007/12/0909/13/2007 13:56:26 EDTYes s s jReplace text on lines 55-56 with "This message is used by a network MIHF to communicate to a MIHF on the MN, of an intent to initiate handover"wAgree{k) done 2007/12/1909/14/2007 18:36:55 EDTNo E Julka, VibhorF DisapproveGProducer^General_152`32a8.5cAThis section is duplicate of the information that is given in 6.5.5. Suggest we delete this section and add a note to section 8.6 which provides a reference to section 6.5.5. Alternatively we can simplify the text in section 6.5.5 and retain the text in 8.5d294g5308j\Add text "See section 6.5.5 for Message parameter TLV encoding" after line 14 in section 8.6v}Sections 6.5.5 and section 8.5 address similar issue. Please update these section and remove any redundancy (refer to them). w Principley Ref Cmt 299{l) none needed 2007/12/1909/14/2007 18:36:55 EDTNoE Julka, VibhorF DisapproveGProducer^ Technical_151`40a8.4.1.1cpusenohyphenVusedWWWWAWWWusedcellidalreadydefinedVusedthecelliddatatypeVusefulWuser WW-WWuser'sWusing WvagusWvalidWWWWvalueWvalues3WOWvariableHWverifiedQWversionW/WAWveryWvia WwWw-cdma3Wa3W3W3WwWw-cdma3W3W3W3W3WoWwhich/WWwhoseWwillW3WW/W2WAWiWjWWwimaxWwithWWWWW3WHWWWWWW W$WAWWWWW WwithoutWAWwon'tWworkWWwouldWW2WwsaWx-refWyouWv0WW/W2WAW1WWWWWW/W0W2W3W<WWWAWWW1furtherclarifythatthepacketidentifierisacontainerVl0psentence(WWWWWWsequence^WWserver3WOWservice$WWWservicesWWset WWshallWshouldW WWWshow*WsideWsimplyWsinceWKWLWMWNWW/WWWsmeWsoWWsome*WRW^WWsourceWWspacesWspecWspecialWspecified3WWWspecifyAWspedWstaWWstackWstandardAWWstandards9WWstartWstartingWstateWWstatusWstayWstdWstep-by-stepWstillWWWW/WstringWstructure^We^W^W^W^W^Wblea-1tableb-19doneina-1stringWstructure^W^W^W^WVstructure^W^W^WP5pbutW2WnWoW/WWbutkeptthesameparaminn2nresponse/confirmasitisuncnVoVbutnochangemadetothephraseprotocolstackVbyWWWWWWWWWWWWWWW WWW#W(W+W3WWWWWc-2WcanWcandidateWcapabilityWcapableWcasenWoWWchangeWWW6W{W|W/WWchange3serviceserviceVchangemadethroughoutthedocumentVchangedWWchangedtexttoVchangedtoVchangesWclarifyWclearer*WcmtWWWWWcmt30deletedthedefinitionVcommentWnWoWWWW>WWWWcommentorWcommitWconcernedWconfigurationWconsistencyWconsistentWW3WconventionWcorrectWcorrespondingWcoverWcrossWW6 cADon't see the need for this field. The destination MIHF will either send an explicit ack message (MIH ACK) or MIH response message. In either case the transaction ID will be the same as was received in the MIH Request message. The transaction ID can be used by the source to correlate the messages. Note that receipt of a MIH ACK or the MIH response is implicit indication that the destination received the MIH request. Suggest we make this a reserved field and remove reference to use of ACK-RBSP bit from sections 8.d293g5309jA[Replace ACK-RSP row in Table 15 with: Field name = Reserved. Size = 1. Description: This field is intentionally kept reserved and set to '0'. Additionally we need to update figure 27 and replace "Ack Rsp" with "Reserved". Also we need to remove references to setting of Ack-RSP field from 8.2.2.2 lines 41, 46 and 50; 8.2.2 line 61; 8.2.1 line 63.[pgroup diagreedvvApgroupdisagreeswithcommentVVV Vh WhandoverWWhandovers WWhas WW(WWW WWWhavingWhence/Where3WhessidWWhessidhasbeenaddedasanexampleVheterogeneousWhifWhigherWAWWhoKWLWMWNWOWgWxWWWW WWhocWhostingWhowW4WhoweverW4 cAWhen a time out occurs in COMPLETED state, we should not report an error. When the source enter this state, it starts a timer in case a re-transmitted MIH response is received due to a lost MIH ack sent by the source node. If no re-transmitted MIH response is received then the destination has successfully received the ACK and the transaction should end. In this case no error has occurred and therefore should not be reported.d290g5312j-From line 65 delete text "and reports error."plERajkumar, AjayF GProducer^ Technical_112`5765ces in each of the lists (LINK_POA_LIST and QOS_LIST) be the same; Combine Preferred Candidate Link List, Available Resource Set, IP Configuration Methods, DHCP Server Address, FA Address, Access Router Address and IP Address Information Status into a single type and return a list of that type; Further, if resources on a candidate are dependent on a particular PoA then all of these parameters need to be on a link and PoA basis.w Principle 2007/12/0709/16/2007 03:08:31 EDTMarkedNo lERajkumar, AjayF GProducer^ Technical_112`5765co be on a per candidate basis thus they should be lists as well (however, care is needed to map the server addresses to the IP configuration methods since not all will be present)d419g5183jsent)d419g5183jEMeylemans, MarcFApproveGProducer^ Editorial_105`17a 7.4.19.1.1cuThe MIH_Net_HO_Query.request primitive is invoked by an MIH User on a network node. Make this clear in this sentence.d377g5225jChange text to 'The primitive is invoked by a MIH User on a network node to communicate to a peer MIH User about its intent of handover initiation.'wAgree{k) done 2007/12/1909/16/2007 02:47:09 EDTNo o proveGProducer^ Editorial_105`17a 7.4.19.1.1cuThe MIH_Net_HO_Query.request primitive is invoked by an MIH User on a network node. Make this clear in this sentence.d377g5225jChange text to 'The primitive is invoked by a MIH User on a network node to communicate to a peer MIH User about its intent of handover initiation.'wAgree{k) done 2007/12/0709/16/2007 02:47:09 EDTMarkedNo J1 09/14/2007 14:42:22 EDTYes s cMIH_NMS_SAP is used to interface between an MIHF and a local Network Mgmt System (NMS) stack. The local NMS stack should be left up to the implementation.d259g5343j$remove MIH_NMS_SAP from the standardpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/0709/14/2007 14:42:22 EDTMarkedYes f the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagree 2007/12/0109/14/2007 14:42:22 EDTYes E Jette, AlanF DisapproveGProducer^ Technical_63cMIH_NMS_SAP is used to interface between an MIHF and a local Network Mgmt System (NMS) stack. The local NMS stack should be left up to the implementation.d259g5343j$remove MIH_NMS_SAP from the standardpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/0109/14/2007 14:42:22 EDTYesSECheng, Yuu HengF DisapproveGGeneral Interest^ Technical_220`1aDc/(Kenichi) Comment in the schema is not correct.d443g5159jRemove tag and the contents.wAgree{k) done 2007/12/1909/16/2007 03:35:02 EDTNo o sapproveGGeneral Interest^ Technical_220`1aDc/(Kenichi) Comment in the schema is not correct.d443g5159jRemove tag and the contents.wAgree{k) done 2007/12/0109/16/2007 03:35:02 EDTMarkedNogtr]ERajkumar, AjayF GProducer^ Technical_78`31a7.4.1cAlocal MIH User specifying local MIHF capabilities as well as remote MIH User specifying remote MIHF capabilities. For example, what happens if the MIH User specifies something that the MIHF can't support? However, it is possible that the "Supported IS Query Type List" and the "Handover related commands" may be an exception as this functionality is provided by an MIH User (e.g. receives indications and generates responses). What if more that one remote MIH User exists, which one is responsiB#ble for responding to this request?d433g5169jever, it is possible that the "Supported IS Query Type List" and the "Handover related commands" may be an exception as this functionality is provided by an MIH User (e.g. receives indications and generates responses). What if more that one remote MIH User exists, which one is responsiB#ble for responding to this request?d433g5169j"ptheproposedsentenceisvagusandthereseemtobenoreasoVthesectionwasremovedbychangefromanothercomment#Vthesentencehasbeenmodifiedandtheproblemseemsnolong(Vthesentencewasdeletedin420changethestartingsentenceVthevaluesdefinedaredeliberatelymadeconsistentwithrad3Vthen Wthere(W^WWWWthereforeWWthese WWthey3WthisWWW*WNWWW^WWWWW W/WAWOWWWWWWWthisisaconventionusedthroughoutspacesareusedintablVthisisapoacontainerpoadoesnotnecessarilyhasanyposVthistexthaschangedbytheresolutionofcomment11VthoughEWthresholdsoWoWoWoWoWoWionofcomment11VthoughEWthresholdsoWoWWWWWWWWW WWWWW$W*W3W6WHWOWVhERajkumar, AjayF GProducer^ Technical_103a7.4.18cW?W@WAWBWCWDWEWFWHWKWLWMWNWrWsWtWuWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW%W'W-W.W0W1W4W7W9W:W;W<W=W>W?WAWBWCWDWEWFWGWHWJWLWMWOWPW|i`ERajkumar, AjayF GProducer^ Technical_71`4142c1Periodic notification is on a per parameter basisd430g5172jAChange "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." to "For each specified parameter, this notification is generated either at a predefined regular interval determined by a user configurable timer or when it crosses a configured threshold."wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o the currently active interface crosses a configured threshold." to "For each specified parameter, this notification is generated either at a predefined regular interval determined by a user configurable timer or when it crosses a configured threshold."wAgree{k) done 2007/12/0709/16/2007 03:08:31 EDTMarkedNo f+@@@?@bc@*j@cJ@aw@ @Ajg@[vAih@c^>@jcAv@@vAe@vAeeee'@vjr@TcBv@UcAvvz@cApAx@cAMpA@cA%@ccAccAr@pK@wL@cAZccBi@%cB@cAvA@1jc@cS@@/{B@cApjAS@<cc@@V@_@c1@r@ vw@!vA(@5@,cERajkumar, AjayF GProducer^ Technical_57`58cNET_SAP is not only used for L3. It handles both L2 and L3, just that L2 communication whould be handled by LINK_SAP (via NET_SAP).d427g5175jChange "For transport services over L2 the primitives are specified by the MIH_LINK_SAP" to "For transport services over L2, MIH_NET_SAP utilizes the primitives specified by the MIH_LINK_SAP"w Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o uld be handled by LINK_SAP (via NET_SAP).d427g5175jChange "For transport services over L2 the primitives are specified by the MIH_LINK_SAP" to "For transport services over L2, MIH_NET_SAP utilizes the primitives specified by the MIH_LINK_SAP"w Principle{k) done 2007/12/0109/16/2007 03:08:31 EDTNo%MEMyles, Andrew FF DisapproveGProducer^ Technical_67`17a7.3.4cis broken on the specified link and no more packets may be sent on the specified link" to "This notification is delivered when a layer 2 connection is no longer available for sending frames." No change made for 7.3.5.3 Delete "normally" in the first sentence of 7.3.5.4. (Note: Probably should delete the last sentence since it doesn't need to be furthur described. Link_Up ends with two sentence.)v"Add clarifying text from TGu draftw Principle{k) done 2007/12/0709/11/2007 17:46:47 EDTMarkedYes EMyles, Andrew FF DisapproveGProducer^ Technical_67`17a7.3.4chandover between networks.yd92g5510jmCorrect the text to state that link down is generated whan all possible L2 links to a given network are down.p network are down.p3ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_67`41a7.3.4.2cAHow does the link layer know that the IP address needs renewal? This goes against the protocol layering. If it is believed that the PoA provides this information, how does the PoA know that the device needs a IP renewal, since this Link-Up is at L2? It would be reasonable to think that the renewal decision must be left to the higher layers but just provide any necessary and available IP information e.g. IP subnet info of the new interface.d607g4995al? This goes against the protocol layering. If it is believed that the PoA provides this information, how does the PoA know that the device needs a IP renewal, since this Link-Up is at L2? It would be reasonable to think that the renewal decision must be left to the higher layers but just provide any necessary and available IP information e.g. IP subnet info of the new interface.d607g49950 09/16/2007 13:36:45 EDTNo chnical_65`49a 7.3.2.2.2cFor added clarity, add text that states that this message can be used for also specifying the time interval between periodic reporting of link parametersd282g5320jReplace line 8 by text "This primitive is used by the MIHF to configure thresholds and/or specify the time interval between periodic reports for the Link_Parameters_Report indication."wAgree{k) done 2007/12/0709/14/2007 18:36:55 EDTMarkedNo E Julka, VibhorF DisapproveGProducer^ Technical_65`49a 7.3.2.2.2cndication."wAgree{k) done 2007/12/0109/14/2007 18:36:55 EDTNox /cAThe text does not state that the link going down notification is delivered when the last possible L2 connection to a specified network is about to be broken. From the definition in the text, a possible interpretation is that a link going down event will be generated whenever an STA makes a transition from 1 AP to another; this is out-of-scope for 802.21 which is facilitating inter-technology and intra-technology (when these are between different networks--e.g., different SSIDs in WLANs) haBndovers.d93g5509jClarify the text.psumes that the link will be valid for Time Interval, only to have it yanked away earlyyd556g5046j.Be consistent with what "Time Interval" means.v^preference@,replaced@respond@lsentence@structured@0style@ superceed@thatAMthemihfisalogicalentitywhosedefinitionisindependent@theproposedsentenceisvagusandthereseemtobenoreaso@ throughout@toWGupdatedausenohyphen@wait@v1wirelessgsm/gprs@:21-07-0317-01-0000-s@23@^3gpp@7@802.21@802.21-specific@able@add0addmihlinkactiontothetable5@addthisinsection8.2@Waddressed@allowed@land,"applicableat@basis@Ibe}bullets@bybycomment105@R__p207W>W21-07-0430-00-0000WWW21-07-375-01W221W24W26HW260W W277W3 WWWW30W3007WW302W334 W339WW343+W35W351 WWW378W394W397W3gppW0W3gpp2W42WW410W417lW420W429[W\W44WWW45WW(W454WWWWWW471W472W48W497WW8WWWW5RW5.3$W5.3changedtomihfserviceoverview$V563W588W59W6.2.1W6.2.3W615WWWW619W621W624W64W66-127W7WWOWQWWWWWWW7.3.5.3W7.3.5.4W6WWWWWWW7.4.276W6W6WWWWWWaccording@WacronymsWactionszWJE Cypher, DavidF DisapproveGGeneral Interest^ Technical_53`12a6552c5There is no Mobility Management IE in this container.d132g5470jAdd Mobility Management IEwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s jIf MIH_NET_SAP is used for L3 only, then there is no need for this parameter and should be deleted throughout the document. If there is a need for the parameter then the text of this clause 6.7 needs to be changed to reflect the meaning of this parameter.vby 427w Superceded 2007/11/2809/13/2007 13:56:26 EDTMarkedYesE Cypher, DavidF DisapproveGGeneral Interest^ Technical_53`12a6552c5There is no Mobility Management IE in this container.d132g5470jAdd Mobility Management IEwAgree{k) done 2007/11/2809/13/2007 13:56:26 EDTMarkedYesejKIf annex D is normative, make it a clause in the body of the specification.wDisagree{l) none needed 2007/12/1909/14/2007 23:15:41 EDTYes sment plus the value data type mappings) included in Annex D.wDisagree 2007/11/28N #6cA=TLV representation for information elements can be confused with later page 152 section 8.5 "Message parameter TLV encoding". Especially the type field has different length. Moreover, IEs can be represented either in binary encoding or RDF encoding. Section 6.5.5 should introduce IE binary encoding and RDF encoding.=d216g5386jAPlease see contribution 21-07-304-00-0000-Organize_Section6.5.docv.Delete section 6.5.6.2 (RDF Schema Propoganda)w Principle{k) done 2007/12/1909/13/2007 16:42:41 EDTYes Change description "binary query" to "TLV query". No modification required for the data type naming and the parameter naming.v.Delete section 6.5.6.2 (RDF Schema Propoganda)w Principle{j) in progress 2007/12/1209/13/2007 16:42:41 EDTYesprogress 2007/12/0509/13/2007 16:42:41 EDTYes s h5pdefinitionWWdefinitions0W3WWWdeleteWdeletedW,WYWRWSWWWWWdeletedm1YVdeletedthe3itemsVdeletedthescanresponsesetinsection7needtomodifyanVdeliberately3WdeliveredWdeploymentWdescribedWdescriptionWqWWWdetailsWdetectWdetectedWdhcpOWdiagramWWdiagramupdatedtoreflecttgureferencediagramVdiagreedWdidWdidbothtables34VdirectlyWdisagreedWIWWWWAWdisagreesWWW WdiscardAWdisconnectionWdiscoverWdiscoveredWdiscoveryWdiscussionWdiscussionwiththecommentorconcludedthatnothingneededVdoW W/WWdocumentWWdoesWWWdoesn'tWdomainWdomainWWWWWWronmentWetc3WeveryW ecAThe location used in the information model is for the PoA. For 802.11 networks this is not the correct information for the following reasons: 1. The mobile node should not care about the location of the PoA. The mobile should only care about whether RF coverage is obtainable at a specific location. 2. Many operators will be unwilling to provide actual location (e.g., latitude and longitude) for a PoA. As such, there will be no location information in many MIIS databases.d88g5514jDelete the PoA location.vPoA location is essential to determining the availabiility of coverage in an area. If an operator is not willing to provide this information they can just include NULLs. wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2a6.5.5.2KLKEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the frequency bands supported by the network (e.g., 2.4-GHz, 3.7-GHz, 2.5-GHz, 5.2-GHz, etc.)d82g5520jAdd this capability.v5The capability already exists in draft in Table B-13.ndrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the frequency bands supported by the network (e.g., 2.4-GHz, 3.7-GHz, 2.5-GHz, 5.2-GHz, etc.)d82g5520jAdd this capability.v5The capability already exists in draft in Table B-13.MarkedYesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the frequency bands supported by the network (e.g., 2.4-GHz, 3.7-GHz, 2.5-GHz, 5.2-GHz, etc.)d82g5520jAdd this capability.v5The capability already exists in draft in Table B-13.{j`Change to "Functional entities shall discard any received IE with an unrecognizable identifier."{k) done 2007/12/1909/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Technical_105a7.4.19cAThe Purpose and usefulness of MIH_Net_HO_Candidate_Query command are unclear. This command is sent from the serving PoS to the UE, but the UE won't be able to query the candidate networks unless the UE is connected to the candidate networks. That assumption is highly unlikely.d348g5254jJremove all definition and mentioning of MIH_Net_HO_Candidate_Query commandpSuperceeded by 260.wDisagreeyRef 260{l) none needed 2007/12/1909/15/2007 22:08:13 EDTYes s `5a6.4.1c_Figure 16 is confusing by showing two unrelated stacks. Showing one stack would be good enough.d347g5255joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.wAgreeside.wAgreeZi+c_The information model proposed in Figure 19 is overly complicated as far as 802.11 networks go.d79g5523vProvide ways of simplificationwDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_44`10a 6.4.3.1.1cAThis comment applies to this clause as well as to the document in general. The text describes the following: 1. MIH_Get_Link_Parameters: get the status of a link. 2. MIH_Configure_Link: configure a link. 3. MIH_Net_HO_Candidate_Query: Network may initiate handover and send a list of suggested networks and ... The text continually switches between the terms "link" and "network". The scope of MIH is roaming between "networks", whether it is inter-technology or intra-technology (e.g., roaming., roamingTMarkedYesEMyles, Andrew FF DisapproveGProducer^ Technical_50`1a6.5.3BcaIn the list of PoA on the bottom right, the first element should state Operator_2, not Operator_1d25g5577{k) done 2007/12/1909/04/2007 16:19:39 EDTNoE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_187`34cNCOS_ID is valid between 0-255 therefore it needs to be set as UNSIGNED_INT(1).d24g5578{k) done 2007/12/1909/04/2007 16:19:39 EDTNoE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_182`57c@Battery level is a percentage and should use the PERCENTAGE typed23g5579p=PERCENTAGE type won't be able to represent "-1" special case.{e) editor disagrees 2007/12/1909/04/2007 16:19:39 EDTNo wxEEmmelmann, MarcF DisapproveGAcademic^ Technical_48`13a6.5.3cARef. to table 8, access-network-aux-id: The table sould not contain any mandatory values for a technologie, i.e. that this IE shall contain the SSID for an 802.11 network. Nevertheless, it is a good idea to have such information somewhere but a normative annex (one for each considered technology) which contains such mandatroy values would be better. Having this, the main chapters of the standard are kept technology-independent and the reader has a single point where technology specific valBues for certain parameter or IEs are assumed. Besides, if a (new) technology supports 802.21 in the future by adding new service primitives / functionality, there is only a single place in the 802.21 standard which need to be revised.d50g5552j5Delete ref to 802.11 and create an annex as suggested2j5Delete ref to 802.11 and create an annex as suggestedw(EEmmelmann, MarcF DisapproveGAcademic^ Technical_41`59a6.4.1cA"Whenever applicable the IEEE 802.21 standard shall use existing media-specific link commands for interaction with specific access networks. New link commands, if required, shall be defined as recommendations to link layer technology standards." This sentence introduces a media-dependent (!) aspect of 802.21 even though .21 shoulde be media-independent. 802.21 should define "generic" link-commands as it does e.g. in table 7. The adaption of such genric commands to the actual technology shoBuld be done by the working group responsible for the specific technology ... and of course one should use existing commands for this. td49g5553jdelete the sentencesvld be done by the working group responsible for the specific technology ... and of course one should use existing commands for this. td49g5553jdelete the sentencesv}k jCome up with a more generic parameter list for the LINK_UP indication, maybe something like old / new IP address only ? For cellular, could allocated PDP contexts or some subparameter of it do the job ?pTChange the MAC Old/New Access Router to LINK_ADDRESS data type throughout the draft.vIChange the data type to LINK_ADDRESS. (AC: Vivek, Qiaobing please verify)wAgree{k) done 2007/12/1909/16/2007 12:18:13 EDTNo ERudolf, MarianF DisapproveGProducer^ Technical_181`57c1`57cses of old and new access routers in its parameters list. That would probably apply for most LINK_UP indications received from 802 access technologies in certain deployments (but for home routers ?), but what would be the corresponding vales in the case of LINK_UP received for GSM/EGPRS or W-CDMA links where there is no access router ?wd513g5089P9E Kim, YonghoF DisapproveGProducer^ Technical_43`33a6.4cwhat does that mean by MIH_Command.indication/response in Figure 18? Does that mean commands can go up to MIH users? Draft needs to clarify command's direction appropriatelyd333g5269jBClarify if commands are allowed to be sent from MIHF to MIH users.v Commands are NOT sent from MIHF to MIH Users. For remote commands link layer indications or MIH level indications may be generated at the remote entity. wDisagree{l) none needed 2007/12/1909/14/2007 23:51:12 EDTYesscommands are allowed to be sent from MIHF to MIH users.v Commands are NOT sent from MIHF to MIH Users. For remote commands link layer indications or MIH level indications may be generated at the remote entity. wDisagree{l) none needed 2007/11/2609/14/2007 23:51:12 EDTMarkedYesozdjReplace with "Notification from either source or target MIHF to the other (i.e. peer) MIHF indicating the status of the handover completion."wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo eERajkumar, AjayF GProducer^ Technical_97`4446cAJust when is a link handover considered complete (see page 98 line 35-40)? And why do we only report a successful handover? What happens to upper layers that are waiting for a HO complete indication and never receive one? How long should they wait before they consider the handover failed? Page 98 (lines 28-31) states that is "could" be posted after a successful MN_HO_Commit or NET_HO_Commit but a MN_HO_Commit doesn't actually perform a handover it simply exchanges messages with a remote MIBUH User (see page 230, a subsequent Link Action is necessary to perform the handover).Cd425g517725g5177iEMyles, Andrew FF DisapproveGProducer^ Technical_26`39a5.5.3cThe text states, "...before a station has associated and authenticated with an AP, whereas the LSAP may ...". Chronologically, a STA authenticates before it associates.d77g5525jFSwitch the order of associate and authenticate in the referenced text.wAgree{k) done 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_26`1a5.5.3cAThe reference model for 802.11 is incorrect. The model shows that MIHF is connected to the MLME SAP. In 802.11, primitives are provided to the SME and the MIHF should have its interface to the SME. The SME is responsible for layer 2 transition between APs and should not provide, for example, a link-down indication everytime the STA re-associates to a new AP. Rather the MIHF should only receive a link-down indication when the STA become disassociated from the ESS (or is about to become disaI{k) done 2007/12/1909/15/2007 22:08:13 EDTYessfrom the stack on the left-hand side.wAgree 2007/11/2609/15/2007 22:08:13 EDTMarkedYesENoens, Richard HF DisapproveGProducer^ Technical_63cMIH_NMS_SAP defines the interface between an MIHF implementation and a local Network Management System stack. It imposes constraints to implementations without any clear benefits. The local NMS stack may not even exist depending on the implementation.d99g5503jRemove MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/1909/11/2007 17:47:21 EDTYes stack. It imposes constraints to implementations without any clear benefits. The local NMS stack may not even exist depending on the implementation.d99g5503jRemove MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/1409/11/2007 17:47:21 EDTYes s s!5 vA# Change sentences to as follows: "Whenever applicable the IEEE 802.21 standard encourages use of existing media-specific link commands for interaction with specific access networks. New link commands, if required, are defined as recommendations to different link layer technology standards."#w Principle{k) done 2007/12/1909/10/2007 07:08:58 EDTYessH {doneWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW%W'W-W.W0W1W2W3W4W6W7W9W:W;W<WeditordisagreesV*V3VVVVV2VeditorWW*W3WWWWWWW2WWfWWWWfpassofftoothereditorVVVVgroup%W+WWWh/Whdefertonextround/Vi!WWitodo!VVinW3WjW3WjinprogressV3VkWWWWWWWWWWWWWWWWWWWW-$ l=cASub-clause 6.5.5.1: Regarding the size of the "Length" field in TLV encoding, it appears that the effort is made to minimise the size of the "Length" field, and the encoding of such information as part of the "Type" field would be more effective. A 32-bit "Type" field is enormous, so it seems reasonable to use 2 bits in the "Type" field to indicate the size of the "Length" field, representing 1-4 octets respectively for the size of the "Length" field. The encoding and decoding of such infoBXrmation seems to be also more efficient than the 3 cases described in the current draft.Fd465g5137jponse RDF Data List, Info Response RDF Schema URL and Info Response RDF Schema List) Page 137, Line 19 (i.e., Info Response Binary Data List, Info Response RDF Data List, Info Response RDF Schema URL and Info Response RDF Schema List)IwAgree 2007/11/2609/16/2007 06:10:15 EDTMarkedYes=ELach, Hong-YonF DisapproveGProducer^ Technical_52`1c"-ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_226`1aGcThe title is not descriptive.d225g5377j3Use "How to extend MIIS basic schema" as the title.p+use "Making User Extensions to MIIS schema"{k) done 2007/12/1909/13/2007 16:42:41 EDTNo DTYes -ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_226`1aGcThe title is not descriptive.d225g5377j3Use "How to extend MIIS basic schema" as the title.p+use "Making User Extensions to MIIS schema"{k) done 2007/12/1409/13/2007 16:42:41 EDTNo o o5EEmmelmann, MarcF DisapproveGAcademic^ Editorial_33`45a6.2.2cEFinal layout by IEEE editorial team will result in tables to "float".d46g5556jjReplace "The following set of service primites" with "The set of service primitves listed in Table 2 ...."{k) done  ESreemanthula, SrinviasF DisapproveGGeneral Interest^General_19`1a5.4.2cThis section is grossly disconnected and suffers from lack of relevance from the rest of the specification. Other than section 5.4.3, the terminology or reference points are not used anywhere in the specification.d596g5006jClarify the use.vcThis clarifies PoA and PoS and provides Reference Points which provides context for the interfaces.wDisagree{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYessnnected and suffers from lack of relevance from the rest of the specification. Other than section 5.4.3, the terminology or reference points are not used anywhere in the specification.d596g5006jClarify the use.vcThis clarifies PoA and PoS and provides Reference Points which provides context for the interfaces.wDisagree{l) none needed 2007/11/2609/16/2007 21:41:08 EDTMarkedYes! jAcPlease state clearly if MIH signalling exchanges using data frames of Ethertype TBD is an option for 802.11 or if it is not. Clearly state to what extent the 2nd available option of using management frames is possible (a.k.a MIH IS only and so on). Alternatively, insert wording here ruling out the possibility of using data frames in 802.11 to carry MIH.cpsuperceded by change from 45vA5.7.2 Transport Considerations Change as follows " Transport of MIH messages over IEEE 802.11 and IEEE 802.16 links is recommended through extensions of media-specific management frames in state 1, and through management or data frames in state 3. No assumptions are made in this standard regarding the transport of MIH messages over 3GPP and 3GPP2 access links at L2. If the MN cannot reach the MIH PoS via the lower layer (i.e. L2) transport mechanisms, then higher layer (i.e. L3) tranB!sport mechanisms shall be used. "w Principle{l) none needed 2007/12/19BEHeubaum, Karl FFApproveGProducer^ Editorial_16`22a5.2.3.5c=There's a period missing at the end of "...layer 3 handover".d65g5537j Change to "...layer 3 handover." pstructuredWstructuresWlauseW W6WWWWWsubscriptionW WsubsetWsuchWWsuggestWsupercededWWWWWWWWW WWW(W+W7W8WWWWWWWW WWW#W'WMWWWWWWWsupercededby106VV V#VVsupercededby3007Vsupercededby300471Vsupercededby35Vsupercededby497VV8VVVVsupercededbychangefrom334 Vsupercededbychangefrom343+Vsupercededbychangefrom45VVsupercededbychangesfrom472Vsupercededbycomment10VVVsupercededbycomment11VVVVMVVVsupercededbycomment2'Vsupercededbycomment454VVsupercededbycomment59VsupercededtheconcernedtextisremovedbyanothertechcomVV_rd52g5550jDelete items a) through e) and move their contents to a (normative) Annex. There should be one Annex per technology containing any technology-specific information which is reqired to make 802.21 work with / adapt to the specific technology.v>Move items [a] through [e] to Annex-L. Make Annex-L normative.wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYes n progress 2007/12/0809/10/2007 07:08:58 EDTYes s l vA;LLC is specifically an IEEE 802 entity and it is valid only for IEEE 802 technologies and is not applicable for other technologies such as 3GPP/3GPP2. Hence it is not shown in this figure, but is shown in other figures for other specific link layer technologies that it is valid for in section 5 (figures 6, 7 etc.);wDisagree{l) none needed 2007/12/1909/03/2007 16:49:33 EDTYesE Seifert, RichF DisapproveGGeneral Interest^ Technical_59a7cAIn numerous places in this clause, conformance requirements (I.e. "shall" statements) are given, for example, on page 54, line 62, subclause 7.3.1.2.4. Clause 7 is a *service specification*, not a protocol specification. It defines a set of abstract primitives used by layer entities within a given device to intercommunicate. Internal implementation details are not a proper subject for the conformance requirements of a standard. It is not necessary for a conformant device to use internal laernal la? 2007/12/1909/16/2007 15:56:25 EDTYes sZ{disagreesW*W3W9WWWWWWWWWWdoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWWW W"W$W)W,W-W.W:W;W>W?W@WAWBWCWHWKWLWMWNWOWPWQWRWSWTWXWZW^W`WaWbWcWdWeWfWhWiWjWkWmWnWoWpWrWsWtWuWzW{W|W~WWWWWWWWWWWWWWWWWWWWWW8 cAAlso subclause 1.5 second para and subclause 1.3 last para on page 2. This is a false assumption in terms of existing 802 architecture. The role of the MAC service in the 802 architecture is to describe the parameters that are conveyed in peer protocol exchanges between systems, not to model local interactions within a single system. The latter is appropriately described either in terms of management interactions with managed objects, or maybe as some kind of local API, but in either case,B not as part of the service interface presented at a (sub)layer SAP. In any case, modelling the (sub)layer service interface in such a way that there are distinct SAPs for modelling different protocol (or other local) functions fundamentally misses the point of the concepts of service boundaries and SAPs in the OSI reference model, which is what the 802 architecture is based on. You really should have discussed this with 802.1 experts long before presenting this kind of material for Sponso7@GcAjAcA@j@_cG@ vA!"@#@U$@jE&v'vA(@)@.*]+@-@+.@/p0@w3@k4@N6cA7@9@:@;@s pandW/WAWqWWWWWannexWWWW9WVW^WaWW4WWannexbthisisaproblembecauseqoslistisasequenceand^V^V^V^Vmie9Vannex1Wannexes/Wannexes16Wannexes1removethetextfrompage197l38p198l24andtext6VanotherW#W2WWanyWapWapplicableWWWWWWappliedWappliesnWoWareW3WWW/WWWas3WnWoWWWWWW W@WOWWWWWWask2Wassigned3WassignmentsWassumeWatWWWauthenticationWauthority3Wautomatically WauxWavailableWWbVW^WaWWWb-19WbasediWjWbasic4WbeWWWW3WVWWW^WWWWAWWWWWWWWbrokenWW5UEJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_3`63a1.4c to specify mechanisms across multiple other standards, has exactly NO normative references. This is laughable, and to me, simply demonstrates that the document is not ready for prime time. Apart from anything else, the standard appears to be trying to re-define the MAC service. Why is there no normative reference to the existing MAC service definition?d250g5352jDetermine which of the references in the bibliography should actually be normative references and move them to clause 2. Add any further normative references that are necessary to clause 2.w Supercededy Ref Cmt 497 2007/11/2609/14/2007 08:30:59 EDTYesEJeffree, Anthony AF DisapproveGGeneral Interest^ Technical_3`63a1.4c.?EMccann, StephenF DisapproveGProducer^ Technical_2`14cAlthough this text refers to IEEE 802.15, it appears that there is no interface defined to this technology, within the main part of the standard.d363g5239jjPossibly remove the reference to IEEE 802.15, as it is not specifically defined within this base standard.vremove 802.15 from Figure 1 and from page 4, line-14. Leave it on page 2 where it is used as an example to describe pico cellsw Principley Ref Cmt 363{k) done 2007/12/1909/16/2007 01:46:33 EDTYesEMccann, StephenF DisapproveGProducer^ Technical_2`33cAlthough this introduction refers to IEEE 802.15, it appears that there is no interface defined to this technology, within the main part of the standard.d362g5240jjPossibly remove the reference to IEEE 802.15, as it is not specifically defined within this base standard. standard.specifically defined within this base standard.KWE Sood, KapilF DisapproveGGeneral Interest^ Technical_5`1a2cAre the no Normative References used by this standard? Eg: What about IEEE Standards Terms mentioned in Clause 3 introduction of definitions.d265g5337j#Update the Normative Reference listvby 497w Supercededydeferred. Same as 497 2007/11/2609/14/2007 16:50:16 EDTYesKyv%Need to change this across the draft.wAgree{k) done 2007/12/1909/14/2007 16:50:16 EDTYessQv'Remove the definition of higher layers.wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Editorial_7`15a3.18c#use correct plural of MN, i.e.: MNsd29g5573jdelete apostrohpe "MN's"{k) done 2007/12/1909/10/2007 07:08:58 EDTNoooM{kWWWWWWWWWWWWWWWWWWWW W W WkdoneVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV V VVVVV-V.V6V:V;V<V>V?V@VAVBVCVDVEVHVKVLVMVNVOVPVQVRVSVTVVVXVYVZV^V`VaVbVcVdVeVfVhViVjVkVmVnVoVpVrVsVtVuVwVzV{V|V~VVVVVVHvDelete: "The MIH services defined by the IEEE 802.21 standard, including event, command, and information services, need to consider network traffic performance objectives and how well they meet the application quality of service requirements."wAgree{k) done 2007/12/1909/10/2007 07:08:58 EDTYess@jDelete "From that perspective, MIHF offers a unified interface to the MIH Users." Replace "The service primitives exposed by this unified interface. . ." to "The service primitives defined at this interface. . ."|vDelete "From that perspective, MIHF offers a unified interface to the MIH Users." Replace "The service primitives exposed by this unified interface. . ." to "The service primitives defined by this interface. . ."wAgree{k) done 2007/12/1909/16/2007 06:10:15 EDTYess)cWhat does it mean by "transparent inter-working with legacy equipment"? Does this standard make legacy equipment speak MIH language? "Interworking" is different from co-existance. Is this principle trying to say two different requirements?d496g5106j'Define the "interworking" or remove it.vWChange as follows: "The standard supports transparent operation with legacy equipment"wAgree{k) done 2007/12/1909/16/2007 08:19:02 EDTYess7phyphenWi3Wiana3WidWWWWWWWWWWideaWidenify2WidentifiedWidentifierWieWWWWWieee9WiesWifW^WWWWillustrated WinWWWWWWWWWWWWW0W2WHWOWQWRWVW[W^WlWnWoW{W|WWWWWWWWWWWW WWW/WOWWWWWWWWWintoWintroduction6WipWWisWWW*WnWoWWWWW2WAWiWjWWWWWWitnWoWWWW2WAWWit'sWitemsWWits3W2WWkenichiiWjWkenichiiswillmodifythefigureiVjVkeptnWoWknows2WlWl126Wl17Wl246Wl346Wl386W/H{k) done 2007/12/1909/11/2007 11:53:29 EDTNooxE Sood, KapilF DisapproveGGeneral Interest^ Technical_15`36a5.3.1cA"MIH services in mobile nodes facilitate seamless handovers between heterogeneous networks" - Has this statement been proven to work inter-operably? I believe the goal of this amendment is to provide such an enhancement. However, unless we have at least 2 inter-operable implementations implementing 802.21, we cannot get any guidance on whether this goal is met. And, in extension, it is not proven if the mechanisms defined in this amendment are sufficient for interoperability. This comment Bis against the entire draft. d272g5330jReword the goal accordingly to mention this as a desirable goal - not as an end result. Also, strongly suggest that participants of this standard conduct a plugfest to ensure that this protocol has been established to inter-operate, and hence, be useful.this protocol has been established to inter-operate, and hence, be useful.".joReplace the sentence starting on line 43 by: "Communication between two MIHFs relies on MIH protocol messages."{k) done 2007/12/1909/16/2007 15:32:58 EDTNoENatarajan, Kadathur SF DisapproveGProducer^General_282c-Annex J does not add value to the final spec.d541g5061jIRemove Annex J "Requirements to support 802.21 by L3 and above transport"wAgree{k) done 2007/12/1909/16/2007 15:23:06 EDTYes ENatarajan, Kadathur SF DisapproveGProducer^ Technical_150`60a8.4.1cPMIH Protocol header is of fixed length, as indicated in fig 27 on the next page.d540g5062jKCorrect Figure 26 to show MIH Protocol Header has fixed length of 8 octets.psuperceded by comment #454wAgree{k) done 2007/12/1909/16/2007 15:23:06 EDTYes ENatarajan, Kadathur SF DisapproveGProducer^ Technical_124a7.4.244a7.4.24a7.4.244a7.4.24$j3remove definition and all occurences of MIH_NET_SAPpduplicate with 105w Supercededy Ref Cmt 105{l) none needed 2007/12/1909/14/2007 03:15:28 EDTYes%E Jee, JunghoonF DisapproveGProducer^ Technical_2`14a1.3cThere needs to clarify how's wireless link conditions change for mobile users. In the IEEE P802.21/D7.1 draft, similar description is used for both mobile user and stationary user case.d233g5369jFor mobile users, handovers may occur due to changes in wireless link conditions according to the user's movement across wireless links.wAgree{k) done 2007/12/1909/14/2007 03:14:16 EDTNo&E Koh, BenjaminF DisapproveGProducer^General_258aH6cGiven the (obvious) usage of MIH in a FMIP scenario, it behooves the draft to provide some guidance as to how MIH may actually be used in such a situation.d232g5370j"Add a call flow for FMIP operation operation operationDm>7ERudolf, MarianF DisapproveGProducer^ Technical_13`36a5.1.7cAThis section must be extended to give a clear idea to the implementor how 802.21 works in conjunction with encryption/integrity protection provided by at least the IEEE 802 technologies. While I agree that 802.21 doesn't need to address security aspects involved in mobility, I also think it is too simplistic to say it is "simply out of scope". The minimum that 802.21 must describe is where the signalling or some of the services (notably, command service) it provides is dependent on prior sbly, command service) it provides is dependent on prior sptoWW^WgWnWoWWWWWWWWWWWWWW WWW-W4WAWlWoWqWWWWWWWWWWWWWWWWtoo/WtransferWtransistionsWtransitionsWtupleWtwoWtypeWWWW WW0WWWWWWWWtypeieroamingpartnersisdefinedtobeabletorepresentWVtypicalWumts0WunauthenticatedWunclearnWoWunderWunderstoodWunifiedWunsignedWunsolicitedWupWWWWupdateWWWlWupdatetomihlinkactionslVupdatedWW2W2WW2W2W2W2W2W2W2W2W2WW2W2Wnex1andtlvassVusageWuseWWW-WzWWusemakinguserextensionstomiisschema-VusemihlinkactionszVpchangemadethroughoutthedocumentVchangethemacold/newaccessroutertolinkaddressdataty Vchangethetypefromunsignedint1toenumeratedVchangetooldtosourcesincethesourcewasusedinsteadofVchangedWWWW$WOWQWWOWqWWWchangedinlinkactionneedtochangethelinkscanrspdataVchangedinsection7annexctableupdatepoatlvmacaddresVchangedinsection7verifiedmessageinsection8QVVchangedinsection7verifiedmessageinsection8QVQVWWWcmt30deletedthedefinitionVcommentWWWWWWWWW#WnWoWWWWWWWWWWWWWWWW'W>WMWWWWWWWWWW Wcommentnolongerapplicableduetoresolutionofcomment11VVVVrossWdata6WpproverE Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8cThe MIH protocol is inadequately specified. In particular, the state machine is overly simplified, and none of the state variables are rigorously or formally defined.d11g5591 a system, conformance to this clause is not necessary for interoperability.,d12g5590jjDelete all "shall" statements and conformance requirements for this clause and all service specifications.v!David to provide some explanationwDisagree 2007/12/0109/03/2007 16:49:33 EDTYesE Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8cThe MIH protocol is inadequately specified. In particular, the state machine is overly simplified, and none of the state variables are rigorously or formally defined.d11g5591a cBhat MIH_NET_SAP is called to carry messages either layer 2 or 3 and above. While MIH_LINK_SAP provides the mechanisms to send the MIH messages at layer 2, it would be MIH_NET_SAP that uses it if MIHF requests to send over layer 2.d133g5469jIf MIH_NET_SAP is used for L3 only, then there is no need for this parameter and should be deleted throughout the document. If there is a need for the parameter then the text of this clause 6.7 needs to be changed to reflect the meaning of this parameter.v$Resolved in other comments (cmt 427)w PrincipleyRef 427.{l) none needed 2007/12/1909/13/2007 13:56:26 EDTYespGMade change to allow HESSID be carried in TYPE_IE_ACCESS_NETWORK_AUX_IDv"Refer to TGu MIh draft for detailsw Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYes s :47 EDTMarkedYes wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cThe TYPE_IE_CONTAINER_NETWORK should contain means to discover the location of the network (or more specifically, the RF coverage of the network).d81g5521jAdd this capability.vThis can be determined from the PoA location. It is very difficult to determine the RF coverage area and be able to represent it accurately.wDisagree{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_50`1a6.5.3c>=J{kWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW~*Wg5163pTYPE_IE_ROAMING_PARTNERS is defined to be able to represent a list of partners. This change would make the representation less efficient.vA - p48 L15 TYPE_IE_ROAMING_PARTNERS -> TYPE_IE_ROAMING_PARTNER ROAMING_PARTNERS -> OPERATOR_ID - p50 L22 Figure 19: The TYPE_IE_ROAMING_PARTNERS -> TYPE_IE_ROAMING_PARTNER and add additional "..." in a way to identify there can be multiple TYPE_IE listed. -p52 L62 Roaming Partners IE -> Roaming Partner IE and add additiona "..." to identify there can be multiple entries. - p192 L13 Delete the ROAMING_PARTNERS - p201 LB714 Bit 8: TYPE_IE_ROAMING_PARTNER (remove S). %w Principle{e) editor disagrees 2007/12/1909/16/2007 03:35:02 EDTYesIctData type for system_information should be defined. Refer to contribution , 21-07-0317-00-0000-System_Information_IEd339g5263j:Discuss and adopt 21-07-0317-00-0000-System_Information_IEp- used CELL_ID already defined.v21-07-0317-01-0000wAgree{k) done 2007/12/1909/15/2007 00:24:13 EDTYes data structures are not organized in the same way the current IE data types are organized, and hence is unclear how to apply the changesv21-07-0317-01-0000wAgree{c) instructions unclear 2007/12/1209/15/2007 00:24:13 EDTYes #109/15/2007 00:00:07 EDTYessC109/14/2007 23:15:41 EDTYesspneeded^WWneeds^WnetgWW WnetworkWWW3WWW WmWWWWWWnetworksecurityisremovedfromothercommentmVnetworks WWnewOWAWWnextWWW<ÃW;ÃW:ÃW9ÃX8ÃX 7ÃX06ÃX@5ÃXP4ÃX`3ÃXp2ÃX1ÃX0ÃX/ÃY.ÃY -ÃY0,ÃY@+ÃYP*ÃY`)ÃYp(ÃY'ÃY&ÃY%ÃZ$ÃZ #ÃZ0"ÃZ@!ÃZP ÃZ`ÃZpÃZÃZÃZÃaÃa Ãa0Ãa@ÃaPÃa`ÃapÃaÃaÃaÃbÃb Ãb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@ _DT`DT\ vA5Emergency services and other applications as well may require information to be made available in the un-authenticated state. This has been discussed extensively in the group over a long period of time. it is up to deployment to decide how much information they make available in the un-authenticated state.5wDisagree{l) none needed 2007/12/1909/14/2007 16:50:16 EDTYes E Sood, KapilF DisapproveGGeneral Interest^ Technical_26`26a5.5.3cSThe 802.11 architecture is missing the 802.1X Authenticator port control component.d274g5328jUpdate the Diagram and description to include the 802.11 Authenticator in consideration. The MIH_NET_SAP should go this interface.p0diagram updated to reflect TGu reference diagramvbThis can be taken care of by 802.11 (TGu) people as part of updating the 802.11 reference diagram.wAgree{k) done 2007/12/1909/14/2007 16:50:16 EDTYess - {noneWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWprogressWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWg#EGiesberts, Pieter-PaulF DisapproveGProducer^ Technical_63cA\MIH_NMS_SAP defines the interface between an MIHF implementation and a local Network Management System stack. Depending on the nature of the device, this local NMS stack may vary or may not even exist. Standardizing this interface brings no benefit to the implementation. In the contrary, it would impose needless constraints to the implementation.\d235g5367j3remove definition and all occurences of MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/1909/14/2007 03:15:28 EDTYes 2/1409/14/2007 03:15:28 EDTYes s s\`{lnoneneededVVVVVVVVVVVVV6p"...an MN may access Information Services from an MIH entity in the network without link authentication. In such an unauthenticated state only a subset of information may be available."v&Clarify this as "link authentication".wAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYes s109/14/2007 23:15:41 EDTYessm+c{A description of the available options for which transport protocol an MIH node would use to discover MIH peers is missing.d483g5119jAuIntroduce a brief description of the L2 transport protocol and the L3 IP-based trasnport protocol options. For example, "MIH node can acquire list of MIH peers either locally or remotely. Locally can mean a pre-configured list. Remote acquisition can mean making use of the following MIH transport options, X, Y, Z". Could consider to move test in page 33 lines 6-14 here ?upsuperceded by change from 343{l) none needed 2007/12/1909/16/2007 07:13:12 EDTNo,ERudolf, MarianF DisapproveGProducer^ Technical_292`47cqThe implementor doesn't care what may or may not have been proposed and only wants to know what to build against.d482g5120jnRemove lines 47-48 and replace by a reference or short summary of features provided through the 11u amendment.pThat section was deleted.vdeleted.vuj@Provide additional requirements which will define MIHF Services.vFNeed to have more specific inputs as to what requirements are missing.wDisagree{l) none needed 2007/12/1909/16/2007 18:16:08 EDTYes ELevy, Joseph SF DisapproveGProducer^GeneralcQoS is a critical aspect of MIH, but there are very few normative requirements regarding the use of QoS measures and their uses.d590g5012jProvide additional normative requirements related to the use of QoS in MIH. e.g. - make some; if not all, of the QoS examples of Annex K and related material normative.pThe group disagreed on 588vuplicate comment as 588wDisagreey Ref Cmt 588{l) none needed 2007/12/1409/16/2007 17:59:40 EDTYes dLE Xie, QiaobingF DisapproveGUser^ Technical_63cA^MIH_NMS_SAP specifies the interface between an MIHF implementation and a local Network Management System stack. Depending on the nature of the device, this local NMS stack may vary or may not even exist. Standardizing this interface brings no benefit to the implementation. In the contrary, it would impose needless constraints to the implementation.^d342g5260j3remove all definition and mentioning of MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/1909/15/2007 22:08:13 EDTepending on the nature of the device, this local NMS stack may vary or may not even exist. Standardizing this interface brings no benefit to the implementation. In the contrary, it would impose needless constraints to the implementation.^d342g5260j3remove all definition and mentioning of MIH_NMS_SAPpsuperceded by 106wAgreey Ref Cmt 106{l) none needed 2007/12/0809/15/2007 22:08:13 EDTV{lnoneneededVVVVVVV V V VVVVVVVV#V&V'V(V+V/V5V7V [cALINK_CONFIG_PARAM allows one to request that a report be generated on a period basis on a per parameter type basis (in addition to crossing thresholds). This creates a very complicated interface. Besides the problem of multiple MIH Users configuring conflicting/overlapping thresholds, there does not appear to be a mechanism for reporting that a particular parameter report is being generated as a result of the periodic timer (e.g. it only reports threshold crossed up/down direction, there iB$s not value for specifying periodic)d435g5167j/see page 66 lines 35-36 and page 71 lines 32-33p%Superceeded by resolution in Cmt 429.w PrincipleyRef 429{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNoo pad@4addedx-reftoallmessagesin8.6@alltheoccurrenciesofmihinformationwaschangedasmihg@and7annexbupdated@sbePbut@by7changemadethroughoutthedocument@Hchangedtextto@clarified@commentnolongervalidbecauseofresolutionofcomment11@deciding@hdefinition@done@5email@examples@generatedvgroupdisagreeswithcomment@hyphen@Aininterval@ul59@made@Qmlme@needed@Rno@number@pagepdf@provides@yqos@reason@nson@neason@nstatusanddescript@reason@n4p8WHWOWQWIWWWW8.2.2W8.2.3.5W8.6WW8.6hasbeenupdatedstillworktodoinannexcV802.11WWW802.21W9WaWWW W9WWW^WWWW WAWWWWWWWWableWWWaboutWWacWaccess W3WOWWWactionWWWactionslWzWzWzWzWzWzWzWzWzWionszWzWnszWzWzW=4oE Cypher, DavidF DisapproveGGeneral Interest^ Technical_200`39c:Consistency problem: bit 1, there is no MIH_Configure_Linkd159g5443j'Change to MIH_Link_Configure_Parametersp(Chanbe to MIH_LInk_Configure_Thresholds.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes re_Parametersp(Chanbe to MIH_LInk_Configure_Thresholds.wAgree{k) done 2007/12/1209/13/2007 13:56:26 EDTYes " disapproverng-yon>0 disapprove2 disapprove3Q3lachhong-yon?2 disapprove4 disapprove515lachhong-yon@4 disapprove689G!U77 disapprove86U8lachhong-yonA7 disapprove9 disapprove:68:lachhong-yonB9 disapprove;C<#< disapprove=;C=-sreemanthulasrinvias , disapprove.F/#P/ disapprove0.F0sreemanthulasrinviasTyref397VDVVref407xVref407duplicatedwith406yVref417lVref420superceedVref427Vref429[V\Vref444supercededVref497Vref532supercededVref556Vref563ref326VVref612Vref615VVVref618duplicateVref621Vref624Vref88Vrefcmt10Vrefcmt10superceded&Vrefcmt105VV$VVrefcmt106VV V#VVrefcmt11MVrefcmt114Vrefcmt260VVrefcmt299Vrefcmt331Vrefcmt35Vrefcmt363Vrefcmt471Vrefcmt488superceededbycmt10'Vrefcmt497VVVrefcmt497duplicatedVrefcmt532Vrefcmt556Vrefcmt576Vrefcmt588duplicatedVrefcmt59supercededVrefcmt615614VsameW Wsameas105 Vsee8Wtiongroup%VdeferWWW/WB!RYes s  5ncA$It appears that IP Address Information Status is unnecessary. What does IP Address Information Status do? We already have IP Configuration Methods (along with one or more server addresses). If one of the server addresses is not listed then I think we can figure out that it was not available.$d416g5186jDelete this parameter.ppbut kept the same param in N2N response/confirm as it is unclear whether the comment applies to that case or notvmake this optionalw Principle{k) done 2007/12/1909/16/2007 03:08:31 EDTNoochengyuuheng.cypherdavidkhendersongregorys  disapprove5*p disapprove5hendersongregorys  disapprove disapprovehendersongregorys  disapproveJ$P disapproveJhendersongregorys  disapprove!8% disapprove!kimeunah  disapprove"approve"ryRef 260 (Duplicate){l) none needed 2007/12/1909/16/2007 15:23:06 EDTYes ENatarajan, Kadathur SF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d536g5066jlRemove the stack marked as "Remote Entity". Remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 347. (duplicated){l) none needed 2007/12/1909/16/2007 15:23:06 EDTYes  P disapproveRFS#PS disapproveTRFTsreemanthulasrinvias S disapproveU H%J'NjV(V disapproveWUjWsreemanthulasrinvias V disapproveXBYCrY disapproveZXBZsreemanthulasrinvias Y disapprove[W\\ disapprove][W]sreemanthulasrinvias \ disapprove^Q_v~_ disapprove`^Q`sreemanthulasrinvias _ disapproveae disapprovefdef vAThe name of these Net_HO commands need to change. " The Network controller provides a list of candiddate network choices to MN. The MN indicates resources required on each of these candiddate networks. The Network controller then queries each of the candiddate networks for available resources and reports this information back to the MN. Thereafter the Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagreey Ref Cmt 260{l) none needed 2007/12/1909/11/2007 17:47:21 EDTYes ENoens, Richard HF DisapproveGProducer^General_42`5a6.4.1c6Figure 16 is confusing. It shows two unrelated stacks.d101g5501jaRemove "Remote Entity" stack and remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 347. (duplicated){l) none needed 2007/12/1909/11/2007 17:47:21 EDTYes @@'@v{@jr@TcBv@UcAvvz@cApAx@cAMpA@cA%@ccAccAr@@pK@wLcA@ZccBi@%cB@cAvA@1jc@cS@@/{B@cApjAScA@<cc@@V@_d1@r@ vw@!vA(@5@,Q 3cA9MIH_NET_HO_Candidatate_Query Request should contain only Query_Resource_Flag, not List (as it is now). Network doesn't provide any resources at this point. It can only request MN to provide list of resource IEs the MN is interested to receive. MN will provide the list of resource IEs it is interested to receive.9d587g5015jFRemove list. The flag is also self evident, it can be removed totally.v7The QueryResourceeportFlag is NOT a list. OK to keep itwDisagree{l) none needed 2007/12/1909/16/2007 16:08:43 EDTYes s asrinvias w disapprovey disapproveztYzsreemanthulasrinvias y disapprove{,@~"|R| disapprove}{"}sreemanthulasrinvias | disapprove~ disapprove{@sreemanthulasrinvias ~ disapprove€tI€ disapprovet€sreemanthulasrinvias disapprove€&(eAJ€ disapprove&€icsEEastwood, Lester FF DisapproveGProducer^General_42`5a6.4.1c7Figure 16 is confusing by showing two unrelated stacks.d111g5491joremove the stack marked as "Remote Entity" and remove text "Local Entity" from the stack on the left-hand side.wAgreeyRef 347. (duplicated){l) none needed 2007/12/1909/12/2007 02:37:36 EDTYes [h vAThe name of these Net_HO commands need to change. " The Network controller provides a list of candiddate network choices to MN. The MN indicates resources required on each of these candiddate networks. The Network controller then queries each of the candiddate networks for available resources and reports this information back to the MN. Thereafter the Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. wDisagreey Ref Cmt 260{l) none needed 2007/12/1909/12/2007 02:37:36 EDTYes es FJ  vAThe name of these Net_HO commands need to change. " The Network controller provides a list of candiddate network choices to MN. The MN indicates resources required on each of these candiddate networks. The Network controller then queries each of the candiddate networks for available resources and reports this information back to the MN. Thereafter the Handover Commit happens" If the above explanation is true it needs to be captured and included in draft. The name of these commands/messageBs need to be changed as well. (Vivek or Qiaoboing, please read editor's note. BTW, should the decision of the group be changed to "principle?)}wDisagree{k) done 2007/12/1909/14/2007 14:42:22 EDTYess ve€!`€ disapprove€williamsmichaelg disapprove€€ disapprove € williamsmichaelg disapprove€! disapprove"B€"williamsmichaelg! disapproveNn3ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_68`14a7.3.5.2cRInconsistent on table formats for primitive parameters. e.g. P67 L32 v.s. P68 L14.d219g5383jjMake the parameters table format consistent throughout section 7. This applies to annex B also (e.g. B14).wAgree{k) done 2007/12/1909/13/2007 16:42:41 EDTNo the lastest draft. Another possibility is to move these into the LINK_PARAM_TYPE. ) wAgree{k) done 2007/12/1309/13/2007 16:42:41 EDTYes3ECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_68`14a7.3.5.2cRInconsistent on table formats for primitive parameters. e.g. P67 L32 v.s. P68 L14.d219g5383jjMake the parameters table format consistent throughout section 7. This applies to annex B also (e.g. B14).wAgree{k) done 2007/12/1309/13/2007 16:42:41 EDTNo %€> disapprove?=s€?chaplinclintf> disapprove€@ disapproveA=X€A"j\Make 'Requested Resource Set' parameter optional in both the response and confirm primitivesp Done in 378.wAgreeyRef 378{l) none needed 2007/12/1909/16/2007 02:47:09 EDTNo o # @ disapproveA?UAcypherdavidsreemanthulasrinvias @ disapproveB! jvB[n section 7.3.8.3 is not applicable due to updates in Cmt 428. (Please read editor's note)Iw Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_93`46a7.4.9cJJust providing MAC addresses of PoA is insufficient for network selection.d614g4988j+Please see the contribution #306 - CHANGE#2pAlready done in 615.vQAdopt contribution 21-07-0306-02-0000-Link-Detection-Update.doc with modificationw Principley Ref 615. {l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes s s S€UchaplinclintfT disapprove€V0]`[Y&W€W disapproveXV&€XchaplinclintfW disapprove€Y disapproveZV€ZchaplinclintfY disapprove€[ disapprove\V`€\chaplinclintf[ disapprove€] disapprove^V0€^chaplinclintf] disapproveNC^ Technical_80`60a 7.4.1.3.1c0Supported Transport List should not be optional.d203g5399jRemove "(Optional)" from Supported Transport List in MIH_Capability_Discover.{response,confirm} primitives and MIH_Capability_Discover response message.wAgree{k) done 2007/12/1909/13/2007 16:03:47 EDTYes s h disapprove€jk30:€k disapprovelj€lchaplinclintfk disapprove€m n3€n disapproveom €ochaplinclintfn disapprove€p disapproveq €qchaplinclintfguptaviveks disapprovetr€tchaplinclintfs disapprove€uTv!€v disapprovewuT€wchaplinclintfv disapprove€x disapprovey&€ychaplinclintfx disapprove€zu{p€{ disapprove|zu€|chaplinclintf{ disapprove€}X~@€~ disapprove}X€chaplinclintf$\ejAdd a status (result) the handover complete indication to account for failed handovers (i.e. completed but failed). Alternatively, define a handover failure as Old Link Identifier set to the same value as New Link Identifier.vsAdd a status (result) the handover complete indication to account for failed handovers (i.e. completed but failed).wAgree{k) done 2007/12/1909/16/2007 03:08:31 EDTNo o  `€ disapprove€sreemanthulasrinvias disapprove€ CVD€ disapprove €chenghong$levyjosephs disapprove€(!`€ disapprove€giesbertspieter-paul jettealan williamsmichaelgxieqiaobing disapprove€€ disapprove € williamsmichaelg disapprove€! disapprove"B€"golmienadawilliamsmichaelg! disapprove_| vfrom^WiWlWmWWWWWEWWWWWWWWWWfunctionWWWfunctionalityWWwWWW WfunctionsW}WfundamentalAWfunnyEWfurtherWwW(WfxWg0W1W2W<WuWWWgatewayWWgenerallyWWgeneratedWgenericWWT€colbanerika disapprove€  V<90€ disapprove€eastwoodlesterfguptaviveknatarajankadathursnoensrichardhxieqiaobing disapprove€'QIqrkadathurs disapprove€`S€ disapprove`€natarajankadathurs disapprove€1G€ disapprove1€natarajankadathurs disapprove€t€ disapprove€natarajankadathurs disapprove€vThe MAC Convergence Gateway Function as defined by TGu provides this functionality for 802.11. Appropriate interfaces are defined in TGu draft. 802.16 deal with this in similar manner as well.wDisagree{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes s approve€ disapprover€vanleeuwenrichardm disapprove€ disapprove€eastwoodlesterfguptavivekxieqiaobing disapprove€ disapproveS€guptavivek disapprove€E;R=)€ disapprove€guptavivek disapprove€'YVVtsttavivek disapprove€p% € disapprove€guptavivek disapprove€$€ disapprove€guptavivek disapprove€7€ disapprove€guptavivek disapprove€3P€T jQRemove this primitive or clarify its purpose. (Link_Handover_Imminent.indication)pPlease check again.v@Please refer to contribution 21-07-0430-00-0000-link-sync-eventsw Principle{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYes s 7P1pannexbupdatedaVannexeinformativebibliographyisarecommendationfromie9Vannexes/WanotherW#WWanyWapWapplicableWWWWWWappliedWappliesnWoWareWW W3WOWWW/WWWarq Was3WnWoWWWWWWW WOWtWWWWWWassignOWassignedW3WassignmentWassignmentsWatWWWauthenticationWauthority3Wautomatically WauxWavailableW WWbVW^WaWWb-12WWb132Wbasic4WbeWW0W3WVWWW^WWWWWWAWWWWWWWWWWWWWWWWWWWWWWWAWWWWWWWWWWWWWWWW disapprove€ :]jADMaking these parameters optional doesn't solve any problem. If the MIH User doesn't specify them, is it MIHF's responsibility? If not, then there is no possibility of mutually exchanging capabilities. The response, however, did not specify event and command as optional thus we are still left with the problems stated above.DvNo change required. This is true in principle but these are implementation specific issues and is not in the scope of this specification.w Principle{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNooQpintervalWintoWipWWipv6WisWWWWWWW*W9WKWLWMWNWWW^WnWoWxW}WWWWW WWWAWmWWWWWWWWWissueWitW WKWLWMW^WnWoW}WWWAWtWWWWWitisclarifiedthatit'slocalnodeonly}Vit's2W^W}WitemsWits3WWkeepWkeptnWoWkindEWkindoffunnythoughEVl17Wl2WEWkindoffunnythoughEVl17Wl2WWWl2WWWWWWWWWWWWWWWl346W6W6W6W6Wl386Wapprove€ disapproveD€rudolfmarian disapprove€5€approve5€famolaridavid approve€I*€approveI€<pgeneratedWWgeographicalWgetOWgetsWgivenWgoWgoingWgoneWgroupWWIWWWWWWAWW WgroupdiagreedVgroupdisagreedIVVVgroupdisagreedtoremovetheversionfieldandagreedtoadAVY8Zzh$€approve*€famolaridavid approve€ disapprove s€chenghong disapprove€%x14disapprove€ disapproveh€chenghong disapprove€ disapproveB€chenghong  disapprove€B € disapproveB€chenghong! disapprove€ h€ disapprove €chenghong" disapprove€ g€ disapprove €chenghong# disapprove€ (@€ disapprove rudolfmarian% disapprove disapproveXovevQAdopt contribution 21-07-0306-02-0000-Link-Detection-Update.doc with modificationw PrincipleyRef Cmt 615, 614.{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYess rudolfmarian+ disapprove disapprove  X rudolfmarian, disapprove disapprove  S rudolfmarian- disapprove disapprove rudolfmarian. disapprove ?2TI*P disapproveIrudolfmarian/ disapprove disapproveEgrudolfmarian0 disapprove disapproveE%rudolfmarian1 disapprove disapprove*rudolfmarian2 disapprove8f( disapprovefrudolfmarian3 disapprove disapprove8rudolfmarian4 disapproveb9p disapprovebrudolfmarian5 disapprove  ypAAdd the following paragraph at the end of this subclause: "In case of 802.11 networks, this notification is generated when the established 802.11 network connection is expected to go down within the specified time interval by the MSCGF The network may be expected to go down because of an event whose timing is well understood, such as an explicit disconnection event observd on the MLME_SAP. It may also be expected as the result of a predictive algorithm that monitors link quality. The detaiBls of such a predictive algorithm used are beyond the scope of this standard. This event is not generated when the 802.11 STA transitions from one AP to another in the same network."vlRefer to TGu draft (Vivek or Qiaobing, the remedy is in the Editor's note, Updated with Vivek Dec 05 email.)w Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYess disapprove;C<#< disapprove=;C=federperetzC< disapprove>##pprovides WpurposeWqiaobingthemihfalwaysknowsaboutthestatusanddescript2Vipt2V2Vgthemihfalwaysknowsaboutthestatusanddescript2V2V2Vpt2V2V2V2V2V㹃㺃㻃㼃sreemanthulasrinvias y disapprove{,@~"|RjR| disapprove}{"}sreemanthulasrinvias | disapprove~ disapprove{@sreemanthulasrinvias ~ disapprove€tI€ disapprovet€sreemanthulasrinvias disapprove€&(eAaJ€ disapprove&€vvUse clarifying text from TGu mapping draft. (AC: Changed from the Disagree to Principle, since updating text. Vivek or Qiaobing, please verify the text. Updated with Vivek email on Dec 05.)wDisagree{k) done 2007/12/1909/11/2007 17:46:47 EDTYes s ! disapprove€ `ih€ disapprove €chenghong" disapprove€ g€ disapprove €chenghong# disapprove€ R(@€ disapprove chengyuuheng/rudolfmarian% disapprove disapproveXvThe QoS is specified for access link and is not end to end. Specific Application level services are out of the scope. Vendor Specific IEs can be used to specify this.wOut of Scope/Unresolvable{l) none needed 2007/12/1909/11/2007 17:46:47 EDTYes s H€JjeffreetonyI disapprove€K disapproveLH€LjeffreetonyK disapproveƒ disapprove(eƒcypherdavidu disapproveƒ disapprove(Zƒcypherdavidv disapproveƒE2`ƒ disapproveEƒcypherdavidw disapproveƒ disapproveRƒcypherdavidx disapproveƒJ2Pƒ disapproveJƒcypherdavidy disapproveƒH' ƒ disapproveHƒcypherdavidz disapproveƒcypherdavid{ disapproveƒ disapprovedƒcypherdavid| disapproveƒ$$ƒ$ccThere is no information about ACCESS_NETWORK_IDENTIFIER which is an important for network selectiond623g4979j8Add "ACCESS_NETWORK_IDENTIFIER" as thee first parameter.vJAdd Access Network Identifier (HESSID for 802.11) as part of LINK_SCAN_RSPwAgree{k) done 2007/12/1909/16/2007 21:41:08 EDTYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_184`22aTable B4cSeveral locations where "MAC address" is used instead of a genric link id or address. MAC is a 802 term, should use a genreal term, which is already defined.d622g4980j correct itvChange it with LINK_ADDRESSw Principle{k) done 2007/12/1909/16/2007 21:41:08 EDTYes H {dodoneWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWWWWWW W"W$W)W,W-W.W6W:W;W<W>W?W@WAWBWCWDWEWHWKWLWMWNWOWPWQWRWSWTWVWXWYWZW^W`WaWbWcWdWeWfWhWiWjWkWmWnWoWpWrWsWtWuWwWzW{W|W~WWWWWWWWWWWWWWWWWWWWWWWQ~wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes s [yvthisisaconventionusedthroughoutspacesareusedintabl@throughout@to2{ztriggered&zun-authenticated@updated@user@ww-cdma@$will@&w@agreec ofprinciple0y612@cmtdeferred@deferredsameas497@)duplicate@oref@QDref397@aseecmt497@{disagrees@4do}doneH)=eeditordisagreesWeditoritodojinprogressk OQ>M=kdone;ll@Yes approve'€guptavivek disapprove€14!€ disapprove€guptavivek disapprove€@%\&:ZVS%P€ disapprove€eastwoodlesterfguptavivekstephensadrianp xieqiaobing disapprove€ p% € disapprove€guptavivek disapprove€$€ disapprove€guptavivek disapprove€ 7HlJ7€ disapprove€guptavivek disapprove€ v3P€,lTpreplacedHWreplacedreferencetovariableoctetswith8octetsinthefHVreplacementWrepresentWWWrepresentationWWrequestWW Wrequired2W WreservedWAWresolutionWWW[WWWWWWWWWresourceOWresources W W Wprove„Z disapprove[:„[stephensadrianp Z disapprove„\ disapprove]%„]stephensadrianp \ disapprove„^_aF„_ disapprove`^„`jeffreetony_ disapprove„a disapproveb^„bjeffreetonya disapproveE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_111`16a 7.4.20.3.2c6Font of parameters in list needs to be made consistentd526g5076jGFix the font. This is there is several other places in draft. Fix this.{k) done 2007/12/1909/16/2007 13:58:33 EDTYes E Gupta, VivekF DisapproveGGeneral Interest^ Technical_108a7.4.20cSeveral MIH Handover primitives use CurrentLinkIdentifier as a parameter. This parameter is not required since MIHF and MN implicitly know which link is currently being used.d525g5077jDelete CurrentLinkIdentifier from all MIH Handover primitives. A SourceIdentifer may be included if required wherever appropriate.vChange the CurrentLinkIdentifier to SourceLinkIdentifier for MIH_Net_HO_Candidate_Query response, MIH_MN_HO_Candidate_Query request and response.w PrincipleyRef 397{k) done 2007/12/1909/16/2007 13:58:33 EDTYes s s EDTMarkedYes FYes ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_87`31a7.4.4.cAA general comment related to event-subscription, link-detect and network commit to be used for network guided handovers. As a concept, the network PoS may not be aware or interested in the PoA specifics for handover selection and decision but only the network identifiers are sufficient to make the decisions. The attached usecase provides more information. Specification changes to support this are individually submitted. Note that these changes are useful even if applied individually to eacBh of the primitivesd615g4987j-Please see the contribution #305, 306 and 307p2„UstephensadrianpT disapprove„V disapproveW+3„WstephensadrianpV disapprove„X disapproveYP&„Ystephensadrianp X disapprove„Z disapprove[:„[stephensadrianp Z disapprove„\ disapprove]%„]?fYes gE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_231`1c~Many figures are missing the vertical/horizontal lines indicating where the messages and primitives are started and terminatedd167g5435jHPlace blocks in correct drawing software order so that the lines appear.wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes hE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_228`47c,Consistency with paragraph/bullet conventiond166g5436j!Add blank link between 9) and 10)wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes iE Cypher, DavidF DisapproveGGeneral Interest^General_226`1cDAnnex needs to be update for consistency to the rest of the documentd165g5437jLpage 226 line 60, missing list in supported_lcp; missing mobility managementwAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYesjE Cypher, DavidF DisapproveGGeneral Interest^General_224`1XnlpUpdate to MIH_Link_ActionswAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYes tvqwwxvqxrajkumarajay\wyz_Bzrajkumarajay]y{j||}{j}rajkumarajay^|~^vrajkumarajay_~dRSrajkumarajay`dCDrajkumarajayaiurajkumarajaybirajkumarajayc!).XYrajkumarajaydUWUWrajkumarajayeababrajkumarajayfu!rajkumarajaygrajkumarajayhurajkumarajayir"r OjXchange those datatype as LIST(datatype). 7.4.20.4.2, 7.4.21.3.2, and 7.4.21.4.2 as well.pDone in 7, 8, and assign new values in C2. Updates for MIH_MN_HO_Query_Resource response and MIH_N2N_HO_Query_Resource response: parameters DHCP Server Address, FA Address, and Access Router Address are changed to LIST.vA/Change to LIST(datatype) except for IP Configuration Methods. The layer 3 configuration applies to all the PoA candidates, not only one. There can be multiple candidates for DHCP, FA, Access Router for the POA. Multiple IP configuration method is already provided in the datatype of IP_CONFIG_METHODS. /w Principle{k) done 2007/12/1909/16/2007 03:35:02 EDTNoo jAj"A one-octet Selector field, followed by a variable length Value field. The Selector value determines the data type. If Selector==i, (i+1)-th data type in the list of data types DATATYPE1,DATATYPE2,[,&] is selected. The Selector field is encoded in increasing order of significance. The Value field is encoded using the encoding rule for the selected data type."jv# Plesae refer to 21-07-0396-01-0000w Principle{k) done 2007/12/1909/16/2007 15:56:25 EDTYes "ƒapprove%ƒheubaumkarlf approveƒapprove}Fƒheubaumkarlf approveƒapprove 5ƒkiernanbriang approveƒ disapproveC@ƒemmelmannmarc disapproveƒ disapprove(5ƒemmelmannmarc҃ disapproveƒ disapproveBQƒemmelmannmarc disapproveƒ disapprovee„emmelmannmarc disapprove„ disapproveR„a IN{k) done 2007/12/1909/16/2007 03:38:14 EDTYes s 1`122P2`3_3 3P3p34 q60n6pk6h67 c7@`7p] fwDisagreeyRef 612.{l) none needed 2007/12/1909/16/2007 21:41:08 EDTYes s 1€eastwoodlesterfgiesbertspieter-paul"natarajankadathursnoensrichardhxieqiaobing disapprove€t€ disapprove€eastwoodlesterfgiesbertspieter-paul#jettealan natarajankadathursnoensrichardhxieqiaobing disapprove€LUw Principle{k) done 2007/12/1909/16/2007 15:56:25 EDTYes s stvwxoylzbida^{_VXS[vE!s!0Z!@!`!p!!!"" "0"@"P"`"B"## ?#0M#@#PR#`H#;#A#>$S$ N$0K$@P$P$$0$%% %@%P%`E%p%B%(%=&& P&0&@:&P5'(' '0'@~'P2'`'p(U(@(P+(`(((()D) )0=)PE)p))%* kA*p**1:1@1P+1`122P2`3_3 3P3p34 q60n6pk6h67 c7@`7p]RvChange as follows on pg 83 line 27 " Registration request code. Depending on the request code, the MIH User can choose to either register or re-register with the remote MIHF "wAgree{k) done 2007/12/1909/13/2007 13:56:26 EDTYess M€Mchaplinclintfkohbenjamin'seifertrichL disapprove€N disapproveO€OchaplinclintfN disapprove€PQD$@€Q disapproveRP€RchaplinclintfQ disapprove€ST€T disapproveUS€UchaplinclintfT disapprove€V0]`[Y&W€W disapproveXV&€XchaplinclintfW disapprove€Y disapproveZV€ZchaplinclintfY disapprove€[ disapprove\V`€\chaplinclintf[ disapprove€] disapprove^V0€^chaplinclintf] disapproveU:vNeed some clarification for first part. (Refer to TGu draft for MIH mapping and add relevant text from there). OK for second part in draft and dont need to add any clarification. (L2 manager can also be on the netwok side...) w Principle{k) done 2007/12/1909/11/2007 17:46:47 EDTYess (€rudolfmarian disapprove€ disapprovep€rudolfmarian disapprove€ disapprove8€rudolfmarian disapprove€ disapproveD€rudolfmarian disapprove€5€approve5€famolaridavid approve€$G IT *€approveI€u4jDefine ARFCN, BSIC, GSM vs W-CDMA band by references to 3GPP specifications. Does PSC mean Primary Scrambling Code ? If yes, use the right name of the scrambling code identifier in the RRC specifications, cite it.vF21-07-0424-00-0000 OTHER_L2_ADDRESS can be combined with LINK_ADDRESSw Principle{k) done 2007/12/1909/16/2007 07:13:12 EDTNo o rajkumarajayrajkumarajaySA$rajkumarajay℃AvrajkumarajayA3rajkumarajayrajkumarajay<KZrajkumarajayNhrajkumarajayNurajkumarajay''p'rajkumarajay(8rajkumarajay+1rajkumarajay#O8vthisisaconventionusedthroughoutspacesareusedintablVthisisalreadyinthedraftVthisisjustanexampleVthisissupportedin802.16aswellbeforeauthentication VthisneedstobedonethroughoutthedocumentVthisseemsliketryingtomanageapriorityqueueandthisk(VthiswillbeaddressedbyathesecuritygroupVthiswillbehandledinthesecuritygroupVthiswouldapplytotheentiredraftVVthoseuWthoughW WthresholdWaWthroughWWWW{A^chengyuuheng@}|f&rajkumarajay@~qrajkumarajay@ disapproverajkumarajay@mccannstephen@‚‚5 ‚:a‚Rmontemurromichael@‚Zmontemurromichael@‚o disapprove‚ disapprove‚zunigajuanc@‚a‚karockipiotr@‚ disapprove‚ƒ  vinfoW<WWWinfoquerybinarydatalistVVinfoqueryrdfdatalistVVinfoqueryrdfschemalistVVinfoqueryrdfschemaurlVVnclintf> disapprove€@ disapproveA=X€ADcqWhat does "current link identifier" refer to, the source or target link identifier (as specified in the request)?d458g5144jEither change "Current Link Identifier to "Source Link Identifier" or to "Target Link Identifier". Alternatively, remove "Current Link Identifier" and add both source and target link identifiers.v=Change "Current Link Identifier" to "Source Link Identifier".wAgreeyRef 397{k) done 2007/12/1909/16/2007 03:38:14 EDTYess 1cIf the MIH Get Information primitive must contain at least one query list, that query list must include some required information. Specify the minimal information requried in the query.d326g5276jThe query information should include at a minimum, information related to the current PoA for the MN or a location. This information needs to be include somewhere in the draft - possibly in the protocol definition clause 8.6 or this clause.pMinor relation with Cmt 563.vMove this text to below the parameters table. At least one of the following parameters shall be specified: Info Query Binary Data List Info Query RDF Data List Info Query RDF Schema URL Info Query RDF Schema ListwAgree{k) done 2007/12/1909/14/2007 23:15:41 EDTYes EMontemurro, MichaelF DisapproveGGeneral Interest^ Editorial_153`5a8.6cGIt is very difficult to relate the primitives to the protocol messages.d325g5277pF jv^These are part of Service management category and group feels that is a better classification.wDisagree{l) none needed 2007/12/1909/16/2007 12:18:13 EDTYes ERudolf, MarianF DisapproveGProducer^ Technical_141`6a 7.6.1.2.2cMAccording to Table B-2 page 176, network error is indicated by code 4, not 3.d509g5093j Correct to 4pAsuperceded. the concerned text is removed by another tech commentwAgree{l) none needed 2007/12/1909/16/2007 12:18:13 EDTNo o o hong-yon?2 disapprove4 disapprove515lachhong-yon@4 disapprove689G!U77 disapprove86U8lachhong-yonA7 disapprove9 disapprove:68:lachhong-yonB9 disapprove;C<#< disapprove=;C=federperetzC< disapprove>- WMWmWWWWWWWWWW Wcommentnolongerapplicableduetoresolutionofcomment11VVVVprovez2{*P{ disapprove|z2|stephensadrianp { disapprove}&~& ~ disapprove}&stephensadrianp  ~ disapprove@GProducer^ Technical_151`43a8.4.1.1cAUIR bit usage is not clear. Which entity is supposed to set this bit? If MN is supposed to set this bit, how PoS? can trust that MN is authenticated when the bit is not set? The underlying assumption for the response limiting using this bit to work is not clear.d206g5396jZDelete the UIR bit or add more text that answers to those questions. (21-07-0373-00-0000)vTGu needs this feature in current version of draft. Other issues with this feature could be clarified separately. Please refer to contribution: 21-07-0373-01-0000w Principle{k) done 2007/12/1909/13/2007 16:03:47 EDTYes E„GgolmienadaF disapprove„H disapproveI='„IseifertrichH disapprove„J disapproveK'„KseifertrichJ disapprove„L disapproveM}a„MseifertrichL disapprove„N disapproveO}B„OseifertrichN disapprove„P= {kdoneVVVVVVV V!V"V$V)V,V-V.V0V1V2V4V6V:V;V<V>V?V@VAVBVCVDVEVFVHVKVLVMVNVOVPVQVRVSVTVVVXVYVZV^V`VaVbVcVdVeVfVgVhViVjVkVmVnVoVpVrVsVtVuVwVzV{V|V~VVVVVV /vAby comments 328 and 643 The table combines versions and features and does not provide the flexibility to indicate all existing combinations, as defined in 3GPP 25.306. Modify the Wireless UMTS Network Description as follows: Network: Wireless W-CDMA FDD Link Type: 23 Revision: (Revision) Bit 0: Rel-99/Rel-4 Bit 1: Rel-5 Bit 2: Rel-6 Bit 3: Rel-7 Bit 4: Rel-8 Bit 5-19: (Reserved) (Features) Bit 20: HSDPA Bit 21: HSUPA Bit 22: MIMO DL Bit 23: MIMO Bit 25: DL HOM Bit 26: UL HOM BBQit 27: CPC Bit 28-63: (Reserved) Acronyms could require definition in section 4 ?w Superceded{l) none needed 2007/12/1909/16/2007 07:13:12 EDTNo KEMyles, Andrew FF DisapproveGProducer^ Technical_52`48a6.5.5.2cVThe TYPE_IE_CONTAINER_NETWORK should contain the means to discover the 802.11u HESSID.d83g5519jAdd this capability.6„8zeiraeldad7 disapprove„9 disapprove:^„:golmienada9 disapprove„; disapprove<E„)0„> disapprove?=h„?golmienada> disapprove„@golmienada disapprove„A disapproveBZ(„BgolmienadaA disapprove„C disapproveDZ„DgolmienadaC disapprove„EF„F disapproveGE„GgolmienadaF disapprove„H disapproveI='„IseifertrichH disapprove„J disapproveK'„KseifertrichJ disapprove„L disapproveM}a„MseifertrichL disapprove„N disapproveO}B„OseifertrichN disapprove„P 6{doneWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W WeW*W3W9WWWWWWWWWWeeditordisagreesV*V3V9Vmannmarc$ disapprove„& disapprove'5C„'emmelmannmarc& disapprove„( disapprove)u„)emmelmannmarc( disapprove„* disapprove+8„+emmelmannmarc* disapprove„, disapprove-&„-emmelmannmarc, disapprove„. disapprove/!„/emmelmannmarc. disapprove„0 disapprove1zH„1emmelmannmarc0 disapprove @ @disapprove‚nQ‚julkavibhor@‚emmelmannmarc@‚ disapprove‚emmelmannmarc@‚soodkapil@‚‚ disapprove‚cypherdavid@‚:bƒ disapproveƒ< disapproveƒUƒ\@ƒ| disapproveƒ disapproveƒcypherdavid@ƒmylesandrewf@ƒheubaumkarlf@„ disapprove„1„P disapprove @ @3 AdB{CpDyEwFvGnHIJK^L_McN`OP QRjS TUVWXYZ[a\x]k^b_`iabmcd efghijklmgnoklmgno %jAIThe Annex overall should contain something like 3 parts, 1) normative definitions (former A to D), 2) something like a PICS or protocol conformance configurations (new, see comment in line 24), and 3) informative parts (like Annex F and G and H collapsed into one), a.k.a F becomes F.1 and G becomes F.2, H becomes F.3 and so on.I{d) confer with resolution group 2007/12/1909/16/2007 07:13:12 EDTMarkedNo &ERudolf, MarianF DisapproveGProducer^ TechnicalcAInter-operability requirements regarding minimum set of mandated MIH functions, SAPs, primitives, maybe depending on the combinations of access technologies and operation scenarios a MN supports are missing in 802.21 and make this specification more of a technical recommendation than an actual specification document. A solution must be found, or this draft spec will never see real-life deployment.d488g5114j)?! 2007/12/1909/16/2007 08:19:02 EDTYes s2 disapprove„4 disapprove5zI„5emmelmannmarc4 disapprove„67AP„7 disapprove86„8zeiraeldad7 disapprove„9 disapprove:^„:golmienada9 disapprove„; disapprove<E„)0„> disapprove?=h„?golmienada> disapprove„@golmienada disapprove„A disapproveBZ(„BgolmienadaA disapprove„C disapproveDZ„DgolmienadaC disapprove„EF„F disapproveGE„GgolmienadaF disapprove„H disapproveI='„IseifertrichH disapprove„J disapproveK'„KseifertrichJ disapprove„L disapproveM}a„MseifertrichL disapprove„N disapproveO}B„OseifertrichN disapprove„P cCdocument for 802.11 (21-05-0359r2) no such standard definitions in 802.11 terms existed. Without the detailed native definitions for the common terms, no functions can operate in a standard way. It is not clear to me how we may finalize a standard which is so incomplete. Perhaps the work should continue? In its current state the 802.21 document provides a coherent transport mechanism for various yet-to-be-defined IEs which are meant to translate into common MIH terms for use in common MIH DNfunctions. How can this work without the detailed media dependant definitions?d628g4974jComplete the command, event and information defintions for each of the common MIH terms which need translation into media dependent native terms for each of the media identified.v%Do a more complete mapping in Annex-Lw Principle{h) defer to next round 2007/12/1909/16/2007 23:32:08 EDTMarkedYesESreemanthula, SrinviasF DisapproveGGeneral Interest^General_193/pAgreed, but since text in the body may still change and hence the order in which the annexes are referenced may change too. Will do this in the last version.{h) defer to next round 2007/12/1909/13/2007 16:42:41 EDTMarkedNo WP>ÃW`=ÃWp<ÃW;ÃW:ÃW9ÃX8ÃX 7ÃX06ÃX@5ÃXP4ÃX`3ÃXp2ÃX1ÃX0ÃX/ÃY.ÃY -ÃY0,ÃY@+ÃYP*ÃY`)ÃYp(ÃY'ÃY&ÃY%ÃZ$ÃZ #ÃZ0"ÃZ@!ÃZP ÃZ`ÃZpÃZÃZÃZÃaÃa Ãa0Ãa@ÃaPÃa`ÃapÃaÃaÃaÃbÃb Ãb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@PE Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8cfamolaridavid approveS%approveSfamolaridavid approve  disapprove!!mccannstephen  disapprove"X#C# disapprove$"X$rudolfmarian' # disapprove%I&*P& disapprove'%I'rudolfmarian/ & disapprove( disapprove)P)rudolfmarian8 ( disapprove*+)+ disapprove,*,federperetzG + disapprove-8.*@. disapprove/-8/chengyuuhengU . disapprove0C1f3# 120C2rajkumarajayx1340f4rajkumarajayy35!6p6 disapprove75!7mccannstephen 6 disapprove8 disapprove99mccannstephen 8 disapprove _DT`DTDTDTs cAMIH_NET_SAP and MIH_LINK_SAP both specify abstract media-dependent interfaces. MIH_NET_SAP provides transport services over the data plane on the local node and MIH_LINK_SAP specifies the interface between the MIHF and lower layers. When transport services over L2 are used, MIH_NET_SAP becomes equal to MIH_LINK_SAP and is mapped to the real media dependent SAP such as LSAP or MLME_SAP that doesn't belong to data plane. It causes some duplication of SAPs for the transport services over L2 aB6nd also shows the inconsistency for the role of MIH_NET_SAP. For transport services over L3, we can use existing NSAP(Network SAP) and/or TSAP(Transport SAP), depending on the decision of MISHOP WG. As these SAPs are located under the MIHF, integration of MIH_NET_SAP and MIH_LINK_SAP would be a good solution.$d638g4964jIntegrate MIH_NET_SAP and MIH_LINK_SAP into MIH_LOWER_SAP (it can include NSAP and/or TSAP etc) and apply it to all related sections.vby comment 105w Superceded vAA Protocol Implementation Conformance Statement (PICS) Proforma cannot contain any information that is not already present in normative text. Therefore including a PICS Proforma would be redundant. Duplication of information within a standard has a tendency to cause inconsistencies. A PICS Proforma covers only conformance, not interoperability. Clause 8 describes the formats of messages used to exchange information. The description of when these messages are used are defined in claB-use 7 since they are triggered by primitives.wDisagree{l) none needed 2007/12/1909/03/2007 16:49:33 EDTYes }ÃQ0|ÃQ@{ÃQPzÃQ`yÃQpxÃQwÃQvÃQuÃRtÃR sÃR0rÃR@qÃRPpÃR`oÃRpnÃRmÃRlÃRkÃSjÃS iÃS0hÃS@gÃSPfÃS`eÃSpdÃScÃSbÃSaÃT`ÃT _ÃT0^ÃT@]ÃTP\ÃT`[ÃTpZJ !cDxcessive. It would appear to be impossible to assess the level of interoperability to be expected between two independent implementations that might claim conformance to this standard. d649g5603vThe use of shall and may within the draft 802.21 is as per the IEEE Standards Style Manual (Dated January, 2007). A PICS is not required part of an IEEE 802 standard, nor is a PICS created simply by doing a word search on shall and may.wDisagree{l) none needed 2007/12/1909/17/2007 18:08:47 EDTYes9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCÃCÃCwvupdatedW WW2WWWWupdatesWupdatingWWuponWtWupperW<WAWWurlW<WWWurltobeassignedneedstobeupdatedVuseWWWWWW+W,WWWWWWWuseanouitoidentifytheaccesstechnologyVuseclarifyingtextfromtgumappingdraftacchangedfromtVuselinktupleidinsteadVusetgumihcontribution11-2604rev2toupdatethereferencVusedWWWW&W'WiWwWWWWAWGWpW{WWWWWWusefulWWusefulness+W,WÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0Ãt@ÃtPÃt`ÃtpÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃuÃuÃv dDTAjProvide additional normative requirements related to the use of QoS in MIH. e.g. - make some; if not all, of the QoS examples of Annex K and related material normative.vAQOS is an important aspect of MIH and thats why MIH provides useful tools in the form of primitives and events in order to make use of measurements available at layers 1 & 2. The value of the MIH is not in defining new measurements in other technologies but in facilitating the exchange of information available. While the tools provided by MIH are all normative, the measurements available in other specifications are informative. wDisagree{l) none needed 2007/12/1909/16/2007 17:47:09 EDTNo Zx :vAQOS is an important aspect of MIH and thats why MIH provides useful tools in the form of primitives and events in order to make use of measurements available at layers 1 & 2. The value of the MIH is not in defining new measurements in other technologies but in facilitating the exchange of information available. While the tools provided by MIH are all normative, the measurements available in other specifications are informative. wDisagreeyRef Cmt 588. (duplicated){l) none needed 2007/12/1909/16/2007 17:59:40 EDTYesPvnormativeW&W'WWWWWWWnotWWWWWWWWWWWW&W'W/W0W2W5WAWOW]WuWwWWWWWWW&W(W8WAWWWWWWWWWWWWWWW WWnoteWWW^W WWWnothing5WWnowxWyWnullsWnumberWWW'WAW W WnumberedWobjectivesWobtainWobtainedWobtainsWofWWWWWWWWHD> 2007/12/1909/16/2007 10:24:17 EDTNo SÃUPRÃU`QÃUpPÃUOÃUNÃUMÃVLÃV KÃV0JÃV@IÃVPHÃV`GÃVpFÃVEÃVDÃVCÃWBÃW AÃW0@ÃW@?ÃWP>ÃW`=ÃWp<ÃW;ÃW:ÃW9ÃX8ÃX 7ÃX06ÃX@5ÃXP4ÃX`3ÃXp2ÃX1ÃX0ÃX/ÃY.ÃY -ÃY0,ÃY@+ÃYP*ÃY`)ÃYp(ÃY'ÃY&ÃY%ÃZ$ÃZ #ÃZ0"ÃZ@!ÃZP ÃZ`ÃZpÃZÃZÃZÃaÃa Ãa0Ãa@ÃaPÃa`ÃapÃaÃaÃaÃbÃb Ãb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@ 6wofWqWWWoutWqWWWoutofscope/unresolvableVqVVVprincipleᆃዃᑃᒃᘃᚃᛃᜃឃ᠃ᢃᧃᨃᬃᭃᮃᰃ᱃ᲃ᳃ᴃᵃ᷃ḃὃăŃƃ̃̓΃ЃԃՃփۃ ÃGPÃG`ÃGpÃGÃGÃGÃHÃH ÃH0ÃH@ÃHPÃH`ÃHpÃHÃHÃHÃIÃI ÃI0ÃI@ÃIPÃI`ÃIpÃIÃIÃIÃJÃJ ÃJ0ÃJ@ÃJPÃJ`ÃJpÃJÃJÃJÃQ~ÃQ }ÃQ0|ÃQ@{ÃQPzÃQ`yÃQpxÃQwÃQvÃQuÃRtÃR sÃR0rÃR@qÃRPpÃR`oÃRpnÃRmÃRlÃRkÃSjÃS iÃS0hÃS@gÃSPfÃS`eÃSpdÃScÃSbÃSaÃT`ÃT _ÃT0^ÃT@]ÃTP\ÃT`[ÃTpZP;xv,MIH_MN_HO_Commit command now for local only.w PrincipleyRef 407.{l) none needed 2007/12/1909/16/2007 03:08:31 EDTNoyERajkumar, AjayF GProducer^ Technical_121`55cIn order to be able to perform a local handover (i.e. replacement for switch command) the destination MIHF ID would not be remote.d405g5197jChange that the destination may be local or remote. Also, specify that it sends a MN_HO_Commit.request message to the destination MIHF only when the destination is not local.v,MIH_MN_HO_Commit command now for local only.w PrincipleyRef 407. (Duplicated with 406.){l) none needed 2007/12/1909/16/2007 03:08:31 EDTNoK |vwDisagreeyRef 10 (superceded){l) none needed 2007/12/1909/03/2007 16:49:33 EDTYes XvprimarilyWprimitiveWWWWAWiWkWwWWWprimitivesWWW&W'W@WfWwWWWWWWWWprimitiviesWprinciple]WwW WWpriorAWprioritizedWWpriorityWW(WproceduresWprocessW Wproforma&W'WWWWWproperlyWpropoganda6WproposedWprorityWWprotocolW&W'W<WWWW'WAW}WWWWWWW W WprovideW/WWWWWprovidewaysofsimplificationVa4,yseecmt4978VsupercededW&W'WWWWWsuperceedWWsuperceeded'WWsuperceededby48810VwithyW{cWcinstructionsunclearVconfer%Wd%Wdconferwithresolutiongroup%VdeferWWW/WWlvaddressedWWaddressesWadmissionWadoptWWWWWWWadopt21-07-0317-01-0000Vadoptcontribution21-07-0305-02-0000-edocwiththefollowiVVVadoptcontribution21-07-0306-02-0000-ldocwithmodificatioVVadoptcontribution305-2withmodificationVadoptionWadvertiseWafteruWagainst WaggregateWagreedWWagreedtexttobesuppliedbynadagolmieVagreementwWalgorithm<W{WallWWW W,W/WOWWWallprimitiviesinsection7wouldneedtobeexaminedcarefVall-zerosWallow0W ycmtWWW4y612W614W615WWWW618W621W624W88WasW Wby'WWcmtWWWWWWW&W'W8WWWWWWWWWWW WW#W$WMWWWWW#{ vAA Protocol Implementation Conformance Statement (PICS) Proforma cannot contain any information that is not already present in normative text. Therefore including a PICS Proforma would be redundant. Duplication of information within a standard has a tendency to cause inconsistencies. A PICS Proforma covers only conformance, not interoperability. Clause 8 describes the formats of messages used to exchange information. The description of when these messages are used are defined in claB-use 7 since they are triggered by primitives.wDisagreey Ref Cmt 10.{l) none needed 2007/12/1909/03/2007 16:49:33 EDTYes  vpicsWWWplacedWplacementWplacesW WWplanesWpleaseWWWWWWWWWW W6WVW\W^WkWlWmWtWWWWWWWWWWWWW W W@WMWWWWWWWWWWWWpleaselookatcontribution21-07-0302-00-0000Vpleasemakechangesaspercontribution21-07-0414-02-0000-3Vpleasereferto21-07-0191-00-0000VVpleasereferto21-07-0308-01VVpleaserefertocontribution21-07-0302-01-0000-sVVVVVVVVVVVpleaserefertocontribution21-07-0317-01-0000-sinformatioVpleaserefertocontribution21-07-0320-02-0000 Vpleaserefertocontribution21-07-0320-02-0000-rdefinitionVVVVpleaserefertocontribution21-07-0373-01-0000@VvincludingWWWincompatibilityAWinconsistencies&W'WWWWWincorporateWincorporatethenewreferencediagramfromtgudraftVincorrectWincrease1Wincreasethelengthtounsignedint21VincrementedAWindicate/WiWindicatesW W WWWWindicationWeWfWtWwWWWAWindicationsWindividualWinferWinferences5WWinfoÃePÃe`ÃepÃeÃeÃeÃfÃf Ãf0Ãf@ÃfPÃf`ÃfpÃfÃfÃfÃgÃg Ãg0Ãg@ÃgPÃg`ÃgpÃgÃgÃgÃhÃh Ãh0Ãh@ÃhPÃh`ÃhpÃhÃhÃhÃiÃi Ãi0Ãi@ÃiPÃi`ÃipÃiÃiÃiÃjÃj Ãj0Ãj@ÃjPÃj`ÃjpÃjÃjÃjÃqÃq Ãq0Ãq@ÃqPÃq`ÃqpÃqÃqÃqÃrÃr Ãr0Ãr@ÃrPÃr`ÃrpÃrÃrÃrÃsÃs Ãs0Ãs@ÃsPÃs`ÃspÃsÃsÃsÃtÃt Ãt0Ãt@ÃtPÃt`ÃtpÃtÃtÃtÃuÃu Ãu0Ãu@ÃuPÃu`ÃupÃuÃuÃuÃv dDTÃTYÃTXÃTWÃUVÃU UÃU0TÃU@SÃUPRÃU`QÃUpPÃUOÃUNÃUMÃVLÃV KÃV0JÃV@IÃVPHÃV`GÃVpFÃVEÃVDÃVCÃWBÃW AÃW0@ÃW@?ÃWP>ÃW`=ÃWp<ÃW;ÃW:ÃW9ÃX8ÃX 7ÃX06ÃX@5ÃXP4ÃX`3ÃXp2ÃX1ÃX0ÃX/ÃY.ÃY -ÃY0,ÃY@+ÃYP*ÃY`)ÃYp(ÃY'ÃY&ÃY%ÃZ$ÃZ #ÃZ0"ÃZ@!ÃZP ÃZ`ÃZpÃZÃZÃZÃaÃa Ãa0Ãa@ÃaPÃa`ÃapÃaÃaÃaÃbÃb Ãb0Ãb@ ÃbP Ãb` Ãbp Ãb ÃbÃbÃcÃc Ãc0Ãc@ÃcPÃc`ÃcpÃcÃcÃcÃdÃd Ãd0Ãd@ÃdPÃd`ÃdpÃdÃdÃdÃeÃe Ãe0Ãe@Ãe@ÃDÃD ÃD0ÃD@ÃDPÃD`ÃDpÃDÃDÃDÃEÃE ÃE0ÃE@ÃEPÃE`ÃEpÃEÃEÃEÃFÃF ÃF0ÃF@ÃFPÃF`ÃFpÃFÃFÃFÃGÃG ÃG0ÃG@ÃGPÃG`ÃGpÃGÃGÃGÃHÃH ÃH0ÃH@ÃHPÃH`ÃHpÃHÃHÃHÃIÃI ÃI0ÃI@ÃIPÃI`ÃIpÃIÃIÃIÃJÃJ ÃJ0ÃJ@ÃJPÃJ`ÃJpÃJÃJÃJÃQ~ÃQ }ÃQ0|ÃQ@{ÃQPzÃQ`yÃQpxÃQwÃQvÃQuÃRtÃR sÃR0rÃR@qÃRPpÃR`oÃRpnÃRmÃRlÃRkÃSjÃS iÃS0hÃS@gÃSPfÃS`eÃSpdÃScÃSbÃSaÃT`ÃT _ÃT0^ÃT@]ÃTP\ÃT`[ÃTpZÃT`[Ã3@/Ã3P.Ã3`-Ã3p,Ã3+Ã3*Ã3)Ã4(Ã4 'Ã40&Ã4@%Ã4P$Ã4`#Ã4p"Ã4!Ã4 Ã4Ã5Ã5 Ã50Ã5@Ã5PÃ5`Ã5pÃ5Ã5Ã5Ã6Ã6 Ã60Ã6@Ã6PÃ6`Ã6pÃ6 Ã6 Ã6 Ã7 Ã7 Ã70Ã7@Ã7PÃ7`Ã7pÃ7Ã7Ã7Ã8Ã8 Ã80Ã8@Ã8PÃ8`Ã8pÃ8Ã8Ã8Ã9Ã9 Ã90Ã9@Ã9PÃ9`Ã9pÃ9Ã9Ã9Ã:Ã: Ã:0Ã:@Ã:PÃ:`Ã:pÃ:Ã:Ã:ÃAÃA ÃA0ÃA@ÃAPÃA`ÃApÃAÃAÃAÃBÃB ÃB0ÃB@ÃBPÃB`ÃBpÃBÃBÃBÃCÃC ÃC0ÃC@ÃCPÃC`ÃCpÃCÃCÃCÃCÃ"pÃ"Ã"Ã"Ã#Ã# Ã#0Ã#@Ã#PÃ#`Ã#pÃ#Ã#Ã#Ã$Ã$ Ã$0Ã$@Ã$PÃ$`Ã$pÃ$Ã$Ã$Ã%Ã% Ã%0Ã%@Ã%P~Ã%`}Ã%p|Ã%{Ã%zÃ%yÃ&xÃ& wÃ&0vÃ&@uÃ&PtÃ&`sÃ&prÃ&qÃ&pÃ&oÃ'nÃ' mÃ'0lÃ'@kÃ'PjÃ'`iÃ'phÃ'gÃ'fÃ'eÃ(dÃ( cÃ(0bÃ(@aÃ(P`Ã(`_Ã(p^Ã(]Ã(\Ã([Ã)ZÃ) YÃ)0XÃ)@WÃ)PVÃ)`UÃ)pTÃ)SÃ)RÃ)QÃ*PÃ* OÃ*0NÃ*@MÃ*PLÃ*`KÃ*pJÃ*IÃ*HÃ*GÃ1FÃ1 EÃ10DÃ1@CÃ1PBÃ1`AÃ1p@Ã1?Ã1>Ã1=Ã2<Ã2 ;Ã20:Ã2@9Ã2P8Ã2`7Ã2p6Ã25Ã24Ã23Ã32Ã3 1Ã300Ã23