Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.00 )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&`wanghleiUwang2nv0W1WW102W105W⹃ $WW106W⸃ #WW114W118W14W2W23EW238W363W3gpp/3gpp2W4W5W52EW556W590W6W7W7.4.15W7.4.17W802W802.11W802.15W802.21W98WaWaboveWacronymGWacronymsGWacrossWactionWactionsWWaddWaddegatthestartingofnextlineVaddedWadditionalWaddressWWaddressedWaddressesWanWWWWandWWEWWannexEWanyWapplicableWapplyWareWWGWasWWWGWWaspecificEWaspectsWassignedWenceWmappingEWmayWmediEWmediaEWmentionedEWneedsWWnon-zeroWofWEWonlyWparameterWreasonWreferenceWK 9@AOKA/A0@@A-A.@A,A-Cancel@A*A+@@A* ;X( `Before importing, Find the records eligible for proposals by this Clause Editor. Only these records will be affected by the import. ABCdD^EiFmGjHkIJKLMNO_P`QaRbScTgUnVpWvXwYxZy[{\]^_`abc d e fghijklmnoQ:ASort by RecommenderE'` iDT_DT`DTDTDTQÃY0?ÃY@@ÃYPAÃY`BÃYpCÃYDÃYEÃYFÃZGÃZ HÃZ0IÃZ@JÃZPKÃZ`LÃZpMÃZNÃZOÃZPÃaQÃa RÃa0SÃa@TÃaPUÃa`ZBUUX  w  $,.YesNo/,  , : AM PMf  HelveticaGenevaVerdanaTimesMonacoTimes New RomanArialCourierSymbol Courier New@ A PICT,alisNAMEMSPCFPTHA9Macintosh HD:Desktop Folder:Ballot#2:802.16.2 Ballot Data9MSPCAQnNAMEA802.16.2 Ballot DataRPTHA802.16.2 Ballot DataalisC-`@@XA Comment List@@*AAbout Commentary@@PACreate Comment@@fACreate and Submit Ballot@@AGlobal Field Setup@@ AEditor's Layout@@AComment List for Printing@@ AComment List for Projection@@ACommentary Version@@@AReply Comment Layout@@ ASubmit Reply Comments   A Comment ListB   vor/ 11 against wRejected{l) none needed 2001/10/24»ETG3/4 MAC group^Technical, Bindinga6.2.XbFAdd new ARQ text found in document 80216abc_01/75 to the WG document. d339g2541wAccepted{k) done 2001/10/24 2001/09/11¼E TG3/4 MAC^Technical, Bindinga6.2.xb'Add a standalone NACK feedback message.d340g2542vneed accepted textwDeferred{l) none needed 2001/10/24 2001/09/13½E TG3/4 MAC^Technical, Bindinga6.2.xb Add RNR feedback message for ARQd341g2543vneed accepted text 2001/09/13D$aGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #{ Document #Report # B A € € € €€ €   G!MKe!MKG*fQjugD€QASDocument under Review€XAYLetter Balllot Number€^A_VoteaGlobal Field Setpb // etpb // etpb // etpb // tpb // b // b // d Setpb // Setpb // tpb // Setpb // b // ld Setpb // d(2) Save Data to Filee(3) Email Data Fileail Data File54 RB 3  $,.YesNo/,  , : AM PMC 3  $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMnD a w n w  $,.YesNo/,  , : AM PMo  w p w  $,.YesNo/,  , : AM PMq  w r w  $,.YesNo/,  , : AM PMs  w t w  $,.YesNo/,  , : AM PMu  w z w  $,.YesNo/,  , : AM PM{  w  D^"M1,,./: AM PMYyTtNnFfNALL OFMPRP^SundayMondayTuesday WednesdayThursdayFridaySaturdayJanuaryFebruaryMarchAprilMayJuneJulyAugust SeptemberOctoberNovemberDecemberQ1Q2Q3Q4 1st Quarter 2nd Quarter 3rd Quarter 4th Quarter,  , AXLS Sheet1X5CMY m]oApFfWyHCB-wang., .lei]} A1FPTH=RPTH NAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9NFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A9OFPTH=RPTH alisNAME MSPCMSPCA NAMEA 80216Ballot RPTHA 80216Ballot A10FPTHXRPTHNAMEMSPCMSPCA2NAMEANumberLastFirst.USRRPTHANumberLastFirst.USRA19uFPTH^RPTHNAMEMSPCMSPCA2NAMEANumber_Lastname_FirstnameRPTHANumber_Lastname_Firstname ot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisA NAMEA 80216Ballot RPTHA 80216Ballot alisVDEF(LISTLISTVDEF(LISTLIST(:K?@MRS Y!^"CAStartup scriptEQADelete Empty RecordsE@ @b*QA Show VotesE@@H-Already voted; submitting additional commentsQASort by Page/LineE'` _DT`DTDTDTQASort by Comment OriginatorE'` DTDT_DT`DTQADelete All RecordsE@ @b*QADelete Abstain CommentsE@ @HAbstain for other reasonsQAShow Editor's ProblemsE @'`@n* _DT`DTDTDTQASort by Comment #E '` dDTQ8 €Bied in recommending rejection on grounds of incompleteness or lack of a specific change request. (3) When you are finished entering replies, look under Scripts and choose "Find Marked Records". This will find the records for which you checked the "Marked" box. (4) Put your name in the "Recommendation by" field of each reply {for a quick method, see Appendix below.} (5) Under Scripts, choose "Export Clause Editor's Proposals". Choose the file type "FileMaker Pro Runtime Files". Enter a Cfile name of the form "BallotNumber_LastName_Firstname.USR", where "Name" is your name. (6) Email the exported file as an attachment to: --------------- Appendix: Using "Replace" in Commentary You can replace everything in a particular field over a batch of records. For example, clause editors might not want to type their name in the the "Recommendation by" field each time. Here is a solution to the problem illustrating the use of "Replace": *Finish entering your data. *Find the bacAEditor's LayoutB   S w  $,.YesNo/,  , : AM PMT w  $,.YesNo/,  , : AM PMU 3 $,.YesNo/,  , : AM PMV 3 $,.YesNo/,  , : AM PMW 3 $,.YesNo/,  , : AM PMYesNo/,  , : AM PM9 Dp=u Av 2 72w27+-f3%:EAFAGA' Submitted by:€QASDocument under Review:UFirst (Given) NameVLast (Family) NameWBallot Group Membership Status:€XAY#Letter Ballot Number or Ballot Code€ZA[ email address€\A] telephone€^A_Vote:`(1) Create Comments€aAHCreate and Submit Working Group Ballot or IEEE Balloting Center CommentsH@AR  33& * Rg2*t {EQFAImport CommentsENALL OTABS# ` ABCDEFGdH^I_J`KaLbMcNOPQRgSiTjUkVmWnXpYvZw[x\y]{^_`abcde f g hijklmnoQGA Email fileE)?@ @A owner-stds-802-16@majordomo.ieee.org The comment file name should include the Letter Ballot Number and  ABCDEFGHdIJ^K_L`MNaObPcQiRmSjTkUvVwWxXyYZ{[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@@G@7I@Q@j@€‚kohbenjamin@ @ @P;xtnorhasitanymeani@dthetermburstprofileisdefinedinthestandardasdefinit@toclarifydocument@d@B@2A@@@cJ@c@M @ @3P;@3P; @3P; @3P;7WNWWWYWbWdWeWhWWWWWWWWWWWWWW)W/W5W8W=W>WBWDW`WhWmWWWWWW?WgapWWWW WW#W$W%WgenerateWgenerated4W6WWWWgeneratingWgenericWgetOWWWgetridofdashthisisaproblemallthroughoutsection6.2OV4/ RM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMBkS-X bWmkwj,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    M€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€ (ENadaFGolmieGMember^Technical, Non-binding_6`54a2bAdd ITU-T Recommendation X.690 : Information technology - ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER) at position 31 and reorder the remaining list accordingly.cXSince ITU-T Recommendation X.690 is referenced 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 sBl#. .#  al# cl#  bl# Bmv#  @iv# sj{#v Dkvv# 8w#f,Cjvf# 0x# V  2y V# 2 # F 6{ F# In # 6 qp 6# LF 8w#/,v/# 0/ Y w $,.YesNo/,  , : AM PMZ w $,.YesNo/,  , : AM PM[ w  $,.YesNo/,  , : AM PMabcd€€€€€€€€€€€€rQ RA 3 $,.YesNo/,  , : AM PMB 3 $,.YesNo/,  , : AM PMC 3 $,.YesNo/,  , : AM PMD  3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMPR RF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMx+!  2y! 4z! 6QS RK 3  $,.YesNo/,  , : AM PML  3  $,.YesNo/,  , : AM PMM 3 $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMO 3  $,.YesNo/,  , : AM PMRT RP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PMT 3 $,.YesNo/,  , : AM PMSU RU  w $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMW 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY 3 $,.YesNo/,  , : AM PMTN OZ 3  $,.YesNo/,  , : AM PM[  3  $,.YesNo/,  , : AM PMA#x x#  #; d;# ##+ #+# ## # ^ #k  _lk#  `Nh R @BBA6 6^_` a b c dijkmnpvwxy{€€€€€€ ++++++++ + +  +  +  + + +++++++++++++X5XX/X1XXXX X3 X X  X  X6X XXX$X"X X&XXXX,XXXX)X+-*,6{7TypeReason k b 3  $,.YesNo/,  , : AM PMc   d  3  $,.YesNo/,  , : AM PMe   f   g 3  $,.YesNo/,  , : AM PMh   i   j 3  $,.YesNo/,  , : AM PMk   l 3  $,.YesNo/,  , : AM PM-dG | w  $,.YesNo/,  , : AM PM}  w ~ w  $,.YesNo/,  , : AM PM  w  w  $,.YesNo/,  , : AM PM  w A^a):|+=9}R~T=b=NR?+M^ance'd303 2001/08/28G6AReply Comment LayoutB U 3  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX 3  $,.YesNo/,  , : AM PMY   Z 3  $,.YesNo/,  , : AM PM[   \ 3  $,.YesNo/,  , : AM PM]     [A, HH HH*<*G!!!!!!!!1111111111 11 11 11 9999 99999999BBBBBBBBJJJJJJJJJJJJRRRRRRRRRRZZZZZZZZZZZZ ZZ!cccc"cc#cc$cc%kkkk&kkkk'kk(kk)kk*kk+ssss,ssss-ss.ss/ssB0{{{{1{{{{2{{3{{456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmZ\ Cnopqr!!s11tBBuRRvccwssxyz{|}~D[] Ek0>nk&8n]n]n!=700UnUnUfa&fH!1fQ!H,bH,Hn\X8FU7=nXnH7%fQH 7k=8HnX10kHbHHgfn=\HX7X8HHf\]?no`_`_`_`_`_`_`_`_`_`_`_`_`_`B]n` [    `    `    `n&0n4WUfZ _ZZZ._ Z)$')d)$')d\^ G)')$h#`` ) )B)y}_ Z ' ' Dyy3sy~[_  )  ) B|uv7~qu|t_Z ( ( Brz}rs9|pr}up|_ ` ) ) Bzprypq~<yppy~pps`_ ' ' @rpp{upp|?vppuvpzZ[ ) ) Ezpt}rppyAsppr}~pr_ _ ' 'Bqp|ypvB~qpyxpz[ ` ) ) BHxpvups@|ptqpr_ Z # #@qp~}rpq~Iypq|ypz_ _E BEB`E BEBmE 'BEBmxpvyp|SX&&Xvpqpr` [  A Z Zqpy8=SHHspzZ _  @  `  `xpv,5^kn~qpr_ [[  _Z`l[  __Yo[ 6__[oqpqrpsbfS=X|pvzpy_ _ ' ) Bxpq}wpq}=]_ IXU7Uyp{zqppq`_ ) ' Bqppq}~p{=TW\fvpr}qppxZ [ ' ) DwppsspxfgT0spw}qpq`  _  '  'A~ppszpu08]n%7~qpp~}qpxZ _ BBEBm BBEBm 'BBEBmvpsppsHQH|ps}qq` [ `  ` _~psvq}Dyz~sx_ _  Z  Z [Jvu|{9to_Z_o__[Z__[^o__[Z__[^o_[^Z_`Z^o~v }~o_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`_`m`                                                                             @lBB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB^` K@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@BB?BB@AB@BA@B_ fXX]XfkJ78H7k=aXH 007U!,7kX8HXU7TT8X7TX77XXXf77`QHU8bk1TnaXfgWU77L7%7XX\ n17&7nbT] Xb!78=HUUXWUTX7 X7TY07=\7Xk Q%QX777b]1n=5n7H8Q!8nn_a M7!Qn=!H% 7TX,XfUXn,7,a bHb7jn &HU\TX$WT878gnn8H W8L7AUXHn8nH,H88N 7X&78=;XT%X7=7&0&0n, n!7HX00T(TXfnn777 H8& X7T7778n XTX778Tbkb H=X!`b O=T TXM*HU7T7&Q= 7Tn7%UW& XTX.7,n7&H%H8,X7gn7 TXT7A78nXH&=TXf7&Q7 PXTX 8n7]&]n7TX8jUQ TXU=n7\gn3n7XHUk=7,+U XTWUH87nn3X8WU77f78 TXUn= 7ac QU7U78&QQ XUX bfb7==nX17!8717W177&7nUT TWTH8fX&k8UUn7771 XUX77j&W7 WX bR8nH7 TXT\7&XUkH8U U77TX XTXn%88=&gC!\7 WX 77nXTUnfXTagWUTgWUTi)())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())())(be S))())RZ                                                    B'S66SmB3BmK63BmVEBBPE.R8|o" *e VK S) i )}=}t<  K o  e   '~tFxy}qx ZV V)Pe2 6V R `vs|zWX!Q{ps}qq  <JR 3` )  A~psuTq}84n]H5}qpp}}qpx  ) _e Z ' o xpsppr5dngspw}qpqm  l <. Vqps~yptk]gX=upqzpy  I: . i J  B )3Sxppq}spwU7fU7xp{zpr V _  Z` l  ;   6qppq}}p{W=ef]{puzpz o  oZ  `2  "  `xpX $%       !ACommentary VersionB ( a w hh h h h h  h hhhhhhhhh!hh$XX,XXXX)X+X5X3c Uq}wpq}nf]1&}qpr 6  <`  ' _m N  */B 6qpqqpsH7Q78spz  lZZ ) `6   ' @_ xpuUQFupqpr V  `_  Z F  ) B qpxLxpr}zpz B ') Io  `P  " B xpwzqp{Q{puqpr BB' B e39 *@ qp~}spq}S}qppqyxpz@;)Bm e 'B  VzpvvpsQspps}qpsE '' R) Zi m   B; rp}zqppuUuppvvp|S  _6IN3_ )`EBmO '_ zpt}sppxQxpqz~ppt `R V)*NO @BYm  B 6rpp|vpp{P{ps}vp|6  ;  oB  E@` 3_zpszqq}L}qv|t oV NEBBZ m <rz}ssCtz~oI)"Ie6)6_cBB@@B@__@BlBB@l<)-V|vui [ w  $,.YesNo/,  , : AM PMA#K dK# ##; #;# # ^#0  _l0#{  `l{# #k  alk# c^_#  _l#  `l#m  av CgTgvh ivTjxivPk#TlPm&3Tn{&h3Po pDw6YTqp&3`Pr nTsj{tTuivcPvXTwmvPxTykvq~l6V~%AAbout CommentaryB\   A wB w I N w  $,.YesNo/,  , : AM PMO W  $,.YesNo/,  , : AM PMX $,.YesNo/,  , : AM PMPMPMPMPMPMPM   $,.YesNo/,  , : AM PM  w ` D .orgl>.;tf ZU  w  $,.YesNo/,  , : AM PMV 3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMX  3  $,.YesNo/,  , : AM PMk, w  3 $,.YesNo/,  , : AM PMx   y 3  $,.YesNo/,  , : AM PMz   {   | 3  $,.YesNo/,  , : AM PM}   ~ 3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM     rksa_2Wj m   n 3 $,.YesNo/,  , : AM PMo   p  w $,.YesNo/,  , : AM PMq 3  $,.YesNo/,  , : AM PMr   s 3  $,.YesNo/,  , : AM PMt   u 3 $,.YesNo/,  , : AM PMv   '   B@\[)!r S // €TA€UA€VA€WA€XA YType€ZA[Suggested Remedy€\A ]Starting Page #€^A _Starting Line #€`AaSection€bAcComment€dAe Comment #fComment submitted by:€gAhResolution of GroupiDecision of Group:€jAk&Reason for Group's Decision/Resolution€lAmGroup's Action Items€nAoEditor's Actions€pA€qArEditor's Notes€sAtProposed Resolution€uAvRecommendation by€wAxRecommendation:€yA=AB=AB[Ab  !"#$%&'()*+,-./012345b& v   $,.YesNo/,  , : AM PMww   3 A0@*E0:@F {G0Z=' QkS%26U%92VLWiyl XU%92VLWiyl 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 GL5603iA 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 DataI@EdREEdREECcAdREEREEREECcAdREEREEREEREEREcAdREEREAdREEdREEdREEdREECcAdREEdREEdREcAdREEREEREEdREEdREEREEdREEREEREEREEdREEdREEcAdREEdREEREEREEcAdREEREEdREREEREEREEREEdREEcAdREEREEdREEdREEREEREEdREEREEREEdREEREEREEREEREEREEdREEGGeneral 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." 2007/09/1909/16/2007 10:24:17 EDTNoEFamolari, DavidFApproveGGeneral Interest^ Technical_198`38cfTable B-15 -Data type for RDF information query: Wrong default value has been specified for MIME_TYPE.d504g5098jIn 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" 2007/09/1909/16/2007 10:24:17 EDTNoEFamolari, DavidFApproveGGeneral Interest^ Editorial_103`19d503g5099 2007/09/1709/16/2007 10:24:17 EDT07 23:51:48 EDTYes/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/20hEAjayFRajkumarncommentcouplesWWWWWlesWWWWWWesWWWWouplesWWWWWWWWWWWWWWWWWWWWWWWWWplesWWWorWfoundWifWifanewlyarrivedmihprotocolmessageisfoundtocarrythVinWisWlinkWlooseWmagicWmakeWmayWmessageWWmessage-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 WanythingWWanywhereWWapWWWWWWWWapartWWapiWappear!W[W/WappearanceWappears=WFWbWnWoWWWW WWWWWapplicableWWJWWWapplicationWW(W<Wapplication'sWappliedWPWWappliesW0WWWWWWW<WappropriateWWWWtWWappropriatelyWWWapproximatelyWapsWarbitraryW'WarchitecturallyWarchitectureWWWWWWWWWW_390سسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسسس| cd‚@wÃ1@ÃB@ÃS@Ãd@j21-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@lacebitmap64withrevisionintherawo@available@Mbeen@nbot@capable@&case@changedescriptiontoabitmapnwherenmustbeamultiple@changen2nhocompletetomnhocomplete@changerequestisreceivedtorequestmessageisreceived@0changethetexttoclearlyspecifyhowthedestainationofe@dchangetothelinkdetectedeventisgeneratedonthemnwhe@fytypesonthelocalmihf@f cAj1) 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. j`>^_ !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℃⅃Ↄ3 ABCdDE 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:g^_`abcd€€€€€,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5Bf9f9" disapprovestↃ‚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ݏݐݑݒݓݔݕݖݗݘݙݚݛݜݝݞݟux@EAjay: 0v@s`pp#!k"#$%& '()Z* 1h2 3e46W78:bA~B{CDEF_GHIJQR{STUuVWXYSZaGbctdDhWN{XZ[cx!`!0G!@!`!!!~"" "0"@"P"`"B"## ?#0M#@#PR#`H#(#.#+$@$ ;$08$@K$P$$%% %@%P%`@%=%%8&& 9&@5&P0'P-'p(U(@(P&(`#(()1) )PE)p)) * X*@*P*`**p*1#1@13L3 3P909P/9p "Qdj0/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(W7WwacceptedᇃɃ!%FGH㏃㤃accepted-modifiedăƃ⣃Edeferredᚃȃ&<⦃⧃⨃rejected㚃Ńƃsupercededƒ܃⤃⮃Ⰳ⸃⹃ #$㨃㫃{e^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ؠ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.21sV10WW10.1W10.6W100NW10000200wW10000302wW107qW10e-3W11WWWWW4WWW5.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 Dxamining - IEEE 802.11 D9.0 - IEEE 802.11k D7.0 - IEEE 802.11r D4.1 - IEEE 802.11.2 D0.12 (t) We found a primitive that might fulfill the mapping28;bc12@21-05-0359r2@3.40@38-52@5.1.2@O8-26@8.6forextendibilityofmihthereisaneedtoallowdefini@"a@hasimilarmechanismmaybeavailableforieee802.16forthi@abbreviations@accomplished@Lacknowledgement@actual@!addressing@yalongnalready@=alsoi@amend@Ganoanalog@and$andparameterextractioncommandsmissinghyphen@andthismessageistransmittedovercontrolplaneusingl2@annex@ annexes@appliestoalltechnologyspecificreferencemodelsupto5.@are@aretherereallynonormativereferencesforthisstandard@_erencesforthisstandard@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@Ao`a4@86.3.2@7.3.3.1.1@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]WcWiWjWtWwWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWW W#W$W'W*W+WCWDWKWLWOWQWXWZW[W\WbWeWfWnWoWWWWWWWWWWWWWWWWWWWWWWWmihmnhocandidatequeryresponseprimitiveismoreapproprVmihmnhocommitrequestbVeVfVfVfVmipwWmipshop'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 jxW(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}jReword 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. 2007/09/1909/14/2007 16:50:16 EDTYesE 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. 2007/09/1909/14/2007 16:50:16 EDTYesE Sood, KapilF Disapprove2 2007/09/17[_Ã%@؃كڃ'0|}Ã%P⒃Ѓ{ Ã%`փ׃⾃Ã%pÃ%ՃÃ%⼃҃Ã%ӃԃÃ&HI⭃㙃Ã& σ@A Ã&0Ã&@҃Ƀ̃Ã&PЃуMÃ'JÃ' zÃ'0Ã'@Ã'Pσ?Ã'`>Ã'pÃ(ᦃʃ˃Ã(@%/xÃ(P̃̓΃⎃=Ã(`˃uvÃ(34Ã(78Ã(⍃stÃ)FGÃ) 2Ã)0Ã)Pៃ᠃01Ã)pqrÃ)ŃÃ)Ã* 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&&&NÃBp'cusedWWWWWWWWWWWWWWWWWWWWW WGWcWpWrWsWWWWWWWWW W WW%W&WMWZW\W^WcWWWWWWWWWusefulWWWWWWWAWWuseful--it'sWusefuleWusefullnessfWusefulnessWW W(WWWuserW W7W>WAWBW]WeWfWiWpWtWwWWWWWW%WZW\WWWWWWWWWWWFWGW^WvariableWWvariousWWWvaryWvendorWverbose<WverifiedWversionWveryWWWWWW<W[WviaWcWvirtualWvisibleWwWWw-cdma W WW0W3W7WwaiteWwaitingeWWBNjsimilar@sourceidentifer@specification@tstartparagraphwithasanexamplefigure19shows@=statethatdiscoveryofmihposoverl3isoutofscopeofi@subsequently@successfully@suggest@table10@Ntaken@target@th@the@then@these@thisappearstoberelatedtotheissueofwhichmihusers@to@;type/id@underlying@(use@used@vs@with@ n@vat@changelinkactionstolinkaction@document@it@page%picklowercase@remove802.15fromfigure1andfrompage4line-14@sapFsaps@state@thisneedstobedonethroughoutthedocument@w@w@w@w@within@n@w@within@x@n@w@w@CHcissueW WwWissuedwWissuesWissuingwWwWwWWWWWWWWWWWWWWWWWWWWWWWW W$W*W0W1W7W<W=W?W@WFWRW[W\W]WcWeWfWgWhWnWoWrWsWtWwWitappearsthatcosvaluesfromthelinkparamtypeofgenerFVitappearsthatipaddressinformationstatusisunnecessarynVoVitisincorrecttosaythatthetransmissionstatuscanbevVitisnoteworthyhoweverthattherewillbenodirectcommunVitmaysoundtrivialbutinitializeuponreceiptofthemihVitemsWiteselfWitsWWWWWW WitselfWjWW.Wj1Wj5WjobWjustWWWWW0W1WcWeWrWsWjustprovidingmacaddressesofpoaisinsufficientfornetwVVWcmayWWWWWWWWWWWW WWWW%W,W7W?WIW]WgWpWuWvWWWWWWWWWWWWW#W&WUWpWWWWWWWWWWWWWWW WmaybeW&WWmbbhandoversupportfWmeWWWWmeanWWW0WpWWWWWWmeaningWWWtWWmeaningful5Wmeaningless.W3WmeansWWWWWWWW/WWWWWmeantW3WmeasuredWmeasurementWmeasurementsWmeasuresWWWWoesnotcrossther1andr3Vthenumberofoctets27isnotcorrectusingthenumbersconVthepoachannelrangeisanimportantcharacteristicofthe: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.21/d7.1%Wp99l122WpacketWWBWFW1WpacketsW(WWpageWWWWWFWbWeWqWwWWWWWWW/W6WUWpWuWwWyWWWWWWpagexvthetableofcontentsitemsh9.1andh9.2wraparoVVVposWWWpositiveWpossibleWWWWf1jchooseW5WWcite4WcivicWclaim&WclarificationWclarificationofscopeforthisaspectswouldbeappreciatedVclarifiedWclarifyWWᴃWWW}WWWWJWWWWWWWWWWWWesentedacrossallliVclarifymappingtransportaddresswithmihfidVclarifyorcombineVclarifyorre-writeVclarifyorremoveVclarifythattheoldlinkactionsreferstothedestination}VclarifytheuseVclauseWWWWWWWWWWWWWWWWclear WGWclearly W WWW7WWWclearlydefinetheinfoquerybinarydataieorifitexistsadVclearlystateif802.16providesamechanismsimilartothe VclearsWcleverWcode4W_WWcodesWcodingWcollapsed%WcolumnWWW:WWL!cacknowledgementWWW'WacknowledgementforreceiptofmihmessagecanbereceivedeVacknowledgementsWacronym:Wacronymfor3gppspelledwrong:VacronymsGWHWWacrossW WWactionWWWWWPWQWeWwW8WWW_W`WlWnWsWzWWWWactionsWWWWRWhWtWuWvWwW}WlWzWWWWWWWwWW&WadWWaddWWWWWWWWaddabreviationVaddedW.WFWWMWaddingWaddition7W[WadditionalYWWWWWadditionallyFWJWadditionallythefollowingisapplicabletotheabove4commJVaddressWWWWWWW4W7WOWgWnWoWpWuWWWRWSWwWaddressesWWW WkWlWmWnWoWW8cshallWWWWWW?WWWWWW WshallsWshim6(WshipWshortestWshouldWWWWWWWWWWWWWWWWWWW W!W$W%W*W.W5WOWPWQWTWWWXWZWdWeWkWlWmWrWsWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WW.W/W0W4W6W7W9W>W?WCWDWpWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW!W"WWWshownWWshowsWWW*WwWWNWWWsibWsideW!W}WsidesIWWW%cthettheWtheWtheWtheWtheWtheWtheWtheWtheWtheoWtheWtheWtheWtheWtheWtheWtheWthe@WBWCWOWRWcWfWgWlWoWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWtheWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWhycdifferentWWWWWWWbWWWWWWW6WWWWWWWdifferentiatedWdifferentiatingWdifferentiation(WdifferentlyFWdifficultwWWWWdigitalWdimensionalWdirectWdirection[WWdirectionsWdirectly WdisappearedWdisassociatedWWdisconnectedWdiscoverWWW+WfWWWWWWWWdiscoveryWWWWWWWWWWWdiscussWdiscussedWWdiscussionWWWWdistinctWWWWwWWWWWWWWdoescurrentlinkidentifierrefertotheoriginalortargetVVdoesthescopeofthisstandardincludethefacilitationofVdoesn'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ݒWUcinteroperabilityWWWinterpretationWintervalWWWintervalsaWinterworkingWintoWWWWWWintra-technologyWWW8WWWWWintroduce6WWintroducesWWintroducingWintroductionWWinvokedWinvokesWinvokingWinvolved7WinvolvementWipWOWgWkWlWmWnWoWpW>W?WWWWWWip-basedWipaddressinformation>W?Wipaddressinformationshouldbeoptionalasotheriprelated>Vipconfigurationmetho?Wipconfigurationmethoandipaddressinformationshouldbeopti?ViprenewalWipv6WWirrelevantWWWhich need 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_kZcasWWWWWWWWWWWWWWWWWWWWWWW6W7W=WBWDWEWIWVWXW[W\W]WfWhWkWlWmWwW|W~WWWWWWWWWWWWWWWWWWW&W)W>W?WIWJWRWTWUWVWqWtWzWWWWWWWWWWWWWWWWWWWWWWWWW W WWaVasapWasking^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&WfWWWWWWWgWWWWWWWWprincipleWWpriorW7WWWWWWWWWWWratesWratherWWWrawWrdfWocreliableWreliesWWrelyWremaingWremainingWremoteWW]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}W8WnWsWWWWactionexecutiontimefromnetVactionsWtWvWwW}WWactivation0Wactive`WbWactual&W1WWactuallyWadaptWadaptationWWaddWWWWWWWWWW2WDWEW^W_WeWgWkWlWmWWWWWWWWWWWWWWWWW WWWWW&W.W4W8W=W@WIWJWMWUWWWhWnWrWsWxWyWWWWWWWWWWWWWWW Waddacallflowforfmipoperation&VaddacolumnwhichincludesthereferencetotheclausewherVVVqueryrespongVWafterWW3jfunctionWWW&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$=ELach, Hong-YonF DisapproveGProducer^ Technical_52`1cASub-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.Fd465g5137j 2007/09/1709/16/2007 06:10:15 EDTYesq'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  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."pWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWpWWbWpWpWpWpWpWpWpW23:32:08 EDTYes܀EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_289`7aK of the middle MPDU.d637g3667j Fix this basic misunderstanding. 2007/09/1709/16/2007 23:32:08 EDTYes܀EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_289`7aKd636g3668 2007/09/1709/16/2007 23:32:08 EDTjremovelines47-48andreplacebyareferenceorshortsumma,VremovelisttheflagisalsoselfevidentitcanberemovedVremovem6VVremovemihnethocandidatequerycommand VremovemihnetsapVremovemihnetsapfromthestandard VremovemihnmssapVremovemihnmssapfromthestandard VremoveoptionalfromsupportedisqueryparametertypeinmiDVremoveoptionalfromsupportedtransportlistinmihcapabilCVmovethechangebars!VremovethesentenceVremovethestackmarkedasremoteentityandremovetextlocVVremovethestackmarkedasremoteentityremovetextlocaleVVremovethetextaboutthearqmobileintroduceamechanismw VremovethewholesectionVremovethissectionseepage178lines23-43fordiscussionhVremovedWgWrenameWrenamer1r5asj1j5throughoutthedocumentVreperesent3Wrepetitive<W Disapprove 2007/09/17U )[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) that period. This is only true, however, if counter overflow does not occur during the period of interest.d636g3668j Fix this basic misunderstanding. 2007/09/1709/16/2007 23:32:08 EDTYes܁EKwak, Joseph AF DisapproveGGeneral Interest^ Technical_289`4aKcd635g3669 2007/09/1709/16/2007 23:32:08 EDT2catdmpduWatdmsduWatleastWattachedWattachmentWWWattempt 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-26W8-octetWW8-octetvalueinorderofsignificanceV8.2MW8.2.3.5WW8.5W6W8.6WWWWWWWWWWWWWectingWWngWWWWWWs limited understanding of these terms.,c"Only an MIHF capable network entity shall respond with this message to the received MIH_Capability_Discover request with broadcast MIHF ID or send unsolicited MIH_Capability_Discover response periodically."d573g5029j"Only an MIHF capable network entity shall respond with MIH_Capability_Discover to the received MIH_Capability_Discover request with a broadcast MIHF ID, or send unsolicited MIH_Capability_Discover responses periodically." 2007/09/1909/16/2007 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."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." 2007/09/1909/16/2007 15:56:25 EDTYesd571g5031 2007/09/17=cNMS 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.2 2007/09/1909/16/2007 23:46:35 EDTYesE 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 d639g4963 2007/09/1709/16/2007 23:46:35 EDT] ]cthisthisclausepurportedlyspecifiesaprotocolyettherearenVthiscommentappliestothisclauseaswellastothedocumeVthisisredundantasitcanbeperformedusinglinkactionshVthisisthemaximumdatatransferratenotthemaximuminforVthisiswithregardtothefunctionalarchitecturefig4thaVacommonlyusedcommunicationstermanditisVthrougputWtimeWWWWWtimeoutsWtimerWtlvWWtoWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtooWtoolsWtransferWtranslateWWtransmissionWWtransmitWWWtransmittedW I mcASince 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)dependent event are not included in the standard. For instance the "Link Going Down" seeia independent event are not included in the standard. For instance the "Link Going Down" seed628g3676 2007/09/1709/16/2007 23:32:08 EDT[d435g5167j/see page 66 lines 35-36 and page 71 lines 32-33 2007/09/1909/16/2007 03:08:31 EDTNo\ERajkumar, AjayF GProducer^ Technical_94`60ccThere is no way for this event to indicate that it was generated as a result of the periodic timer.d434g5168jsee Page 71, line 32-32 2007/09/1909/16/2007 03:08:31 EDTNo]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?08:31 EDT 2007/09/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 remove 2007/09/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?d602g5000jClarify 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_41`3a6.3.5cd601g5001 2007/09/1709/16/2007 21:41:08 EDTNK_ACTIONd625g3679j correct it 2007/09/1709/16/2007 21:41:08 EDTYes܌ESreemanthula, SrinviasF Disapprove0 2007/09/1709/16/2007 21:41:08 EDTjadditthereVaddmissinglisttothenameyVaddmissingmessagetolistWVaddmissingopeningbracketunsignedint2VaddmobilitymanagementieVaddnewstatediagramsorremovethiscapabilityandanyassMVaddperiodVaddr2UVaddtextinthisscenariothesourcemihnodemaysilentlydVaddtextseesection6.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 EDTclabelWlabelled1WlackW(W+W,Wlack-of-itWlackingrWlanguageWlansWlargeWlastWW/WWWWlater6WWlatitudeWWlatterWWWWWlaughableWlayarWlayerWWWWWWWWW7W;W?WWWWWWWWWWWWWWlayer2macandllcVlayer-dependentWlayer-specificWlayeringWWsupportedmihcommandlTWsupportedmiheventlisTWsupportedtransportliTWsupportingcWsupportscWsyntaxWsystemWtableWW>Wtarget<WZWtechnical߁WtechnologiescWdW߁WtechnologycW߁Wterm]WterminateJWterms WWtextWLWMWeWmWnW߂WthCWthan(W)WJWthatWW(W)WQW[W\WaWcWjW߁WWmgERajkumar, AjayF GProducer^ Technical_109a7.4.19cAawhy this request contains more information 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).ad423g5179jAdd IP configuration method to Net_HO_Candidate_Query.response (page 106 section 7.4.19.3) as an optional parameter, along with any corresponding optional server address. Alternatively, this information could be removed from Mn_HO_Candidate_Query. 2007/09/1909/16/2007 03:08:31 EDTNohERajkumar, AjayF GProducer^ Technical_103a7.4.18cW@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 EDTZbGProducer^ 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." 2007/09/19YesܕESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_87`31a7.4.4.cd615g3689 2007/09/1709/16/2007 21:41:08 EDT(qcThese parameters are not available for network initiated handovers (see page 107, Section 7.4.19, Net_HO_Candidate_Query.request) but, they could be.d413g5189 2007/09/1909/16/2007 03:08:31 EDTNorERajkumar, AjayF GProducer^ Technical_115`28cStates 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.d412g5190jDelete "prepares resources, " 2007/09/1909/16/2007 03:08:31 EDTNosERajkumar, 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.d411g5191 2007/09/1709/16/2007 03:08:31 EDTNo04/2007 16:19: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 EDT6c[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". 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_128`65c"The "may" makes it sound optional.d393g5209jChange "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/1909/16/2007 03:08:31 EDTNoERajkumar, 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). 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_128d391g5211 2007/09/1709/16/2007 03:08:31 EDT pF 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_ELEMENT 2007/09/1909/13/2007 13:56:26 EDTYesqE 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 27 2007/09/1909/13/2007 13:56:26 EDTYesrE Cypher, DavidF DisapproveGGeneral Interest^ Technical_186`32c Consistency in naming is lackingd156g5446j*Add underscore between PACKET and TRANSFER 2007/09/1909/13/2007 13:56:26 EDTYessE Cypher, DavidF DisapproveGGeneral Interest^ Technical_179`43c'There is no bit for Link_Action commandd155g5447jAdd bit for link action command 2007/09/1909/13/2007 13:56:26 EDTYescup W$W0WvWWWW WW+W,WZW\W`WWWWWWup-to-dateWup/down[WupcomingWupdateWWOWQWiWjWkWupdates(WuponWWWupperWeWWWWWupper-layerBWuptoWusageWWWWWW&W@WWWuseWWWWWWWWWWWWWWW'W+W=WWWWWW WWGWHWlWWWWWWWWWWusecorrectpluralofmniemnsVusecaseWestWhoܐ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#xsjDelete "prepares resources, " 2007/09/1909/16/2007 03:08:31 EDTNotERajkumar, AjayF GProducer^ Technical_119`22cAMStates that an MIH User must generate a response to the indication while the following paragraph states that MIHF is to carry out the specified actions when a Net_HO_Commit request is received. However, if the MIHF carries out the link actions then how does the MIH User get the status so that it can create the appropriate response.Md410g5192jAThat 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.?H jBd 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.t~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~W~Wlmost~W~W~W~W~W~W~Wst~W~W~Wst~W~W~W~W~Walone=W=W=W=W=W=W=Walone=W=W=Wlone=W=W=W=Wlone=W=W=WalongalongalongalongalongalongalongalongalongalongalongalongalongalongalongalongWalongalongWalongalongalongalong=WalongalongalongalongvWvWvWalongvWvWvWvWalongvWvWvWvWvWvWvWalongvWvWvWgvWvWalongvWvWalongvWvWVVVstandardVVrdVVVVVVstandardVVdVVWWconstructed WcontactW /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/17VWVmGGeneral Interest^ Editorial_186`42aB.2.5cQThis is the maximum data transfer rate, not the maximum information transfer rated528g5074jReplace "information" by "data" 2007/09/1909/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. 2007/09/1909/16/2007 13:58:33 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Editorial_111`16a 7.4.20.3.2c6Font of parameters in list needs to be made consistentd526g5076 2007/09/1709/16/2007 13:58:33 EDTYes41:08 EDTdrichardWWWWWWWWWrudolf 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;Vnd52g5550jDelete 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. 2007/09/1909/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_49`17a6.5.3c&Emphasize that this is only an exampled51g5551j;Start paragraph with: "As an example, Figure 19 shows ...." 2007/09/1909/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_48`13a6.5.3cd50g5552 2007/09/1709/10/2007 07:08:58 EDT, 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 ?wd513g4440 2007/09/1709/16/2007 12:18:13 EDTNona2Vsupportedtransportlistshouldnotbeoptional1VsupportedisquerytypeWsupportedmihcommandlWPEChaplin, 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.d555g5047j"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." 2007/09/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. Request/Response do not have to go in the directions they are shown; that the reverse directions are also allowed.709/16/2007 21:41:08 EDTYesjeitherchangecurrentlinkidentifiertosourcelinkidentifDVEVeitherchangen2nhocommittousesourceandtargetlinkidJVeithercorrectthislisttoindicatethatthesestatisticsaVeitherinserttheethertypeforl2mihifoneexistsalready-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<WxWyWWWWonlyanmihfcapablenetworkentityshallrespondwithmihcVonlymihnetworkentitiesshallrespondtobroadcastedmihcVopeningWoperate'WoperatingW1Woperation&W'WWoperationsWoperatorWoperator-4WoptimizedWoptimizingWoptionWWW&WW WWWoptionalWWW&W]WgWWWWW>W?WCWDWJWoptionallyWoptions&W+W709/16/2007 21:41:08 EDTYesܧd597g3707 2007/09/17v09/16/2007 15:56:25 EDTYesEChaplin, 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." 2007/09/1909/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_147a8.2.2.3cA)Figure 24: 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.)d569g5033j6Update the state diagram to match the text description 2007/09/1909/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Technical_145d568g5034 2007/09/1709/16/2007 15:56:25 EDT[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 EDT@djeEsjKcA{@`zad)dcPG}cAd>jj@E&dgcc^?c^pdjcEc5j<j4jA?cAld@FSEYjAcA\dPjAcGjgcApd}jGWcAdG@j@k c @cdcAdcBdGccBdcAdrjEM"E$cA.&@'a)E,GQE/cAdN2cR4c6dt9j=EO@dCjEvGFa4:㎃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&WjWtWWWWWWWWWWprimitivesWWW&W@WcWfWtWWWWWWCWDWIWZW\WWWWprimitvesWWprinciple'WpriorWprioritiesWprioritizedWWpriorityWWproblem]WwWWproblems]WwWprocedureWproceduresWWWprocessWWprocessesWprocessing?WwWproduce'WproducedBWproformaWWproject:WproperWproperlyZW\WWpropertiesWproperty WproposeWproposedWprorityWWprotocolWWWW WWW%W&W+W7WBWWWWWWWWWWWWWWWWWWWWWWWWWWprovideWWWWWWWWWWVmarian 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.19g7.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.23W7.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'sWheaderWWHWWWWWWheadingmWhelpWhelpfulWWhelpsWhenceWhereWWWWWWJWWWWwWWheretargetpoaisspecifiedasmacaddressaswellasinmnVhessidWheterogeneousWWWWhexNWhigherWWWWWWhighestWhighlyWhoWWWWWWWJWKWLWMWNWeWgWiWqWrWsWtWuWwW~WWWWWWW W W WIWKWTWUWVWYW[WWWWWWWWWhocWWhoghooghiWhome WWhopefullyWEmmelmann, MarcF DisapproveGAcademic^ Editorial_17`32a5.3.4c&incoherent usage of singular or plurald36g4917 2007/09/1709/10/2007 07:08:58 EDTNoq cAThe 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. EDTNoECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_208`48aDc.(Kenichi) cardinality should be minCardinalityd442g4511jreplace 1 with 1 2007/09/1709/16/2007 03:35:02 EDTNoEDTNoECheng, Yuu HengF DisapproveGGeneral Interest^ Editorial_208`48aDc.(Kenichi) cardinality should be minCardinalityd442g4511jreplace 1 with 1 2007/09/1709/16/2007 03:35:02 EDTNo442g4511jreplace 1 with 1 2007/09/1709/16/2007 03:35:02 EDTNo bIcAMConsistency: 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?Mk nodes, etc.d267g4686jZRaname "Home Network" to "Home Subscriber Network" in this clause and throughout the draft 2007/09/1709/14/2007 16:50:16 EDTYes{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.d266g4687jClarify or re-write. 2007/09/1709/14/2007 16:50:16 EDTYes|E Sood, KapilF Disapprovete sentence.d266g4687jClarify or re-write. 2007/09/1709/14/2007 16:50:16 EDTYes|E Sood, KapilF Disapprove8 2007/09/1709/14/2007 16:50:16 EDTVhacThroughout 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 spec 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_32`33a5.7.2c*There is a period in front of the sentenced370g5232jRemove period (.) 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, 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) 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_13`10a5.1.4d368g5234 2007/09/1709/16/2007 02:47:09 EDT/09/17*GProducer^ Technical_67`17a7.3.4cAThe 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.W޾W޾W޾W޾W޾W޾W޾W޾WWޮW޾W޾W޾W޾W޾WW޾W޾W޾WW޾W޾W޾WW޾W޾WW޾W޾WޮW޾W޾W W W WWW%W-W2W3WIW\W]W^WbWeWoWpW{W|W݇WݔWݘWݝWݯWݰWݱWݴWݽWWWWWWWWWW W7W@WBWDWIWnWoWyWjrequestWWW 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 EDT"]EMeylemans, 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.' 2007/09/19K_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.Rd40g4913jUse 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. 2007/09/1709/10/2007 07:08:58 EDTYes^EEmmelmann, MarcF DisapproveGAcademic^ Technical_27`37a5.5.4melmann, MarcF DisapproveGAcademic^ Technical_27`37a5.5.4d39g4914 2007/09/1709/10/2007 07:08:58 EDT4 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."jVVVVVVVVVVVVVVVVVVVVVVVVVVVVhemissingdefinitionmustbefilledݙVthemobilenodeiscapableofsupportingmultiplelink-layerVtheneedanduseofthemihnethocandidatequerycommandaVthenumberofqoslevelsofserviceisnotdefinedfor2.11܂Vtheoverallnetworkmayincludepicocellssuchasieee802.Vthepagenumbersofthepdfdon'tlineupwiththepagenumbVtheparagraphmentionsthatmihprovidesamechanismformihVz\ctypenameipconfigstatuscarriesvalueswhicharetemporarVtypesWWWWW4WFWGWW=WWWWe 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 EDTYesnENatarajan, Kadathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g4418arked as "Remote Entity". Remove text "Local Entity" from the stack on the left-hand side. 2007/09/1709/16/2007 15:23:06 EDTYesnENatarajan, Kadathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g4418adathur SF DisapproveGProducer^General_36`20a6.3.1c7Figure 13 is confusing by showing two unrelated stacks.d535g4418 2007/09/1709/16/2007 15:23:06 EDTYesWW!W7WYWallocatedWWWanyWappearanceܻWocamendWamendmentWamendmentsWWWWammendmentsWamongIWWWWanWWWWWWWWWWWWW W WW&W'W+W.W0W1W>WAW]W^W_WjWpWtWvWwW~WWWWWWWWWWWWWWWWWWWWWWWWWW WWW#W$WIW|WWWWWWWWWWWWWWWWWWWWWWWWWWenormous+WenoughݡWݤWenterWWentire܅WݚWWކWentitiesܗWܘWܫWWWW0WWentityܧWܪWܾWܿWWWWWW.WޥW޲WentriesYWZW[WentryܔWޛWenumerated'Wequal~WWequationWequipment WJIfGProducer^ Technical_5`8a2c;Are there really no normative references for this standard?t 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?d578g3726j 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?d578g3726j 2007/09/1709/16/2007 15:56:25 EDTYesHPd364g5238jhNormative references should be considered such as the base standards of the media specific technologies. 2007/09/19e 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.b56:25 EDTYesܽ6:25 EDTYesܼ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?d576g3728jy"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." 2007/09/1709/16/2007 15:56:25 EDTYesܽ 2007/09/1709/16/2007 15:56:25 EDTYesܽd575g3729 2007/09/1709/16/2007 15:56:25 EDTaHF DisapprovereeitemsorpreferablymovethemtoaninformaXVdeletetheuirbitoraddmoretextthatanswerstothosequV==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."jcinFWGWHWIWJWMWRWYWZW\WlWrWtWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWnder 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 EDT09/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. 2007/09/1909/16/2007 15:32:58 EDTYesEColban, Erik AF DisapproveGUser^ Technical_31`45a5.6.2.6cWhat is "existing" and what is "new" is relative to the development stage of this standard and the referenced 3GPP/3GPP2 standards.d543g5059j 2007/09/1709/16/2007 15:32:58 EDTNoRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWRWtarts߇WstateLWMW߁W߃WߊWߏW߮WWGWPWRWTWXWYWdWW)WKWLWMWubscription߇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~WWWWWWWWWWWWWWWWWWWfamolaridavidVVVVVVfederCWDWEWFWGWHWIWJWKWLWMWNWfederperetzCVDVEVFVGVHVIVJVKVLVMVNVI09/16/2007 01:46:33 EDTYesEMccann, StephenF DisapproveGProducer^ Technical_2`33cAlthough 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 cells. wAccepted-Modified 2007/09/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.vby 363w Superceded 2007/09/1909/16/2007 01:46:33 EDTYesz crdfW.W4W6Wre-associatesWre-defineWWre-definingWre-drawnWre-transmit'Wre-transmittedWWWWWWWWoptionalWWWWWWWWWWWWWoptionallyiWiWiWiWiWlyiWiWiWiWiWiWiWWWWWWWWWoptionallyiWiWiWiWWWWWWWWoptionallyiWiWiWiWiWiWiWallyiWiWiWiWiWoptionsߢ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{WucwhenthemihtransportisreliabletheacknowledgementmechaVwhenthemimetypeisapplicationsparql-resultsxmlthisfi<VwhenthetimerexpireswithoutreceivingaresponsemessageVwhen/ifWwheneverbWWWWWWwheneverapplicabletheieee802.21standardshalluseexistVwhereWWWWWW W7WKWLWMWNWWWWWZW\WgWWWwherearethenormativereferencesVwhereasWWwhereinWwhetherWWzWWWWWWWWW W W WWWWWWWWWWWWWW 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/17%d96g5506j-Remove this primitive or clarify its purpose. 2007/09/1909/11/2007 17:46:47 EDTYesEMyles, 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 wod95g5507 2007/09/1709/11/2007 17:46:47 EDTkWoWpW݁W݂W݉W݋WݖWݦWݱWݾWWWWWWWWWWWWWW$W<W@WAWGWHWJWZW_WdWfWhWsWwWހWފWޒWޛWޜWޞ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 LcA 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). %%7.3.14.1.2.21.2.27.3.2.2.2lllllllllll.2llllll.2lllll.2.2ll.2.2llllllllllllllll2.2ll2.2ll$V$V$V$V$V$V$V$V$V$V$V$V$VVclintܸWܹWܺWܻWܼWܽWܾWܿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcolbanWWWcolbanerikaVVVdavidWWWWWWerikWWWqjfigureWWWWW*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$WaIctransaction 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". 2007/09/1909/16/2007 03:38:14 EDTYesJE 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 identifiersd452g5150j 2007/09/1709/16/2007 03:38:14 EDTYesthedifferentcosidberepresentedconsistentlyacrossVwimaxWWwiredWWwirelessWWWWWWe-defined܈WyieldWyouWWzero܁WlE 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.6 2007/09/1909/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^General_282c,Annex J does not add much value to the spec.d356g5246jIremove Annex J "Requirements to support 802.21 by L3 and above transport" 2007/09/1909/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^ Technical_203`1c&The missing definition must be filled.d355g5247jDefine the missing definition 2007/09/1909/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^ Editorial07/09/1809/15/2007 22:08:13 EDTYesE Xie, QiaobingF DisapproveGUser^ Editoriald354g5248 2007/09/1709/15/2007 22:08:13 EDTjinbothline38and37changedefaultvalueformime-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 EDT+Z+jRemove Packet Identifier 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, 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#1 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, 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. 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_67`41a7.3.4.2cd607g4995 2007/09/1709/16/2007 21:41:08 EDTVwimax|WWWWwiredcWWWwirelesscW߁WߦWpWWWWerenceݺWcrossedIWWDr09/16/2007 02:47:09 EDTNoEMeylemans, 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 Falsed379g5223j\Make 'Requested Resource Set' parameter optional in both the response and confirm primitives 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Technical_107`25a 7.4.19.3.2cThe 'Requested Resource Set' parameter should be Optional because the 'Query Resource Report Flag' in the request or indication can be True or Falsed378g5224j\Make 'Requested Resource Set' parameter optional in both the response and confirm primitives 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_105`17a 7.4.19.1.1d377g5225 2007/09/1709/16/2007 02:47:09 EDT09/16/2007 15:56:25 EDTYesd562g3742 2007/09/17cindicatesWWWWWWWindicating_WgWWindicationW W W WeWtW~WWWWWWWIWZW[W\W_W`WaWWWWWWindication/responseWindicationsWW W]WindicatorWindividualWGWindividuallyWinefficiencyWinexact@WinfoWWWWWWinformaitonOWinformationWWWWWWWWWWWWW%W=W>WAWgWnWoWWWWWWWWWWWWWWWWWWWWWWWWW)W4W6WIWpWWWWWWWWWWWWinformationelementsbeforethemnisauthenticatedwiththeVinformationonhowtoextendtherdfrepresentationshouldb4VinformationalWWW6 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.;W;WW;W;W;W;W;W;W;WtransmittedWtransparent W W W Went W W W W W W W W Wrent W W W W W WL_@ăσ`ᾃ8⠃⢃p;⟃⡃ÁἃὃAB‚!:‚"‚#‚$7➃Â%?@‚&ể߃‚'‚(ƒރ‚)‚*ẃ‚1‚2‚3‚4Ꮓᐃ‚6܃‚7ۃ‚8‚:>‚A‚B6㥃‚Cᎃṃ'()✃كڃ̃‚Dῃ$+ⷃ㣃‚݃ރ߃‚f‚ᧃ‚‚‚\‚‚eÃ![Ã!0QÃ!@PRhÃ!`Ã!Ã!Ã!giÃ"jÃ" OmoÃ"0lÃ"@knpÃ"PqsÃ"`rÃ"ឃᢃ Ã"tÃ#uvÃ# ᝃᤃwxy{|}Ã#0ᣃz~Ã#@⁃Ã#P᥃Ã#`Ã#CÃ#E℃⅃Ↄ?Jc3&and parameter extraction commands - missing hyphend368g5234j$add hyphen to 'parameter-extraction' 2007/09/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' 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ Editorial_5`1a2c#No normative references are listed.d366g5236jJList all normative references or if there are none, then indicate as such. 2007/09/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. 2007/09/1909/16/2007 01:46:33 EDTYesEMccann, Stephen9/170`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 primitive 2007/09/1909/13/2007 13:56:26 EDTYesE 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. 2007/09/1909/13/2007 13:56:26 EDTYesE 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.V2jAdd 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& 2007/09/1909/16/2007 07:13:12 EDTYes3ERudolf, MarianF DisapproveGProducer^ 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). 2007/09/1909/16/2007 07:13:12 EDTNo4ERudolf, MarianF DisapproveGProducer^ Technical_177`27c[In table B.3 Data types for address, 3GPP identifiers are unclear and need to be corrected.d474g5128jDefine 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.static4Wstating߶W,peretzCWDWEWFWGWHWIWJWKWLWMWNWpieter-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~VVVVVVVVVVVVVVVVVVVrichWWWWWWWWWޡWdsj`Change to "Functional entities shall discard any received IE with an unrecognizable identifier." 2007/09/1909/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Technical_105cAThe 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 command 2007/09/1909/15/2007 22:08:13 EDTYesE 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. 2007/09/1909/15/2007 22:08:13 EDTYesⴀ 2007/09/17 }cgenerationWgenericWWWWgenrealWWWgenricWWWWgeoW. 2007/09/17steningWlistsYWZW[W[WWWWWWWlocallyWWWlocatedWlong WlongitudeܸWlongitudeshouldbenormalizedtowithin180degreespositivܸVlookW W WlostWlower~WW)Wlsb+WmacܲWܳWWWWW)WmachinesWmain#Wmake܇WܩWܮWܰWWW#W+WTWmaketheannexnormative܇VmakesWmakingWKWmakingtheseparametersoptionaldoesn'tsolveanyproblemiKVmanagement}WWWWWW*Wmandatory#Wmap#WmappedWmappingWWmappingsWmarkedWWmasked+WmatchyWWWmaterialܮWܰWmax܆Wmaximum܄Wmaximumdataratein802.11termsisthehighestavailableb܄V!zcqueryWWWW WWYWZW]WgWiWpWqWrWsWWWWWWWWWWWWW W WDWIWKWVWYWWWWWWqueryingW*WquestionWWquiteWquotationWquoteW/Wquotefrom2007stylemenupage17lastparagraphannexessh/Vdard 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.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.?6jochange text to 'The primitive to set parameter thresholds that could trigger this event is specified in 7.3.3.' 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, 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' 2007/09/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 2007/09/1909/16/2007 02:47:09 EDTNoEMeylemans, MarcFApproveGProducer^ EditorialaN/Ad371g5231 2007/09/1709/16/2007 02:47:09 EDT6~ 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, 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". 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, 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 indications 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_123`52d397g5205 2007/09/1709/16/2007 03:08:31 EDTW_WarqWarreWMnjbeconsistentrecommendtousemediaindependentnohyphenVbeconsistentwithwhattimeintervalmeansVbearerWbecause9WWbecomes%W 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?Yes>EWilliams, 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)WassignmentWassistedWassisting<WassociatedWW WwWWWWassociatesWassociationWassociations7WassumeWWWWWWWassumedWWassumesWassumingWassumptionW'W7WWW@W6:25 EDTYesYEChaplin, Clint FF 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݊W3Z cA!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 CommentwDeferred 2007/09/1909/16/2007 01:46:33 EDTYes 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. td49g4904jdelete the sentences 2007/09/1709/10/2007 07:08:58 EDTYesUEEmmelmann, Marc this. td49g4904jdelete the sentences 2007/09/1709/10/2007 07:08:58 EDTYesUEEmmelmann, MarcGAcademicd48g4905 2007/09/1709/10/2007 07:08:58 EDT'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 ?d487g5115jed set of choices available ?d487g5115j 2007/09/1709/16/2007 07:13:12 EDTYesline 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 8cthereisnowayforthiseventtoindicatethatitwasgener\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*WWW~^ Technical_26`37a5.5.3cWIf MLME-SAP messages are permitted in State 1. They would also be permitted in state 3.WWsuggestrewritingthissection.Vsuggesttomove8.2.2toanannex%VVsuitableWsummarize߮WsummaryߣWxWsupersetߝWsupplied߮WsupporthWߝW߯W!W4WTW Wsupported WUWVWWWXWߑWߝWWTWWWWWsupportedisquerytypeTWsupportedmihcommandlTWsupportedmiheventlisTWsupportedtransportliTWsupportingcWsupportscWsupposed߉W߮W߾WswitchWswitchlocationofremotemihfandremotelowerlayersinfiVsymmetricalWsyntaxWsystemWWtߞWtableWW>WߴWWHW`WnWoWWWWW WtablesCWHWWtagW;WtakeߔWWWtakealookwhatother802standardsdoesanddefinethenorߔVtalking߭W=09/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_53`25a6.5.5.2cZThe contents of PoA System Information IE are not defined within the 802.21 specification.d90g5512j$Remove the IE or add the definition. 2007/09/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]WxWyWWWWWWWpWspecifyinformationelementpVspecifytheminimuminformationthatneedstobeincludedfoVspell7WGWHWspelloutmnandpoainthedefinition3.7HVspelloutpoaGVsquareNWstackWWWWWW!W"WWWWWstadnardEWstandardWW)WWWWWWW W WW=WW WstandardsWWWWWWstanndard?WstartWWtartsWstateWW W WWW7WvWWWWWWWWMWWWWWubscriptionWsubsequentbWs ycmihmihconfigurelinkcommandisnotdefinedthereamihlinkcVmihdeploymentmodelwhichspecifiesthelocationofmihfpoVmiheventsubscribeandunsubscribearelistedpartofserviVmiheventsubscriptionasdefinedhaslimitedcapabilityforVmiheventsubscriptionshouldallowthesubscribertosetceVVVmiheventscommandsandinformationservicemessageexchangeVmihgetinformationresponsechangethetableentryfrominfVmihhandoverprimitivesprovidelimitedhandoverfunctionaliVmihhandoverprotocolbehaviorismissingfromthesection8Visafixedlength8bytesHVmihisabouthandoverbetweendifferentaccesstechnologiesVmihisnottheonlywaythroughwhichthehigherlayersandVmihn2nhocommitcurrentlydoesnotallowtheoptionofreqVmihn2nhocommitdoesnotallowtheoptionofrequestingreVmihn2nhocommitshouldalsoallowtheoptionofrequesting V3L,a8.2.2.1cA)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 description 2007/09/1909/16/2007 15:56:25 EDTYesEChaplin, 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;" 2007/09/1909/16/2007 15:56:25 EDTYesEChaplin, Clint FF DisapproveGGeneral Interest^ Editorial_143`8a8.1d566g5036 2007/09/1709/16/2007 15:56:25 EDTainer(W)W*W=Wcontaining߾Wcontains߄WߜWߺWWWWWWWWWcontecttWWFcAnnex 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.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. 2007/09/1909/06/2007 13:47:55 EDTYesE Golmie, NadaF DisapproveGGovernment/Military^ Editorial_50caIn the list of PoA on the bottom right, the first element should state Operator_2, not Operator_1d25g5577 2007/09/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 2007/09/1909/04/2007 16:19:39 EDTNoE Golmie, NadaF DisapproveGGovernment/Military^ Editoriald23g5579 2007/09/1709/04/2007 16:19:39 EDT(t 2007/09/1909/16/2007 03:08:31 EDTNouERajkumar, AjayF GProducer^ Technical_120`9cAoSince 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.od409g5193 2007/09/1909/16/2007 03:08:31 EDTNovERajkumar, 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?e09/16/2007 15:23:06 EDTNocdiverseWdividedWdividingWdoWWWWW?WeWnWoWWWWWEWWWWWWWWWWWWdocuementsWdocumentW&WWWWWWWOWQWiWjWkWzWWWWdocument'sWdocumentsEWdoesWWWWWWWWWWWW WWWWWW0W1W7W?WDWEW[WnWoWpWtWwWWWWWWWWWWWWWWWWWWWWWW*W2WIWRWTWVW[WWWWWWWWWWWWWWWWWWWWWWWWWWWofVdoesn'tWWWWWWW W W,W0W7WeWrWsWwWdomain W `44IWIWIWIWIWIWIWIWIWtitled>W>W>W>W>Wled>W>WoWWWWWWW W W WWWWWW"W#W%W&W'W(W)W*W,W.W/W6W8W:WAWBWGWHWKWNWOWPWRWTWYWZW[W]W_WcWfWgWhWkWoWpWtWvWwWyWzW{W߀W߁W߂W߅W߈WߊWߋWߐWߑWߒWߕWߖWߙWߚWߛWߜWߞWߡWߢWߣWߤWߥWߧWߨWߩW߫W߬W߭W߮W߳WߴWߵW߶W߷W߸W߹W߻W߼W߽WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWWWW!W%W'W)W.W/W0W2WK cA8MIH_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_SAPv105w Superceded 2007/09/1909/15/2007 22:08:13 EDTYesd allow the subscriber to set certain conditions or qualifiers. With that only events meeting those conditions or qualifiers will be notified to the subscriber.d538g3766Kadathur 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.d538g3766 2007/09/1709/16/2007 15:23:06 EDTYes3j802.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,W8WamendmentsWamongIWWeGGeneral Interest^ Editorial_256`19c!There is no MIN_MN_Commit.requestd169g5433jMIH_MN_HO_Commit.request 2007/09/1909/13/2007 13:56:26 EDTYesfE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_252`19c!There is no MIN_MN_Commit.requestd168g5434jMIH_MN_HO_Commit.request 2007/09/1909/13/2007 13:56:26 EDTYesgE 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. 2007/09/1909/13/2007 13:56:26 EDTYeshE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_228`47c,Consistency with paragraph/bullet conventiond166g5436j!Add blank link between 9) and 10) 2007/09/1909/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 EDTYesjfP^ Technical_103`13a 7.4.17.2.2c9(Kenichi) LINK_ACTION_RSP should be LIST(LINK_ACTION_RSP)xVxVxVe1givesexamplesofupperlayersipetcandlowerlayxVxVxVxVxVxVxVxVxVxVxVxVxVyxVxVxVxVxVxVlayxVxVxVxVxVxVxVxVxVxVxVxVxVxVlayxVxVayxVxVxVxVxVxVxVxVxVxVxVe1givesexamplesofupperlayersipetcandlowerlayxVxVxVxVxVxVxVyxVxVxVxVxVxVxVfigure12shouldbemovedtosection6.2.1becauseitshowsߡVߡVߡVwsߡVߡVߡVߡVߡVߡVߡVߡVfigure12youmightwanttoindicatethatthemiheventsubs[V[V[V[V[V[V[V[V[V[V[Vumightwanttoindicatethatthemiheventsubs[V[V[V[V[V[V<W<W<W<W<W<W<W<W<W<WSjremovereferencetovariableoctetsfromthefigureHVremoveremoteentitystackandremovetextlocalentityfromVVremovesection7.4.18andalsorelatedsectiondatatypemihRVremovetableb-10VremovetagandthecontentsSVremovethechangebars!VremovetheieoraddthedefinitionVremovethesentenceVremovethestackmarkedasremoteentityandremovetextlocVVVVremovethestackmarkedasremoteentityandremovethetext!V"VremovethestackmarkedasremoteentityremovetextlocaleVVremovethetextaboutthearqmobileintroduceamechanismw VremovethewholesectionVremovethisprimitiveorclarifyitspurposeVremovethissectionseepage178lines23-43fordiscussionhVremovedWgWremovingWrenameWrenamer1r5asj1j5throughoutthedocumentVreorderWWesent3Wrepetitive<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߶WIWstation8WstationaryW{zyE Chin, Kevin AFApproveGGeneral Interest^General_48cMisc comments in .USR file.d340g5262 2007/09/1909/15/2007 18:28:36 EDTNoE Kim, YonghoF DisapproveGProducer^ Technical_193`2aB.2.8ctData 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_IE 2007/09/1909/15/2007 00:24:13 EDTYesE 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. 2007/09/1909/15/2007 00:21:32 EDTYesE Kim, YonghoF DisapproveGProducer^ Technical_46y and adopt it. 2007/09/1809/15/2007 00:21:32 EDTYesE Kim, YonghoF DisapproveGProducer^ Technical_46M 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}WWWWWWWQ_Ã7 bcÃ7@aÃ7p`Ã7^_Ã7]Ã8\Ã80[Ã8@ZÃ8pYÃ9VWXÃ9 TUÃ90.⪃RS㖃Ã9PᕃᗃᘃᙃQÃ9p5Ã9ᔃÃ9Ã9ᒃÃ:Ã:0ሃ,-Ã:@Ã:pPÃ:YZOÃAPÃB`NÃBp⩃eGProducer^General_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.3WWmEVan Leeuwen, Richard MF DisapproveGProducer^ Technical_203`9aB.2.17c+Definition for NETWORK_SECURITY is missing.d532g5070j(Add the definition for NETWORK_SECURITY. 2007/09/1909/16/2007 14:02:28 EDTYesEVan 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. 2007/09/1909/16/2007 14:02:28 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_33a6h. 2007/09/1809/16/2007 14:02:28 EDTYesE Gupta, VivekF DisapproveGGeneral Interest^ Technical_33a6d530g5072 2007/09/1709/16/2007 13:58:33 EDTsK09/15/2007 22:08:13 EDTNoE Xie, QiaobingF DisapproveGUser^ Editorial_36`48a6.3.1crepeated statementd345g5257jZdelete "MIH events may be local or remote. Remote MIH events originate at a remote MIHF. " 2007/09/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. 2007/09/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.d343g5259 2007/09/1709/15/2007 22:08:13 EDTNo&|julkavibhorVVVVVVVVVVVVVVVVVVVVjunghoonWWWWW%WWWWWWWWkapilWWWWWWWWWWWWWkarockiWWkarockipiotrVVkevinWkimWWWWWWWWWWWWWkimeunahVVVVkimyonghoVVVVVVVVVkwakWWWWWWWWWWkwakjosephaVVVVVVVVVVlach<W=W>W?W@WAWBWlachhong-yon<V=V>V?V@VAVBVleeuwenWWlevyWWWWlevyjosephsVVVVmWWmarcWWWWWWWWWWWWWWWWacmisleadingW@Wmisleading--theWmissesWmissingWW&W+W-WYWfWWWWWWWWW1WgWmWyWWWWWWWWWmissingaparenthesisforthetypeofpacketidentifier1Vmissingbracketinunsignedint2VmissingcommaVmissingcommaafterlastwordinlineVmissingdefinitionmustbefilledVmisusedWmixesWmlmeWWWWWWmlmesapc-sapmih3glinksaplsapcssaparenotshowninfVmlme-sapWmnWWWWWWW&W0WJWKWLWMWNWdWeWiWuWvWwW}W~WWWWWWWWWWWWW@WUWYW[WbWeWfWWWWWmn'sWmnsWWWWWWWWWW&W'W5W7WkWlWmWtWvWW17jProvide the capability for the MIH-capable mobile node to broadcast information to devices at a PoA in addition to the request/response mechanism. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_170`14a8.6.4.1c}If at least one query is required, there should be some minimum required information that needs to be included in that query.d323g5279juSpecify the minimum information that needs to be included for the query. For example, PoA information, location, etc. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, 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. 2007/09/1909/14/2007 23:15:41 EDTYesncitWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W$W*W0W1W7W<W=W?W@WFWRW[W\W]WcWeWfWgWhWnWoWrWsWtWwW|W~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW#W$W&W(W0WBWIWJWYWmWpWqWwWzWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WWW0W1WcWeWrWsWwWjustprovidingmacaddressesofpoaisinsufficientfornetwVVWd137g5465jClarify 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?) 2007/09/1909/13/2007 13:56:26 EDTYesE Cypher, DavidF DisapproveGGeneral Interest^ Editorial_71`14a7391cSentence is missing punctuationd136g5466j Add period 2007/09/1909/13/2007 13:56:26 EDTYesE 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" 2007/09/1909/13/2007 13:56:26 EDTYesE 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 medium 2007/09/1909/13/2007 13:56:26 EDTYesd133g5469 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>WAWreportWQWaWreportedWreportingWreportsWWWWrepresentationWrepresentedWWreqWceWWWWWWWXZjchangedescriptiontoabitmapnwherenmustbeamultipleVchangeeithertochangingalinkimpliesortochanginglinkVchangeentitymihbasicurltobeassignedVchangefig9and10Vchangefigure26toshowmihprotocolheaderhasfixedlengtVchangefortransportservicesoverl2theprimitivesarespecVchangefrommacadresstolinkidVchangeguildtoguide{Vchangeintoieee802.16alsoallowsanmntoqueryusingpkmVchangeitPVQVchangeittostatus9Vchangelinkidtolinktupleid7VchangelinksacntolinkscanVchangemaytoshalliealwaysgeneratesanindicationwhenVVchangemihinformationrequest/responsewithmihgetinformaOVchangemihnethocommitrequesttomihnethocommitrequesVchangemihftomihfuserVWWWWWWWWWWWWWWWWWWWW WWW)W-WclayersWWWWWWWWWBWeWWWWWWWWlayoutWlcpWVWyWleadsWleastW W'W5W7WKWLWMWNWWWWWWW WleftW!W WlegacyWlengthWWW=WHWWW6WWWless<WgWletWlet'sWlevelW WWWWlevelsWliasonWlikeWWW0WWWWWWWWlikelyW WWlikewiseWlimitW WlimitedWWWWW'W>WAW(WlimitingWW@WWWlineWWWFWeWjWWWWWWWRWxWWWWline1WlinesWWWbWeWvWW WgWDWEWFWGWJWKWLWMWNWPWQWRW[W^WaWbWcWeWcsapsWW&WWWWWsaveWsayWWW7WWWWsayingWWsaysWscaleWscanWWRWWWWWscanningWscenarioW&Wscenarios&WschemaWW.WschemeWscope6W7W<W?WWWWWWWWWWWWscratchWsdo'WWsdo'sWsduBWte machine. 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 EDTcSThere's an extra period at the beginning of ".There are two kinds of transport...".d66g5536j/Change to "There are two kinds of transport..." 2007/09/1909/11/2007 11:55:31 EDTNoEHeubaum, 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." 2007/09/1909/11/2007 11:53:29 EDTNoEHeubaum, Karl FFApproveGProducer^ Editorial_11`14a4cN"Network management system" should be capitalized to match the other acronyms.d64g5538j&Change to "Network Management System". 2007/09/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". 2007/09/1909/11/2007 11:49:56 EDTNoEKiernan, Brian GFApprove540 2007/09/17#-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-rspderegistrationVwuFcmac-hs Wmac-wlanZW\WmachineWWWWWmachinesWWMWmacroWmadeWW=WWW'WWmagic WmainWWWWmakeWWWWW&W5WuWWWWWWWW WmakerWefereCVinabilityWincludesWWWWW)VeVthedefaultmimetypevalueisincorrect(V)V)VeVthedefaultmimetypevalueisincorrect(V)V)VeVthedefaultmimetypevalueisincorrect(V)V)Votherhthedefaultmimetypevalueisincorrect(V)V)V)ViVthedefaultmimetypevalueisincorrect(V)V)VViVthedefaultmimetypevalueisincorrect(V)V)VnctionthatcouldbVtheimplementordoesn'tcarewhatmayormaynothavebeenpVtheinfofrommnisinformativeandsoitdoesnotcontaintܶVxed425g5177jAdd 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. 2007/09/1909/16/2007 03:08:31 EDTNofERajkumar, 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.d424g5178j:One possibility is to make these MIHF generated primitives 2007/09/1909/16/2007 03:08:31 EDTNogd423g5179 2007/09/1709/16/2007 03:08:31 EDTAcfromWWWWWWWWWWWW W WWWW.WFWWWWWWWWWWWW/WNWZW\W_W`WWWWWWWWfromline1to13thecontextdoesnotreallyrelatetocommaVfrom/toWfroms5Wfront WWfunctionWWWWWWWWWfunctionalWfunctionalityWW]WWW*WWWWfunctionsWWWWWW&WWWfundamentallyWfurther?WfurthermoreWWfutureWWWgWWW%W[W]WgWuWWWW(W/W3WWWWWWWWWWWWWWgenerallyWWWgenerateIWtWWWgenerated WW[W\WaW~WWWWWWgenerates]W WxcitappearsthatcosvaluesfromthelinkparamtypeofgenerFVitappearsthatipaddressinformationstatusisunnecessarynVoVitisbettertoincludealistoflinkidentifiersinmihreBVitisimportanttonotethatwithcertainaccessnetworksanVitisthemihusernotmihfthatprocessesthismessageVitisverydifficulttocross-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 EDTYes)Pd335g5267j/Clarify mapping transport address with MIHF ID. 2007/09/1909/15/2007 00:01:16 EDTYesE 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." 2007/09/1909/15/2007 00:00:07 EDTYesE 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. 2007/09/1909/14/2007 23:51:12 EDTYesE Kim, YonghoF DisapproveGProducer^ Technical_17`1a5.3.3.5d332g5270 2007/09/1709/14/2007 23:49:26 EDT09/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Editorial_32`33a5.7.2c"Sentence starts with a period (.).d44g5558jDelete leading period 2007/09/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.6 2007/09/1909/10/2007 07:08:58 EDTYesEEmmelmann, 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 10 2007/09/1909/10/2007 07:08:58 EDTYesEEmmelmann, MarcF DisapproveGAcademic^ Technical_25`1a5.5.2cd41g5561 2007/09/1709/10/2007 07:08:58 EDT2007 15:23:06 EDT 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$WWWWWWWunclearwhatoldlinkactionsisreferringtothemnornetw}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_WWbWwWWr@F DisapproveAjayF 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?ommands" 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?. What if more that one remote MIH User exists, which one is responsiB#ble for responding to this request?08:31 EDTonsareanormativVDcwouldbenicetohavethemiheventsintable4orderedaccoVwouldn'tWWwouldn'titbeusefultoreferencepreviouslydefineddefiniVwpaWwrapWwrongW/W2W:WWW WwwanWxNWxmlW<WxmldoesnotcompileVxvWxxx WWxxxxWxyzWyankedWyes1WWyetWWWfWW Wyet-to-be-definedWyieldWyouWWWWWWzeroW conditions 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ܠWWWWWWWWWWxd615g4987j Please see the contribution #307 2007/09/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#2 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_73`40a7.3.12cAWhy 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.d613g4989 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_72`54a7.3.11cd612g4990 2007/09/1709/16/2007 21:41:08 EDTrskWqualifies߮Wqualify߮W'WW{\crecognizingWrecommendationWW&WrecommendationsWWrecommendedWrecommenedWreducesWredundantWWWWhW|WWWWreestablishmentWrefWreftotable8access-network-aux-ithetablesouldnotcontVreferWDWEWWWWWWrefertocontribution21-07-0317-00-0000-sinformationieVreferenceWWWWWWW WW-W8WdWiWWWWWWWWWW0WWWWWWraft. 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.WdbmWdcdWdecideWdecidesWdecisionWWWWWWoreplacethe802.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 EDTocrequiredWWWWWWWW2WJWWrequirementWW WrequirementsWWWWW&W.WgWWWWWWrequiresWrequriedWreservationWW W*WWWE 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_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 EDTQ)E Koh, BenjaminF DisapproveGProducer^General_34a6.2.5cMIH registration is stated to provide for authentication and authorisation, however no specific information is given as to how to incorporate the security aspects.d229g5373j%Update section with text on security. 2007/09/1909/14/2007 02:24:47 EDTYes*E Koh, BenjaminF DisapproveGProducer^General_44a6.4.3cThe current Command Service allows for querying of available resources but does not provide any functionality for the reservation of resources by MIH users.d228g5374jNMake allowances to enable an MIH user to request for reservation of resources. 2007/09/1909/14/2007 02:24:47 EDTYes+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/09/1909/14/2007 02:24:47 EDTYes,E Koh, BenjaminF Disapprove6 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-303-00-00002W21-07-304-00-0000-or6W21-07/320r0W21-07/321r0W214kW2170W224jW226iW23-43hW24%W25-49W25.133W25.2152W26WWWWuWWW27WQWqWuW28uW285QW287QW288QW29WuW2g/3gW2ndW2sW3%W5W=WQWWW3-mbms/W3.23W3.7HW305W306WW307W308WW309WW32QW32-32\W32-33[W33+W34W35jW35-36[W36W37W3gppWW'W0W4W6W8W;WW3gpp/3gpp2W3gpp2WW:W3rd:W4WW4-55W40QW41WW41-43W42W43WjW46WQW47-48,W49WWWjW5<WWWW5.1.1WsJd59g4894 2007/09/1709/10/2007 07:08:58 EDTcsyntaxWsyonymousWsystemWWWWWWWUWWWW WWW#WWWWWWWsystemsWWWWsytaxWsytaxofprimitivesintextdoesn'tnotmatchsyntaxinadjoVtWWtableWWWWWWWWW3W4WWWWWW3WwWyWWWWWWWWWWWWtable10statesairinterfaceforlinkgetparametershoweveVtable14ipisnotatransportprotocolsimplystatingthatVtable5doesnotincludethemihlinkactionsasacommandtVtableb4linktypeumtsismeaninglesssupposedlyw-cdmafd3Vtableb4thresholdwhichisusedextensivelyforlinkconfiVtableb-13Vtableb-15datatypeforrdfinformationquerywrongdefaultVWWWWWWWWWWW W W WW V^ 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).s identifies the current link" to "This identifies the source link of the handover". 2007/09/1709/16/2007 03:42:16 EDTYes߻93jCorrect definition of "protocol data unit". A possible definition is: "Packet produced by a protocol for exchange between the protocol's peer entities." 2007/09/1709/16/2007 06:10:15 EDTYesߺE Feder, PeretzF DisapproveGProducer^ Technical_127`32c[The description contains "This identifies the current link" for the source link identifier.d459g4494j_Change "This identifies the current link" to "This identifies the source link of the handover". 2007/09/1709/16/2007 03:42:16 EDTYes߻tifies the current link" to "This identifies the source link of the handover". 2007/09/1709/16/2007 03:42:16 EDTYes߻d458g4495 2007/09/17=jstatethatdiscoveryofmihposoverl3isoutofscopeofiVstated]WstatementWW&WkWlWmWWWstatementsWstates WWWWstatingJWstatisticsWstatus WW_WdWeWkWlWmWvWW2W9WstayRWSWlWWstepsWstill]WwWstring~WWstronglyWstructures/drawings WstyleWsub-clause0WsubclauseW"W#W$WWWW WsublayerWsubmittedWsubnetWsubparameter WsubscribeWWsubscriberWsubscriptionWsubsequentbWF |}~〃ぃゃッ㄃ㅃㆃ㇃㈃㉃㊃㋃㌃㍃㎃㏃㐃㑃㒃㓃㔃㕃㖃㗃㘃㙃㚃㛃㜃㝃㞃㟃㠃㡃㢃㣃㤃㥃㦃㧃㨃㩃㪃㫃㬃㭃㮃㯃㰃㱃㲃㳃㴃㵃㶃㷃㸃㹃㺃㻃㼃㽃㾃㿃ƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃ ecified 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%W1DjI 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?) 2007/09/1908/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.d5g5597jzAdd a subclause defining conventions for PDU structures/drawings in this standard. (See 802.11-2007 7.1.1 for an example). 2007/09/1908/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_144a8.2.1d4g5598 2007/09/1708/24/2007 10:31:14 EDTSNR or RSNI.d631g4322 2007/09/1709/16/2007 23:32:08 EDTYes^cincludes^WWWWWWincludingWinclusionWWincoherentWWincoherentusageofsinglevsdoublequotationmarksVincoherentusageofsingularorpluralVincompatibleWincompleteWWinconsistencyWJWinconsistentzW{W3Winconsistentontableformatsforprimitiveparametersegp3Vincorporate)WincorrectWIWWW:W;WWincorrectlyWincreasingWWWincrementingWincudeWindeedWindefiniteWindependenceWindependentW'WWWWWWindicateWWW=W\WaWbWwWWWWindicatedWWWWWWWWeGProducer^ Technical_32`44a5.7.2c DisapproveGProducer^ Technical_32`44a5.7.2cd507g3797 2007/09/1709/16/2007 12:18:13 EDTiT~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".od76g5526j:Correct the figure and the resulting reference model text. 2007/09/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_6`57a3cAThe 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.d75g5527 2007/09/1709/11/2007 17:46:47 EDTYesWW#'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 EDTNoWQWUWW cIt 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. 2007/09/1908/24/2007 10:31:14 EDTYes EStephens, Adrian PF DisapproveGProducer^ Technical_144`29a8.2.1cA'"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. 2007/09/1908/24/2007 10:31:14 EDTYes EStephens, Adrian PGProducerd2g5600 2007/09/1708/24/2007 10:31:14 EDT(jtheseWWW5W]WfWkWlWmWWWWWEWWWWthesesWtheyWWWWWtWthing0WthingsWthisWWWWWWWWWWWWWWWWWW WWW"W#W&W(W)W-W0W7W@WCWGW`WbWgWhWjWnWoWvWwWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW.W3W=WJWMWPW^WcWWWWWWWWWWWWWWWWWW W WW'W(W,W7WWthroughoutWWthroughputWFWthus]Wtile$WtimeWWWWtimerW`WWtitleZWtlvWWWWhcasimilarmechanismmaybeavailableforieee802.16forthi Vastawithipv6interfacedoesnotneedtoknowwhethertheVa-1wWyWaaa7WabbreivationGWHWWWW<WgWvWWWW'WaboveWFWJWabreviationWabritrary1Wabsence6Wabsenceofamedia-dependentsapforgsm/egprsthereisonly6VabsoluteWabstractWabstractionsWacWacceptedWaccessWWWW W WWWW&W1W5W6WOWWWWWWW WWWaccessibleuWaccommodateWaccomplishedWaccordingWWW"W#WKWLWMWNWWaccordingtotableb-2page176networkerrorisindicatedbVaccount~WWWackWWWWWWWWWW'WackfailureisnotrelatedtoplrackfailureisatransmitVack-rspWWD09/16/2007 03:38:14 EDTYesEE 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. 2007/09/1909/16/2007 03:38:14 EDTYesFE 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.jd456g5146 2007/09/1709/16/2007 03:38:14 EDTYesclarification+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ÃBackWF 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 entires 2007/09/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 2007/09/1909/10/2007 07:08:58 EDTNoEEmmelmann, 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 ...." 2007/09/1909/10/2007 07:08:58 EDTNoEEmmelmann, Marc9/171YjlistofsupportedmiisquerytypesonthelocalmihfVlistofsupportedtransporttypesonthelocalmihfVlistedWWlisteningWlistskWlWmWWWWWW&Wlocally WW+WlocatedWlong2WlongitudeWlongitudeshouldbenormalizedtowithin180degreespositivVlook WW2WlostWlowerWW;Wlsb=WmacWWWWWW;WmachinesWmain5WmakeWWWWWW5W=WfWmaketheannexnormativeVmakes0Wmaking+W]Wmakingtheseparametersoptionaldoesn'tsolveanyproblemi]VmanagementWWWWW(W<Wmandatory5Wmap5WmappedWmappingWWmappingsWmarkedWWmasked=WmatchWWWmaterialWWmaxWmaximumWmaximumdataratein802.11termsisthehighestavailablebVz8 cA Channel utilization has nothing to do with Maximum Link Data rate. Throughput here is curiously defined to be Maximum Link Data rate (P284L61). Channel utilization is defined in 802.11 to mean fraction of time the medium is busy (CCA). These are incompatible terms. xml" (which is applicable for query result, but NOT query) to: "application/sparql-query" 2007/09/1709/16/2007 10:24:17 EDTNoEFamolari, DavidFApproveGGeneral Interest^ Editorial_103`19nical_198`38cfTable B-15 -Data type for RDF information query: Wrong default value has been specified for MIME_TYPE.d504g3800jIn 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" 2007/09/1709/16/2007 10:24:17 EDTNoEFamolari, DavidFApproveGGeneral Interest^ Editorial_103`19d503g3801 2007/09/1709/16/2007 10:24:17 EDT&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/17mGProducer^ Technical_124ciIn *HO_commit*, targetPoa should not be MAC_ADDRESS if network type doesn't support that form of address.d585g5017jMIH_N2N_HO_Commit.request / .indication and MIH_MN_HO_commit.request / .indication: Target PoA type MAC_ADDRESS, change to LINK_ID. 2007/09/1909/16/2007 16:08:43 EDTYesEWilliams, Michael GF DisapproveGProducer^ TechnicalcWhy 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_IDv change the type to LINK_ADDRESS wAccepted-Modified 2007/09/1909/16/2007 16:08:43 EDTYesEWilliams, Michael GF DisapproveGProducer^Editorial (was Technical)c,no Info Response Binary List TLV in Table C2d583g5019Michael GF DisapproveGProducer^ Technicald585g5017 2007/09/1709/16/2007 16:08:43 EDTGcݠG_GcareWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW$W&W.W4W<WJWKWLWMWNWeWkWlWmWqWWWWWWWWWWWWWWWWWWWWWWWWW WWWWWWW W'W/W>W?WZW\WgWmWtWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW WarethenonormativereferencesusedbythisstandardegwhaVW8W9Wlevyjosephs6V7V8V9VmqWrWmarcW W W W W WWWWWWWWWWWLcpagesWWpairIWpairedWpairing WparaWparagraphWWtWWWWW/WWWparagraph/bullethWparagraphsWWparamW2WFW[W^WaW2WparameterWWWGW[W`WWWW6WDWIWYWWWWWWparametersWWWWWWWWW WGWUW^WaWfWqWWWWWWWW2W3WJWaWWWWWWWWWWparametersdcducdsibsystemparametersarenotdefinedVparametersforlinkgetparametersprimitivelinkparamtype2VparametesWparenthesis1WparmetersWparsing=WpartWW6W=WWWWWWWWWWWpartiallyWparticularW[WWWWWpartnerWWposWWWKWLWMWNW 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'WWWWWWWWWWWsuffersWsufficientWWWsuggestWWWWWWWWWWWWdisapprovevoteor 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;WLcfitWfitsWfixedWWHWWWWWbilityWflexibleWflow*WflowswWWfocused<WfollowedWwWfollowingJW_WtWfontWfontofparametersinlistneedstobemadeconsistentVforWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWW%W'W+W/W0W4W6W7W:W=WBWCWGWJWKWLWMWNWYWZW[W\W]W^W_WcWeWfWqWrWsWxWyW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWTud12g5590jjDelete all "shall" statements and conformance requirements for this clause and all service specifications. 2007/09/1909/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.d11g5591jInclude 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). 2007/09/1909/03/2007 16:49:33 EDTYesE Seifert, RichF DisapproveGGeneral Interest^ Technical_143a8c;No conformance requirements are provided for this protocol.d10g5592j(Include a PICS proforma for this clause. 2007/09/1909/03/2007 16:49:33 EDTYesE Seifert, RichF Disapprove 2007/09/17Hab2.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 EDTWKWexpectedW cAI 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?:)jconditions W%WWconductWconference)WconfigWconfigurable`WconfigurationgWkWlWmWconfigurations%WconfigureWWLWQWXWoWconfiguredW`WconfirmWWWWCWDWconformance%WWWconnectedWconnectionWWbWWconsequenceWconsider WWW+W9WWWconsiderationWconsiderationsWconsidered WWWconsistentWW3WWconsistentlyWWWwWxWzWconsistentlyaddorremovemobilitymanagementfromentiredxVconsistentlyuseonevaluewVconstructstWcontainW%W2W^WcWcontained7WcontainerWWWWWcontentW0WWcontentsSWWWcontextW0Wcontexts WWcontinutity&WcontributionWWWWWWYWWW2W6WVx~vd408g5194jA 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.  2007/09/1909/16/2007 03:08:31 EDTNowERajkumar, AjayF GProducer^ Technical_121`8cAThe texts describes this as either an MIH User to MIH User exchange or as a locally initiated handover (i.e. when dst MIHF ID is the local MIHF ID). However, the call flows indicate that it could also be a combination of the two (which is confusing). Page 230 and 231 describe it as an MIH User to MIH User exchange, followed by the issuing of Link Action commands to actually perform the handover. Page 252 shows it as a combination MIH User to MIH User and Link Action commands issued by the d407g5195 2007/09/1709/16/2007 03:08:31 EDTg5284jFrom clause 5, there was a registration and discovery process for initiating an MIH connection. Include these processes as part of the state machine definition. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, 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.6 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_55`3a6.5.6.3d316g5286 2007/09/1709/14/2007 23:15:41 EDT3EChaplin, Clint FF 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."  2007/09/19WsWsWsWsWsWsWsWsWsWsWsWsWsWWsWsWWsWsWsWsWsWtextWWWWWWW W WWthܺWthanܟWܠWWWthatvW܅WܟWܠWWWWWWWWWWWWW*#ctheieee802.21standardspecifiesmihfunctionthatcouldbVtheimplementordoesn'tcarewhatmayormaynothavebeenp,VtheinfofrommnisinformativeandsoitdoesnotcontaintVtheinformationmodelproposedinfigure19isoverlycompliVthelinenumbersarepositionedsuchthatthechangebarsovVthelinkactionrequestissenttomacwimaxhoweverthecor_Vthelinkactionrequestissenttomacwlanhoweverthecorr`VthelocationusedintheinformationmodelisforthepoafoVVthemaymakesitsoundoptionalVVthemediadependantnativedefinitionsforthemihcommonteVthemihfunctionsinmnandnetworkentitiescommunicatewitVthemihmnhocompletemessagemaybesenttothetargetposUVissingdefinitionmustbefilledVthemobilenodeiscapableofsupportingmultiplelink-layerVtheneedanduseofthemihnethocandidatequerycommanda V^cinformativeW%W/WWWWinformedWinfrastructureWinitWWinitializeWinitiatepWvWWinitiatedgWqWwWinitiatingWinitiatorWinputWinsertWWinsertthebeforefollowingconventionsareusednotproperVinsertthebeforefollowinghandoverflowrefersnotproperVinserts<WinsideWWinstanceWWinsteadWWWW 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.I?cI 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. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, 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. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interestd312g5290 2007/09/1709/14/2007 23:15:41 EDTciassumethatthetlvtypeassignmentisnormativeforthisVibelievethisisalreadyintheieeedictionaryFViblievetheuseofacronymsintheabbreivationtobeconfuGVHVicannotbelievethataproposedstandardsuchasthiswhichVidonotagreewithprovidingareferencestonamedinternalEVidonotseeawayforamobilenodetousemiistodeterminVidonotseeawayforthenetworktocommandamobilenodeVidonotseeawayforthenetworktoqueryamobilenodetoVidon'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 Wd50g5552j5Delete ref to 802.11 and create an annex as suggested 2007/09/1909/10/2007 07:08:58 EDTYesEEmmelmann, 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 sentences 2007/09/1909/10/2007 07:08:58 EDTYesEEmmelmann, MarcGAcademicd48g5554 2007/09/1709/10/2007 07:08:58 EDT/qjeitherremovethemihnethocandidatequerycommandorbettVeitheruse802.1abtoachievethisresultordemonstratewhyVelementWpWeliminateWelseiW'WelsewhereWenableWWW*WencodeWencodedWWWWencodingWWencrypt7Wend7WWWWWW4W=WWendingWendoWenhanced)WenhancementsWensureWWWWensuringWentireMWxWentirely'W9WentiresWWentitiesWWWWWWBWWWWWQWWWWWWWQWWWWQWWWLWQWWWQWWWWWWWWWQWWWWWWWWWWWWWWWWWWWWWQWWWWWWWgeWusagesW%d95g5507jClarify the text. 2007/09/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_70`32a7.3.8cAThe 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. 2007/09/1909/11/2007 17:46:47 EDTYesEMyles, Andrew FF DisapproveGProducer^ Technical_69`25a7.3.6.3cd93g5509 2007/09/1709/11/2007 17:46:47 EDTmj 'jAFor 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 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).equirebothmobileeVhandoverackWhandoversWW W!WcWsWtWWWuWxW(W)WGWhappenLWMWrWhappensWWhas W'WLWMWrW߁WߍWWWFWcWfWuWvWzWWWWW%W'W8W=WSWsWwW>UIE Cypher, DavidF DisapproveGGeneral Interest^ Technical_113`53a742112ce of acronyms in the abbreivation to be confusing.d198g5404j+Spell out MN and PoA in the definition 3.7. 2007/09/1809/13/2007 15:42:30 EDTNoIE Cypher, DavidF DisapproveGGeneral Interest^ Technical_113`53a742112cion to be confusing.d198g5404j+Spell out MN and PoA in the definition 3.7. 2007/09/1809/13/2007 15:42:30 EDTNoIE Cypher, DavidF DisapproveGGeneral Interest^ Technical_113`53a742112che abbreivation to be confusing.d198g5404j+Spell out MN and PoA in the definition 3.7. 2007/09/1809/13/2007 15:42:30 EDTNoIE Cypher, DavidF DisapproveGGeneral Interest^ Technical_113`53a742112cd197g5405 2007/09/1709/13/2007 13:56:26 EDTitorial_35`16a6.2.5nF DisapproveGProducer^ Editorial_35`16a6.2.5d484g3820 2007/09/1709/16/2007 07:13:12 EDT?pcHow 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. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, 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. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Editorial_32`33a5.7.2c5Remove the period from the beginning of the paragraphd308g5294j See comment. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral InterestR8% 2007/09/1909/16/2007 07:13:12 EDTNo&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/09/1709/16/2007 07:13:12 EDTYesWWWWWWWVWWWWWWWWWWWWWWWWWWWVWWWWWWWWWWWWWOWUWVWWWWWOWUWVWWWWWOWUWVWWWWWOWUWVWWWWWWWWJWOWUWVWWWWWWWWWWWWWWWWWWWW;WtakeߔWWWtakealookwhatother802standardsdoesanddefinethenorߔVWcoffWoffers@Wold WuWvW}WWWoldlinkactionsusesthelinkactionstypewhichdoesnoteVVWWWWWW&W7W?WFW[W`WbWfWkWlWmWpWuWWWWWWWWWWWWWWW WWWWW#W$W/W3W4W=WAWpWuWonmessagesmihmnhocommitrequestandmihmnhocommitinVoneWWWWWWWWW WWW.WKWLWMWNWRW[W]WeWnWoWWWWWWW5Wone-octetWone-to-onekWlWmWone/twoWonlyWWWWWWWWWWWWWW,W6W<W[WcWeWuWWWWWWWWWWW'W5WNWWz)|a6.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_޼W޼W޼WCW޼W޼W޼W޼W޼W޼WWsystemCW޼W޼WWsystemCW޼W޼WWsystemCW޼W޼WWsystemCW޼W޼W޼W޼WW޼W޼WWWWtechnologiesWWWWW!W$WtechnologyWWW%Wtechnology-specificWtermWterminateWterms܄W܈WtestWtextWWWWWWW W WWthܺWthanܟWܠWWWthatvW܅WܟWܠWWWWWWWWWWWWWW#W%W+W.Wy cAThe 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.WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW23-43fordiscussionVVremovedܱWUWrenameWrenamer1r5asj1j5throughoutthedocumentVreperesent!Wrepetitive*Wv8UjdeletetheversionfieldAVdeletethisparameternVoVdeletethroughputandpacketerrorratefromqoslistFVdeletedWdeletesWdemonstrateWdependentWkWlWmWdepending WWWWdeploymentWderegistrationWderegistrationbyc-nem-rspderegistrationVdel, 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 SponsoC r ballot.WWW6WݛWW W?Wfigure-7Wfirst܍WܟWܠWWWPW|W}WݽW WfirstintroducesomethinglikeapicssomewhereintheannexVfixW܀W܄WWWWWfixthefontthisisthereisseveralotherplacesindraftVfixthemodellingsothatthestandarddoesn'tplayfastandVfixthepdfand/orthetextsothepagenumberscorrespondVfixthetextVVcialwaysthoughtitispossibletousemihsignallingexchanViassumethatcomponentinformationelementdefinitionsareViassumethatinformationelementdefinitionsareanormativViassumethatthemiisschemadefinitionisnormativeifsoVof 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.d80g4873jChange 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. 2007/09/1709/11/2007 17:46:47 EDTYes6EMyles, Andrew FF Disapproveument. 2007/09/1709/11/2007 17:46:47 EDTYes6EMyles, Andrew FF Disapprove 2007/09/17c-4 2007/09/1909/16/2007 07:13:12 EDTNo5ERudolf, 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.d473g5129jRecommend 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. 2007/09/1909/16/2007 07:13:12 EDTYes6ERudolf, 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.d472g5130 2007/09/1709/16/2007 07:13:12 EDTYesveܸWpossible܅WܙWܞWܡWW'a8.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 Annex 2007/09/1909/14/2007 02:24:47 EDTYes(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. 2007/09/1909/14/2007 02:24:47 EDTYes)d229g5373 2007/09/1709/14/2007 02:24:47 EDTc3.40BW3.43W3.44AW3.6W3.6homenetworknetworkmanagedbytheoperatorwithwhomtV3.7-ghzW30W300W30thWW31W32-bit=W35WW35-40eWs 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.Gly 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.Gnce 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.GWޠWޡWޮWްWܝWEEastwood, Lester FF DisapproveGProducer^ Editorial_51`25a6.5.4csentence is ambiguousd113g5489j`Change to "Functional entities shall discard any received IE with an unrecognizable identifier." 2007/09/1909/12/2007 02:37:36 EDTNoEEastwood, Lester FF DisapproveGProducer^ Technical_105cMThe Purpose and usefulness of MIH_Net_HO_Candidate_Query command are unclear.d112g5490jJremove all definition and mentioning of MIH_Net_HO_Candidate_Query command 2007/09/1909/12/2007 02:37:36 EDTYesEEastwood, 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. 2007/09/1909/12/2007 02:37:36 EDTYesEEastwood, Lester FF DisapproveGProducer^ Editorial_37Producer^ Editorial_37d110g5492 2007/09/1709/12/2007 02:37:36 EDTWW9Zjprotocol'sBWprotocol-conformance&WprotocolsW7WWprovideWWWWWWWWWWWW Want 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.*d604g4349jis list for network selection or handover decisions." 2007/09/1709/16/2007 21:41:08 EDTYes)ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`29a6.5.5.2cA*When more than one access network 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.*d604g4349j 2007/09/1709/16/2007 21:41:08 EDTYes]d433g5169jADMaking 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.D 2007/09/1909/16/2007 03:08:31 EDTNo^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. 2007/09/1909/16/2007 03:08:31 EDTNo_d431g5171{_cThe 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.d16g5586jAIf fragmentation/reassembly is needed for proper operation of MIH, then it must be provided as a function within the protocol. If not, then eliminate all references to fragmentation, and ensure that the maximum message size (SDU) submitted by MIH to any allowable lower layer does not exceed the maximum frame size supported by those layers (i.e., determine an acceptable maximum SDU that will work with any allowable MAC). 2007/09/1909/03/2007 16:49:33 EDTYesE Seifert, RichF DisapproveGGeneral Interest^ Technical_143`16a8.1cd15g5587 2007/09/1709/03/2007 16:49:33 EDTxxxxvWxyzWyankedWyesWWyet܈WW WTWyet-to-be-defined܈WyieldWyouWWWzero܁WOjlimitWWlimited'WlineWWWWW%W:W\WjWpWWWWWWWWWWWWW0WQWiWjWkWqWWline38Wlines+W,W[WhWWWWWWWWgWlinik8WlinkWWWWWWWWWWWW W WWW-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.d476g3828ss 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.d476g3828 2007/09/1709/16/2007 07:13:12 EDTYes%jIf 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. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, 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.d304g5298j`There needs to be some form of ensuring that the MN is authorized to obtain the MIH information. 2007/09/1909/14/2007 23:15:41 EDTYesEMontemurro, MichaelF DisapproveGGeneral Interest^ Technical_15`34a5.3.1d303g5299 2007/09/1709/14/2007 23:15:41 EDT3jdeleteallreferencestomihnetsapfromthespecdeletereVdeleteallreferencestomihnmssapfromthespecdeletereVdeleteallshallstatementsandconformancerequirementsforVdeleteannexfVdeleteannexjVdeleteapostrohpemn'sVdeletebothoccurrencesYVdeletecases12and3onpage51replacethelengthfieldm=VdeletecurrentlinkidentifiefromallmihhandoverprimitivesVdeletefromthatperspectivemihfoffersaunifiedinterface@VdeleteitemsathrougheandmovetheircontentstoanormatVdeleteleadingperiodVdeletelinepVdeleteline1to13VdeletemiheventsmaybelocalorremoteremotemiheventsoVVesW[Wfile1WWfilled"WWpWpWguresW[Wfile1WWfilled"WWpWpWWfilled"WWpWpWbVform<Wforth,Wfraction Wframe"W0WIWframes/WframeworkdWW csupportingWsupports&WWWWWWsupposedWWW@WWsupposedly3WswitchxWyWWWswitchesWswitchingWsymmetricallyWsyncWsynchronousW^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^WW^W^W^W^W^WW^W^W^W^W^W^W^W^W^WW^W^WW^W^WW^W^WW^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^W^WW^W^W^WW8.2.2yW%W`WW8.2.2.2`W8.2.3.5.1ߏW8.3W8.3mihprotocolstepsV8.3.1W8.3.1informationqueryV8.3.2W8.3.2resourceavailabilitycheckV8.3.3W8.3.3resourcepreparationV8.3.4WWEcwealth%WtWcontainstWtWtWtWtWtWcontecttWtWtWtWtWtWtWtWtWtWtWd to be corrected.d474g3830jDefine 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.d474g3830jDefine 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.d474g3830jDefine 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.' jcorrectfigure26toshowmihprotocolheaderhasfixedlengVVVcorrectitVVVVVVcorrecttableb14tomatchb13Vcorrectthe802.21architecturethe802.21entitymustresidVcorrectthefigureandtheresultingreferencemodeltextVcorrectthetextVcorrectthetexttostatethatlinkdownisgeneratedwhanaVcorrectto4VcorrecttolinkscanVcorrectuseofaandanthroughoutthewholespecVcorrespondWWWWcrossWcross-referenceWcrosses`WcrossingaWcs&W;WcurrentCWDWEWzW{WWWWWWWcurrentlinkidentifieWcurrently`Wd%WWdataWWWWWWW(WBWXWZWWWdatatypeOWRWdatatype1Wdatatype2Wday'Wde-emphasizeWde-emphasizemihfdiscoveryasseparatemihservicemanagemeVdecidingWWocanalogWandWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W WWWWWWW$W%W&W,W/W2W4W5W7W<W=W>W?W@WAWFWIWJWKWLWMWNWOW]W^WbWcWeWfWiWkWlWmWuWvWwW~WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW W W W WWWWWWWWWWW W#WV_Qjquestions@Wr1WTWVWr2UWr3TWVWr5Wr99/WradioWradio/dualWramificationsWranameWranamehomenetworktohomesubscribernetworkinthisclausVrangeWWrangesWrapidWrateWWWFWQWWratherWvWrawXWrdf.W0W4Wre-defineWre-orderWre-orderrowsoftable10Vre-organizeWWre-use1Wre-writeWWre-writedefinitiontodescribethefunctionandresultsVre-writingWre-writtenWeGProducer^ 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 EDTYes?l 2007/09/1909/14/2007 18:36:55 EDTYesE Julka, VibhorF DisapproveGProducer^ Technical_150`16a8.3.1cConfiguration of the MIHF is not specified in this standard. Should add text to state that configuration of the MIHF is outside the scope of the standard.d292g5310jQTo end of line 16 add following text "and not within the scope of this standard." 2007/09/1909/14/2007 18:36:55 EDTNoE 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." 2007/09/1909/14/2007 18:36:55 EDTYesE Julka, VibhorF DisapproveGProducer^ Technical_146`65a8.2.2.2cd290g5312 2007/09/1709/14/2007 18:36:55 EDTlengthasindicatedinfigur$VVVlheaderisoffixedlengthasindicatedinfigur$VVVindWminimiseߴWminimumߝW߮WcWߖW*WucmanagementWWWWWWW#WWWWW#WxWWWWWWWWmanagerWWWmandated&W5Wmandatory5WWWWWWmandatroyWmanipulatedWmanualWWWmanyW<WgWWWWmanyfiguresaremissingthevertical/horizontallinesindicgVmapWkWlWmWmappedWWWmappingWWWWWWWmappings5WWmapsWmarkedJWmarketWmarksWmatchWWWWWWWmaterialWmaterialsWWmaxWWmaximumWWW the services (notably, command service) it provides is dependent on prior sd471g3833 2007/09/1709/16/2007 07:13:12 EDTconlyanmihfcapablenetworkentityshallrespondwiththisVonlymihnetworkentityshallrespondtobroadcastedmihcapVoperateWoperatingWWoperationW&WWW'WoperatorWWWWoperator'sWoperatorsWWopportunityWopposedwWWoptimizationWoptimizeWoptionWW WWWWWWWWWWWWWWWWWWWWWWWW W W WW&W'W,W1W7WDWEWYWeWgWnWoWwW}WWWWWWWWWWWWWWWWWWWWWorderWWW%WvWxWyWWorganizationWorganizedWoriginalWWWotherWWWWWWWWWW?WzW{WWWWWWother'sWycSeveral 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 it 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, 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 it 2007/09/1909/16/2007 21:41:08 EDTYesESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_87`31a7.4.4.cd615g4987 2007/09/1709/16/2007 21:41:08 EDTWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEWEW/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 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 R3 WUWVWWWXWߑWߝWsupportedisquerytypeTWsupportedmihcommandlTWsupportedmiheventlisTWsupportedtransportliTWsupportingcWsupportscWsupposed߉WsyntaxWsystemWtߞWtableWW>WtakeߔWtakealookwhatother802standardsdoesanddefinethenorߔVtarget<WZWtbdߊWtd-scdmaߪWtddߪWtechnical߁WߞWߠWtechnologiescWdW߁WߞWߧWߪWtechnologycW߁WߝWtechnology-specificߨWterm]WterminateJWterms WWtestߢWtextWLWMWeWmWnW߂WߋWߒWߖWߗWthCWthan(W)WJW߇WthatWW(W)WQW[W\WaWcWjW߁W߇W߉WߝWߞWߠWߧWs generalinterestVVVVVVVVVVVVVVVVVVVV VVVVVVVOVPVQVRVSVTVUVVVWVXVYVZVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVVV-V.V/V0V1V2V3V4V5V6VEVFVGVHVIVJVKVLVMVNVOVPVQVRVSVTVUVVVWVXVYVZV[V\V]V^V_V`VaVbVcVdVeVfVgVhViVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVVWcA_d6v@@KcBTdGujBB1j c Fscapability 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.d606g4347j Please see the contribution #305 2007/09/1709/16/2007 21:41:08 EDTYes(ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`49a6.5.5.2cibution #305 2007/09/1709/16/2007 21:41:08 EDTYes(ESreemanthula, SrinviasF DisapproveGGeneral Interest^ Technical_52`49a6.5.5.2cd605g4348 2007/09/1709/16/2007 21:41:08 EDTjestablishment0WetcW'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 EDT5gGAcademic^ Editorial_60`58a7.2.2.1c4Rows should be grouped / sorted by service category. followed by the "reports" it gets back locally or from a remote peer.WWWWWcomplyWWcomplyWWWWcomponentsWWWWWntsWWWWWWWWWWWWWWWnentsWWWWWWWWWWcomputing+W+W+Wting+W+W+Wuting+W+W+Wuting+W+W+WplyWcomponent%WcomponentsWcomputing+W+W+W+W+W+W+WplyWcomponent%WcomponentsWcomputing+W+W+Wuting+W+WWcomprisingWcomputing+W+W+W+W+W+W+W+Wuting+W+W+Wnt%WcomponentsWcomprisingWcomputing+W+Wg+W+W+W+WR$cBoth 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.3 2007/09/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.^d489g5113j 2007/09/1709/16/2007 07:13:12 EDTNoWWWWWDWdWWWibelievetherehastobeatleastonequerythereforethesDViproposetomakemiheventsubscribeandunsubscribeparto߇Visuggesttoreplacethe802.3&3gpp2boxesinfigure11bytߋV 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 textkmessagewithforanmgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVmgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgVgV%`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". 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_127`32c[The description contains "This identifies the current link" for the source link identifier.d390g5212j_Change "This identifies the current link" to "This identifies the source link of the handover". 2007/09/1909/16/2007 03:08:31 EDTNoERajkumar, AjayF GProducer^ Technical_132`49cReference to wrong message.d389g5213j)Change N2N_HO_Complete to MN_HO_Complete. 2007/09/1909/16/2007 03:08:31 EDTN