Copyright 1984-1999 FileMaker, Inc. HBAM2016AUG95HPro 5.0)@0inding@cthenormativereferencesectionisblank@@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&`wanghleiUwang€A1.55: Added "Fig/Table Number" field Deleted XML file output option. 1.54: Added "Technical, Satisfied (was Binding)" to value list Comment Type/Group. 1.53: in Reply Comment layout, reduced display to three replies 1.52: *Changed instruction on saving files to specify .USR instead of .fp5 *Fixed bug that wouldn't allow exporting a ballot with no comments. *Fixed "Show All Records in Order" script so that it goes to "Comment List" layout (otherwise, "Show All Records" button in Create andB Submit Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new K 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] ijklmnopqrstuvwxyz{|}~րցւփքօֆևֈ։֊֋֌֍֎֏֐ְֱֲֳִֵֶַָֹֺֻּֽ֑֖֛֢֣֤֥֦֧֪֚֭֮֒֓֔֕֗֘֙֜֝֞֟֠֡֨֩֫֬֯־ֿƒÃăŃƃǃȃɃʃ˃̃̓΃σЃу҃ӃԃՃփ׃؃كڃۃ܃݃ރ߃g^_`€€€€€'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\{]^_`abcde0Abdata@cbecause@modification@Lthebasicschemarepresentationinasn1isnotusefulunles@jlists@sourceidentifiershouldbeprefered@802.16@Qattempts@comment@for@`from@{i@make@ofdm/ofdma@selected@the@thecompliancewith802.16allowsforatleasttwoseparate@there@these@5two@two@redefined@"there@*these@|two@e@|two@unified@ispartwiththemeshmodeisputtingtheunified@guagesyntax@tclanguagesyntax@u@|tofitclanguagesyntax@nguagesyntax@eparameterrcvphyarenot@|tofitclanguagesyntax@phyarenot@|tofitclanguagesyntax@arenot@|tofitclanguagesyntax@onthislineshouldread@typosubscriptyinformulanyky@ geunnecessa@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 PM)Z@B@2@Iֵ@@P;;P;P;;P;;@y„-@q @z @P;;P;;P;bleisnotreferencedinthetextnorhasitanymeani@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€ (O^ Editorial_10`12b'At this time it is more for informationc/This is just a test comment given as an exampleg2211 2005/09/21Marked ayFRajkumarGMember^Technical, Binding_25`1a5bRemove the sectioncThis is another exampled2g2214 2005/09/20 2005/09/20S^Technical, Non-binding_30`2a6bRemovec Example 3g2215 2005/09/20T^ Editorial_40n 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=A4andrea@eric@njedjou@qiaobingandreaajayperetz@yoshihiroy@^binding@ֵeditorial@non-binding@technical@technicalbinding@_ @`p@‚'@a5.1@7.4.7.1.2@8.2.1@Iannex@Rb10@5.3.2@v6.1.5primitivesforlinklayerevents@T8@Bactive@"adoptthefollowingnewtext@Fadvertisement@Namendments@associated@between@mcarry@0completely@etely@@pletely@letely@etely@0completely@n@links@(measurement@9message@multiple@Jon@ only@uparameter@queryresourselist@nreference@replacecurrentsection5.3.2bythesection5.3.2indcn21@greports@/sdo@_subsectionsuch@termination@ this@ttransport@!values@Sweb@2 BD VOTEREMAILpDs`jA.nA%€B?€A€ACC@============6_BdD`@4AFF*KL)QaA0@./////./////qq@@jAqcA%jBDkBZq@<jUq@q@qcMq@qcjqHBq@l_qkCq@qbAjBqjAfkAgq@vqcqboq@Pq@Giq@qPqjA q@qbq@abAqcr@Or=^6r@GprB@jA|rE@N^HrHPqrR@rSbjrT@jSril1rt@'r@Irl4r@bAjB[kA\ 2002-04-15Ballot layout doesn't work. 1.51: slight changes, mainly in "Import Clause Editor's Proposals" 1.5: Added "Reply Comment Layout" and Relationship to reply.fp5 1.4: Added "Comment List for Projection" Split "Commentary Version" from "Global Field Setup" layout Added "Report Number" field and set up layouts for its use 1.3: *Added XML export for IEEE Balloting Center comments *Added "Marked" field 1.2: *Fixed "Import Comments" script. It had not been updated in 1.1 to match the new Ccomment format. *Corrected grammar in email subject. *Made all fields in Comment List layout read/write (except the global fields Doc Number and Ballot Number). *Added Editor's Layout 1.1: Many changes, including addition of use as a balloting tool.  2002-04-15  w  $,.YesNo/,  , : AM PM  w AaBSn DyRoxp zqr srtyuB+zy*{QbSzaq@Hg@@PB s@A 3  $,.YesNo/,  , : AM PMB 3  $,.YesNo/,  , : AM PME 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMXY!€aACommentary Version@A* ww  ww*}Commentary Version # Version NotesCommentary Version Date B A€€€888r ysrtyuB+zw*{EV|GIU}n~pI~YjR[7iaGlobal Field Setupo Email SubjectqEmail TosEmail ccuBallot #fFJ I 3  $,.YesNo/,  , : AM PMJ 3  $,.YesNo/,  , : AM PMK w  $,.YesNo/,  , : AM PMA%x  Yx% ^%  _l%@ l`l@% j%0  al0% cl%  bl@GY^6i7w"#$A=CEw€\€a@5BG4M1R/YOAC+'@€BD8, consequtive in time, of a preamble and data subchannels. --------------------------------------------- 8.3.6.3.5.2.3 should be handed to a clause-editor to be entirely rewritten. ItC needs substantial additional information on how to do this type of rotation in TDD, and it shouldn't use the word frame for allocations. How it will fit under the MAC etc.. (i.e. it needs definition on how this shifted superframe structure fits in with TX/RX boundaries)cH3  @BBA^_`abc€XXXXXXXXACreate and Submit BallotB    E 3 $,.YesNo/,  , : AM PMF 3 $,.YesNo/,  , : AM PMG 3 $,.YesNo/,  , : AM PM'   ^AAssign EditorsE 5 4 3 2 1 0 / . -  ,  *  )  (  ' & % $ "    !Q7AShow All Records in OrderE '` dDTQ8A Export Clause Editor's ProposalsE OFMPR$@` ABCdD^EiFmGjHkQ9A Import Clause Editor's ProposalsE NALL OTABSW@# `BBXXXXYYYYZZYYZZp` "Guillemette" GuillemetteQAAssign Editor 11E@[@!r@a11.@a11.@!r@a11.@802.16.1/D1-2000Q`"11"^52_ 8.2.1.2.5n'tuWdownstreamuWexistuW6M<?ACreate CommentB    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM    3  $,.YesNo/,  , : AM PM     3  $,.YesNo/,  , : AM PM   X , : AM PM      ~LA+Commentary: The IEEE 802.16 Comment ManagerA*by Roger Marks *@A> ww ) ww> AICreate and Submit Working Group Ballot or IEEE Balloting Center CommentsI@AR  33& + RN#Version: <<ACIABB>> (<<ACIABG>>)OView Comment ListA5For help, see 5@A> ww 4 ww>Xhttp://WirelessMAN.org B A   €€A>  ww    ww>AGo To Create Vote Page@A> ww  ww>UV 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 GL2217iA Resolution byB GH ijyi O 3  $,.YesNo/,  , : AM PMP 3  $,.YesNo/,  , : AM PMQ 3  $,.YesNo/,  , : AM PMR 3  $,.YesNo/,  , : AM PMS 3  $,.YesNo/,  , : AM PM* E@^"Technical, Binding"@A>4> = "Disapprove with binding comments"   "Member" Disapprove with binding commentsMemberBOKA/A0@Ҡ@A-A.@A,A-Cancel@A*A+@@A*B0\ ӠpThe vote of type "Disapprove with binding comments" is permitted only by Members. Please correct and try again.Ca)&) = "Disapprove with binding comments" Disapprove with binding commentsl, Binding"^Technical, BindingEOKA/A0@ @A-A.@A,A-Cancel@A*A+@@A*" \ !"A "Disapprove" vote must include at least one "Technical, Binding" comment. Please correct and try again.FC^="Technical, Binding"^Technical, Binding, Binding"^Technical, Binding ABCDEFGHIJK^L_M`NaObPcct and try again. g! QEz\iP{jT|nP}T~TyP!1"#0!1FJ#L53C$1F7VUHU2 3IC dd5BDe5Bf Ec %bR %d %Zt jH @JHHF@J+f* (€UA€VA€XAYType€ZA [Suggested Remedy€\ADe ]f)aTgvhYi(NQAImport Ballot CommentsENALL OTABS# ` ABCDEFGHIJK^L_M`NaObPcQRSTUdVgWiXjYkZm[n\p]v^w_x`ya{bcd e f ghijklmnoQRA Help WebLinkEo@ @A :%http://ieee802.org/16/docs/Commentary.htmlQSAWirelessMAN WebLinkEo@ zt J 3  $,.YesNo/,  , : AM PMK 3  $,.YesNo/,  , : AM PMM 3  $,.YesNo/,  , : AM PMN  3  $,.YesNo/,  , : AM PMN  3 $,.YesNo/,  , : AM PMy RE 3  $,.YesNo/,  , : AM PMF 3  $,.YesNo/,  , : AM PMG 3  $,.YesNo/,  , : AM PMH 3  $,.YesNo/,  , : AM PMI 3  $,.YesNo/,  , : AM PM( HGB Left("Manufacturing", 4) Copyright 1994 - 1999 FileMaker, Inc. All Rights Reserved.1{Balloter: Attach your comment file before sending this email message. The comment file name should include the Ballot Number and your full naC:me in the format "BallotNumber_Lastname_Firstname.fp5".}umQ ¦ w  $,.YesNo/,  , : AM PMæ 3  $,.YesNo/,  , : AM PM   Ŧ 3  $,.YesNo/,  , : AM PM   Ǧ 3  $,.YesNo/,  , : AM PM    @  A1%KFPTHPRPTH NAME MSPCMSPCA2NAMEA 80216Ballot RPTHA 80216Ballot A1!FPTH9RPTHNAME MSPCMSPCAiNAMEA XMLExport RPTHA::XML Export:XMLExportA9kFPTHTRPTH alis(NAMEMSPCFPTHATTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USRTMSPCA NAMEA ReplyData.USRRPTHA ReplyData.USR alisA((TiDriveXBD ReplyData.USR mcFMP5UFSRCommentary Folder 2000. UTTiDrive:Documents:802:802.16:Ballots:Commentary:1.55:Commentary Folder:ReplyData.USR(fp500. UATiDrive:Documents:802:802.16:Ballots:Commentary:1.5:ReplyData.fp5TG3/4:CommentaryDataReplyRhM 9A/%-g>9t 9t 9tJ[F8(t4 8(t48(t4a;z RB2a;za;zRj SjjS$u R   3 $,.YesNo/,  , : AM PM           w $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM      3  $,.YesNo/,  , : AM PM 3  $,.YesNo/,  , : AM PM   p *AImport Group ResolutionsE NALL OTABS# ` ABCdD^EvFwGxHyIJKLMNOP_Q`RaSbTcUgViWjXkYmZn[p\{]^_`abc d e fghijklmnopqQ?AExport Editor's InputEOFMPR$@` ABCdD{EpFnGQ@AImport Editor's InputENALL # ` ABCdD{EpFnGHIJKLMN^O_P`QaRbScTgUiVjWkXmYvZw[x\y]^_`abc d e fghijklmnopqfd Bl#[  bl[# Bmv#K  @ivK# >j#; Dkv;# 8w#+,v+# 0x#  2y# 2C  @BBA( (^_`ab c di j km vwxy€€€          hm Bk xYCSZGjT[Vf\Zvg] ^_* *`*Ca! E!d!E_ G_e_G-f"^g2*t Cjvf# 0x# V In V#  2y # F 2 F# 6{ # 6 qp 6# LF @BBA6 6^ _`a b c dijkmnpvwxy{€€€€€€ 00000000 0 0  0  0  0 0 0000000000000#f,u EBl#.  .#  al# bl# 8w#,v#  2y# 2#v 6{v# In#f qC>pf# L WE@@MarkedQYAExport IEEE XMLEOTABS D[@!d$@`@A14[p 0 h[[ [[ /0 h[p / AQ^AOpen Reply Comment FileE ! FMPRQ'`QdDTQAzHHddE(HH(d'`zA'dE7*`'`+ dDTQ] w  $,.YesNo/,  , : AM PM  UU? €Ad?2     _` a ^@"7 c>gt;Z<lt;Z b>gt;Z<lt;Zd W2&&Zgt;>Zlt;<Z:GC€A VoterMemberIDB G€A ReportNumberB G€A FigTabNumberB G ajayrajkumar@lucent.com 1IEEE 802.21 Comment Resolution for P802-21-D00-02 vivek.g.gupta@intel.comP802.21D00.02 08/20051.55€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)i@k@mcojr^vjyczc|jA}ցjAք^ֆ֋@֎c֓^֗E֛c֟j֤^֨E֫vְ`ִb ֹbA jA ֻiֽccbACccAbAC`$bB&D'bA)C*@+bA.b1bA3C4E5G6cA7bAcbesidesmihmacsapthelsapcanalsobeusedtotransportp֌VbetterWbetween|W֨WWWWbeyongWbi-directionalWbitWbitmap֥WbothWWWWWbox}WbreakwW֧W֬WbriefWbroadcastWWWbsօWbufferedWbuffersWbutrWִWWWWWWby{WִWֵWWWWWWWWWWWWbythecurrentdraftwhenmihfunctionreceiveslinkdetecteVbytesWcalledֵWcannWwWzWցWքW֌W֗W֚W֥WWWWWWWWWWWcan't֒W֥W֦Wcan'tfigureouthowisthissapused֒VcannotWcapabilityWWcapabiltyWcapableWjWcarriedִWcarryWcaseWWWWWcasesWWcellularnW֫WcertainֵWcertainlyrWchangeքWWWW֓^Technical, Binding_27`6a5.6.4c Not so sure.d43vNo specific text proposedwRejected 2005/09/21 2005-09-14֔E Eric NJEDJOU^Technical, Binding_27`26a5.6.6c$New sentence since the May draft. OKd44v withdrawn 2005/09/21 2005-09-14֕E Eric NJEDJOU^Technical, Binding_27`54a5.7.1c>This is only true for .11. The draft needs to be more generic d45jOriginal Text: The packet payload for these services may be carried over L2 management frames, L2 data frames or other higher layer protocols. vNo specific text proposedwRejected 2005/09/21 2005-09-14֖E Eric NJEDJOU^Technical, Binding_27`62a5.7.1cSpecific to one technology! d46jOriginal Text: Thereafter these packets can be encapsulated in a L2 MIH Protocol using MIH ethertype when the payload needs to be sent over normal data frames as in case of ethernet vNo specific text proposedwRejected 2005/09/21 2005-09-14֗42wcnotaccuratekVnotaccurateagainwhatisthemobilitymanagementprotocolqVnotsosure֓Vnottrueicanusethe802.11interfacetotalktoanmihloցVnotationWnotifyWobjectivesWobtainedWWWWobtainsWoccurencesւWփWoctetWoctetsWofiWjWmWrWyW}W~WւWփWքW֍W֎W֏W֦WֱWִWֹWWWWWWWWWWWWWWWWWWWWWWWWWWWok֔WoldWWomittedW֗E Eric NJEDJOU^Technical, Binding_31`26a6.1.2cdThis is not absolutely true as link layer events consumers can be different from the network layers.d48vNo specific text proposedwRejected 2005/09/21 2005-09-14֘E Eric NJEDJOU^Technical, Binding_28`3a5.7.1d47wRejected 2005/09/21 2005-09-14֙E Eric NJEDJOU^Technical, Binding_33a6.1.3cxIt should be precised which context this figure holds to. Is for an 802.11 flow model? Why is MAC the L2 protocol used? d49j????vNo specific text proposedwRejected14 2005/09/21 2005-09-14֚E Eric NJEDJOU^Technical, Binding_33a6.1.3cCommand on the title below Figure 14:: This is only an example link event flow model. Other can exist The Link Event request has not been defined anywhere d50vNo specific text proposedwRejected14 2005/09/21 2005-09-14֛E Eric NJEDJOU^Technical, Binding_34`55a6.1.6vwithdrawn֔workցWworkwitheditorցVwacceptedւփaccepted-modifiedvy}ցrejectedoprstuwxz{|~քօֈ֊֌֍֎֏֐ְֲֳ֑֖֛֢֣֥֦֧֚֭֮֒֓֕֗֘֙֜֝֞֟֠֡֨֫֬֯Ńǃrejected-duplicatewithdrawnֱ֤֪֩€C^editorialփֆև։ƒ҃كeventWWWWWWWWWWWWWWindicateWinformationWisWWlinkWlistWlocalWmakeWmarkWmessageWmihWnewWWnon-bindingWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWofWorWparameterWWparametersWremoteWremoveWWrequestWWWWrequestthatanewparametertocarryabasicinformationelVrequestthatanewparametertoindicatethetypeofparametVrequesttoremovesection7.2.13and7.2.14andrespectiveeVrespectiveWWWsectionWWtableWWWtable-1WtablesWWWQjeventցWֹWeventsցWօWexchangeցWֶWexecution|Wexisting|WexperiencexWfallsָWֺWֽWfollowingyWforxWyW֏W֕WּW־Wframes֕W֖W֞WfunctionlWnWֶWֿWfunctioninstanceֿVfunctionalitiesjWfunctionslWgօWֶWgivenyWglobal֏WhandoverkWxWyW|W֬Whandover-enablinglWhandovers|WhasWրWhaveiWցW֠Wheterogeneous|Whigher։W֕W֞Whle։Whlmp։Whomogeneous|Whowever|WioWid֠WidentificationkWidentifier֠W֩W֪WַWidentifiers֤W֫Wids֤Wie֠WifyWցWimpossibleօWiniWnWxW|W}W֖WֱWּWincludesֿWWWindependentցW֟j"Complete reworking of this part...vNo specific text proposedwRejected 2005/09/21 2005-09-14֠E Eric NJEDJOU^Technical, Binding_42a6.3.2cSOperator IE: Network Identifier and Operator information element have to be mergedd56jmOperator IE: Network Identifier and Operator information element have to be merged. New name: Provider ID v/Defer to Information Element table redefinitionwRejected4 2005/09/21 2005-09-14֡E Eric NJEDJOU^Technical, Binding_46`25a6.3.3c"Already described in section 5.3.3d57vNo specific text proposedwRejected 2005/09/21 2005-09-14֢E Eric NJEDJOU^Technical, Binding_49`49a7.2d58wRejected 2005/09/21 2005-09-14֣E Eric NJEDJOU^Technical, Binding_55`12a7.2.7.1cKWhat does layer 2 mean? We need to be deeply accurate in this specificationd59vNo specific text proposedwRejected 2005/09/21 2005-09-14֤E Eric NJEDJOU4ckindֱWl2֙WWWl3Wl3mpmWւWփWքWlanguageWlastWlayerrW։W֗W֣WWWWWWWlayerspWWրWւWփWևW֗WWWleftWlengthWWlessWlevelrWlike|W֜W֝WWWlimitedWlinkpWrW֗W֚W֜W֝WWWWWWWWWWWWWWlinkeventhandoffxxxprimitivesaredefinedtoindicatethVlinkhandoffcompleteisthisalinkeventlookslikerather֝Vlinkhandoffimminentisthisalinkeventlookslikerather֜VlinksdutransmitxxxprimitivesareusedtonotifythetranVeedrWֆWneednotdetectionֆVneeds֕WnetworknWyW֗Wnew֔Wnewsentencesincethemaydraftok֔Vno}WnodeoWnotjWkWmWoWpWqWrW|W}WցWքWֆW֍W֎W֏W֓W֗W֚Wad‚b֛‚c֜‚d֝‚e֞‚f֟‚g֠‚h֡‚i֢‚j֣‚q֤‚r֥‚s֧‚t֦‚u֨‚v֩‚w֪‚x֫‚y֬‚z֭‚֮‚֯‚ְ‚ֱ‚ֲ‚ֳ‚ִ‚ֵ֤^Technical, Binding_55a7.2.7.1ceIn the table: MAcMobileTerminal: This implies that we identify every terminal with its MAC addressd60j@Need to agree on identifiers... (MIH IDs, Mobile Terminal IDs). w Withdrawn 2005/09/21 2005-09-14֥E Eric NJEDJOU^Technical, Binding_55a7.2.7.1ckIn the table: Mobility Management Protocol Support Type bitmap : Can't see how this parameter can be usedd61vNo specific text proposedwRejected 2005/09/21 2005-09-14֦E Eric NJEDJOU^Technical, Binding_73a 7.4.8.1.4c^In the table: can't see the purpose of having NETWORK_ID in the MIH_Configure primitive d63vNo specific text proposedwRejected 2005/09/21 2005-09-14֧E Eric NJEDJOU^Technical, Binding_70a 7.4.7.1.2crIn the table: Handover Mode: We always want make before break when possible. There is no point specifying thisd62vNo specific text proposedwRejected 2005/09/21 2005-09-14֨Kclinks|WWWlistWWlistsWllcrW֛WWlliWlocalWWlocate֏WWlocatedցWlocationքWWWlongzWlookWlooks֜W֝Wlower-layerWlsap֌WmaWmacrW֌W֙W֛W֤W֫WWWWWWWmacmobileterminal֤WmadeWmakewW}W֧W֬WWWWmanagementlWmWqWքW֎W֏W֥WmarkWmatterִWmattersrWmay֔WWWWWWmdiWWmeaingWmean֣WmeaningfulWWmeansWmechanismWWmediaWWWmediatypescolumnisnotmeaningfulthemediatypescolumnVVmedia-dependentWmedia-independentWmedia-independentinformationmdilinklayerinformationlliVmedia-specificWmeetingWmerged֠WWWmessageWWWWWWWWmodelsW'c802pW802.11ցWօW֙WWWWWW802.16WWWW802.21jWlWrWWWWWWWWWW802.21onlydefinesenablersformobilitymanagementprotocolV802.3W9W9.1W9.2W;cie֠WieeepWrWWWiesִWWietfpWrWif{W|W֬WWWWWWWifiwouldliketotransitionbetweentwolinksiwontuse|Vifthemihreferencemodelfor802.16isacceptedsection7ViiWiiiWillustratedWimminent{W֜WWimplies֤WimportantWWiniWnWyWzWցWօW֍W֎W֡W֣W֤W֥W֦W֧W֩W֪W֫W֬W֭W֮W֯WֹWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWnonthemihreferencemodeVinsection7.2.13and7.2.14sdurelatedeventservicesareVinsection7.2.157.2.167.2.17linkhandoverimminentindicVinthedraftallsuccessfulcasesareconsideredduringaliV֨E Eric NJEDJOU^Technical, Binding_74`14a7.4.9cl We already have MIH_Poll which does the same thing. We need to specify the difference between the two... d64vNo specific text proposedwRejected 2005/09/21 2005-09-14֩E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIn the table: Command Source : Defined as "Source Identifier" in other primitive description. Need to choose a single term. d65j%Source Identifier should be prefered.w Withdrawn 2005/09/21 2005-09-14֪E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIn the table: Command Destination : Defined as "Destination Identifier" in other primitive description. Need to choose a single term. d66j)Destination Identifier should be preferedw Withdrawn 2005/09/21 2005-09-14֫E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIIn the table: Suggested PoA identifier : No MAC address for cellular. d67j Work on defining identifiers...arcwhatdoweexactlydefinebyhandoversignalingisittheex{Vwhatdoeslayer2meanweneedtobedeeplyaccurateinthis֣Vwhatisnotclearinthisdescriptionistheclarificationo֍V֎VwhenpW֌W֧WWWWWWwhenmihscancommandisissuedtorequestscanningformultVwhereWwhetherWWքVwich֍WwillmWwWִWwirelineWwithnWWրWւWփWևW։W֤Wwithin}WWwon|WwordjWwould|WքWWWWWwrongvWyouwWd i0j@kPl`mpnqpo‚!r‚"s‚#t‚$u‚%v‚&w‚'x‚(y‚)z‚*{‚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֚‚bcbecauserW|W֟WWWbecausefigure26onlyreflectstheipv4caseitisnecessarVbeen}W֚WbeforewW֧W֬WWWbelongWbelongsWWbelow֚WbeneficialWbesides֌WWUOcprocessnWpropagateքWpropertiesWpropoertiesWproposalWWproposaltochangethepresentmihgeneralpacketformatsamVproposeWWproposedֹWּWWprotocollWqW֏W֙W֥WWprovideWWWWprovidingWpurpose֦WWWWpurposesWWqosWqueryWWWWWWWqueryfiltertypesWqueryingWWradioiWrateWrather֜W֝WִWrdfWrdf/xmlWreadsWrealisedWreasonWrecalledmWreceiptWreceivesWreducedWredundancyWredundantWWWrefereedWreferencepW֏WֹWּWWWWWWWWreferencesWreferringWreflectWWWreflectsWregardWregistrationWWscommentsVtVsap֌W֍W֎W֒WWWWWWsapsWW֫vNo specific text proposedwRejected 2005/09/21 2005-09-14֬E Eric NJEDJOU^Technical, Binding_74a 7.4.10.1.2cIn the table: Handover Mode : Again there is no point having this as a type. We do break before make only if we don't have other choice. d68jRemove Handover ModewRejected 2005/09/21 2005-09-14֭E Eric NJEDJOU^Technical, Binding_79`21a7.4.11.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d69vNo specific text proposedwRejected 2005/09/21 2005-09-14֮E Eric NJEDJOU^Technical, Binding_80`34a 7.4.11.1.4cCText is that same as in 7.4.10.2.4 (MIH_Handover_Initiate.response)d70vNo specific text proposedwRejected 2005/09/21 2005-09-14֯E Eric NJEDJOU^Technical, Binding_80`45a 7.4.11.2.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d71wRejected 2005/09/21 2005-09-14ְE Eric NJEDJOU^Technical, Binding_82>JcterminalnW֤WִWWWWterminal-centricWzW֭W֮W֯WWWWWWWWWtextisthatsameasin7.4.10.2mihhandoverinitiaterespo֭V֯Vtextisthatsameasin7.4.10.2.4mihhandoverinitiateres֮VthanWthatmWnWoWwW{W}W֟W֤W֭W֮W֯WִWWWWWWWWWWWWWWtheiWjWmWnWoWqWrWwWyWzW{W~WցWքWօW֌W֍W֎W֏W֔W֕W֗W֙W֚W֤W֥W֦W֧W֨W֩W֪W֫W֬WֱWִWֵWֹWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWjsourceidentifiershouldbeprefered֩Vspecification~Wspecified|WspecifyyWstackkWqW֏WstackslWօWstandardyW|Wstandards|Wstation֌Wstick֏WstoreiWsubnetoWsubsequent|WBjsourceidentifiershouldbeprefered@such@the@transport@vany@mentioned@nospecifictextproposed@notinupdatedtext@replaced@withdrawn@IZa7.4.7.1.2֧7.4.8.17.4.8.1.4֦7.4.9֨7.4.9.2.47.47.13.2.2dVdWtable-1table-5b0WW0successV1WWWW1authenticationfailV10W2WWWWWW2linksetuptimeoutV21-05-0348-01-0000WW21-05-0359-00-0000WW21-05-0361-00-0000WWWWWW21-05-0370-00-0000W22-43W3WWWWW37reservedV3.2W3gppWWW3gpp2WWW5.3.2W5.3.3W5.5.1W5.5.2W5.5.3W5.6WW5.6.1WW5.6.1mihmgmtsapVV5.6.2W5.6.3W5.6.4W5.6.5W5.6.6W5.6.76W5.6.87W5.6.9W5.6.98W6W6.3.1W6.3.1.1W7WWW7-11W7.1W7.2W7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.2.7WWib'cdestination֪Wdestination/sourceWdestructivenWdetailedWWWdetailsrWWdetailsofthemihcapabilitydiscoverwasleftoutasthepVdetectWWdetectedWdetectionֆWdeterminewW{WdevicesWdhcpWdiagramWWdifference֨WWWdifferentxWyW֗WWWWWdifferentiate֛WdifficultWdirectlyWWdiscoverWWdiscoveredWdiscoveringWdiscoveryWWdiscussesWdbyinformationVeWeachWeavesdroppedzWeciֵWelement֠WִWelsewhereWenablerslWenoughpWWentity։WequallyWequipementsִWes/csִWessentialmWethernetWevenzWքWevenaftersecureassociationtheeventscommandsandinformzVeventքW֚W֜W֝WWWeventszW֗W֛WWWWWevery֤Wexactly{Wִ 2005-09-14posedwRejected 2005/09/21 2005-09-141 2005-09-14ֱIH_Handover_Initiate.response)d71 2005/09/21 2005-09-14ְE Eric NJEDJOU^Technical, Binding_82`10a 7.4.12.1.1d72 2005/09/21 2005-09-14ֱ(MIH_Handover_Initiate.response)d71 2005/09/21 2005-09-14ְE Eric NJEDJOU^Technical, Binding_82`10a 7.4.12.1.1d72 2005/09/21 2005-09-14ֱ_Handover_Initiate.response)d71 2005/09/21 2005-09-14ְE Eric NJEDJOU^Technical, Binding_82`10a 7.4.12.1.1d72 2005/09/21 2005-09-14ֱc NJEDJOU^Technical, Binding_80`45a 7.4.11.2.1cAText is that same as in 7.4.10.2 (MIH_Handover_Initiate.response)d71 2005/09/21 2005-09-14ְE Eric NJEDJOU^Technical, Binding_82`10a 7.4.12.1.1d72 2005/09/21 2005-09-14ֱtiate.response)d71 2005/09/21 2005-09-14ְE Eric NJEDJOU^Technical, Binding_82`10a 7.4.12.1.1d72 2005/09/21 2005-09-14ֱ2ֵE Eric NJEDJOU^Technical, Binding_30a6.3cAThere is a need to add an Information Element set for User Equipements. The problem is that some IEs will not be carried by IS but rather by ES/CS. Some reorganisation of the document might be needed for that matter. Please see the attached doc "Terminal_IEs.doc"d76 2005/09/21 2005-09-14ֵE Eric NJEDJOU^Technical, Binding_30a6.doc"d76 2005/09/21 2005-09-14ֵE Eric NJEDJOU^Technical, Binding_30a6d76 2005/09/21 2005-09-14ֵE Eric NJEDJOU^Technical, Binding_30a6Information Element set for User Equipements. The problem is that some IEs will not be carried by IS but rather by ES/CS. Some reorganisation of the document might be needed for that matter. Please see the attached doc "Terminal_IEs.doc"d76 2005/09/21 2005-09-14ֵE Eric NJEDJOU^Technical, Binding_30a6`‚'ֱ‚(l‚)zօ‚1‚2֭‚3Ѓу‚5ֈ‚6֡‚7֔֗‚8ֆև‚A‚Brvփ‚C‚E֮֞‚Fs‚G֎‚H{|֋‚I‚J‚Qt֌‚RpӃ‚S҃‚U֐ك‚V֯‚Wր֍‚X‚Y‚Z֢Ã݃‚bx‚cֲ‚du֒‚en֕‚fq}֛Ƀ‚g‚h‚iiރ‚j‚q‚s֖Ã% a1W1.2ijklm1.3nq2W2.1p3orstuvֶַָֹֺֻּֽ־ֿW4WWWWWWWWWWWWWWWWWWWW6cabovemW֏Wabsolutely֗WacceptedWaccessWaccessrouterinfoWWaccordingWaccordingtodefinitionin7.2.12linkparameterschangeutiVaccordinglyWaccuratekWqW֣WacrossWactiveWadWWad-hocWadaptedpWaddִWֶWַWָWֺWֻWֽW־WֿWWWWWWWaddanewdefinitiontosection3ֶVַVָVֺVֻV־VֿVVVaddnewdefinitiontosection3ֽVaddedWWWWWWandzW֍W֎W֏W֠WֵWanotherRWbWgWanywhere֚WarchitecturejW}WarepW֏W֟WasOW_WdWmWrWsWtWzW}W֗W֩W֪W֬W֭W֮W֯Wassociated֌WassociationoWzWattachedִWֵWbasedxWbbbbbchbejWmWnWwWxWzW~WWրW֌W֕W֗W֙W֠W֣W֥WֱWִWL,cbecause@besidesmihmacsapthelsapcanalsobeusedtotransportp@captured@changed@2comment@currentsection5.3.3istooambiguous@idestination@discussion@beach@example@flavour@format@handoverandhandoffareusedtogetherinthedraftforcons@;ie@in5.6sapssuchasmihphysapmihllcsaparedescibedbut@inthetablecan'tseethepurposeofhavingnetworkidint@-information@it@kind@links@messages@Kthiscouldbeperformancedestructivefortheterminalince@toֶtobetakenoutofthespecification@updatereferencediagramanddescriptionfor802.16@%weshouldbecarefulonusingthewordarchitecture802.21d@whatdoweexactlydefinebyhandoversignalingisittheex@d‚b֛japplication/layer@connectivity@different@event@information@is@ ֵcA modification is suggested to section 6, by adding new primitives and by modifying certain definitions. Please see the attached doc, called New_ECI.docd77 2005/09/21 2005-09-14ֶEQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bA[The following new definition emphasizes the distinction between having an MIH function instance available and having the communication entity actually involved in MIH-related exchanges with the MIH function instance. For example, an 802.16 link endpoint that does not exchange MIH primitives with the local MIH Function instance is not MIH-active.[c!Add a new definition to section 3jAMIH-active entity -- A communication entity (e.g., a link endpoint or network node) that is configured to exchange MIH primitives with an MIH function instance. @A*  33  33* 2005/09/21 2005/09/14ַEQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3 [^bindingֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWchanged Wcurrent Wdevices W W Wdevices W Wices W Ws W Wvices W W W W W Wces W Wcurrent Wdecisions Wdetect Wdevices W Ws W Wes W Wdevices W Wces W WdirectionsWionsWWonsWWnsWWsWWtionsWWsWWWWnsWWsWWWionsWWWWWWectionsWWWWWWK.cmodificationֵWmodifyingֵWmore֕WWWWWWmsWmultipleւWփWWmustWWWWmyօWnameWnaturalWnecessarilyoWnecessaryWWneedrWֆW֣W֨W֩W֪WִWWWWWWWWWWWneeds֕WWWWWneighborWWneighboringWWWnetworknWyW֗W֠W֦WWWWWnetworksWnew֔WֵWֶWַWָWֺWֻWֽW־WֿWWWWWnewsentencesincethemaydraftok֔Vno}W֧W֫W֬WWWWnoneedtohavesuchadescriptiveintroductioninsection6VnodeoWּWnotjWkWmWoWpWqWrW|W}WցWքWֆW֍W֎W֏W֓W֗W֚W֟WִWWWWWWWWWWWWWWWWWWWW,g AS T3C|U#3}C<V#3ACWDFdVX^H7UaY TZbh[FXVt \_BlHUS]FV ^`lHoU_FV`alHPUaWTbcKX6c3IC dd5BDe5BfyxdasÃăgroetingƃǃguptaɃʃ˃̃̓΃σЃу҃ӃԃՃkim׃؃كڃۃ܃݃ރ߃kohleeohbasreemanthulaxie^rameterqueryresourcelistintomihhandove V V V V V V V VV V V V Ve V Ve V Ve V VaddedWWWWformiheventsorlistmiheventsinthetaddedWWWWWWWWWWW}W~WWրWցWւWփWքWօWֆWևWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֡W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭W֮W֯WְWֱWֲWֳWִWrandreaֶWַWָWֹWֺWֻWּWֽW־WֿWWWbenjaminpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWրWցWւWփWքWօWֆWևWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֡W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭W֮W֯WְWֱWֲWֳWִWֵWericnjedjouiVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVրVցVւVփVքVօVֆVևVֈV։V֊V֋V֌V֍V֎V֏V֐V֑V֒V֓V֔V֕V֖V֗V֘V֙V֚V֛V֜V֝V֞V֟V֠V֡V֢V֣V֤V֥V֦V֧V֨V֩V֪V֫V֬V֭V֮V֯VְVֱVֲVֳVִVֵVYbfollowingֶWַWָWֻWּWֽW־WֿWWWWWWWWWWfollwingֺWforֶWWWWWWWWWWWWWWWWWWWWWWWWforneighborreportiesremovemeasurementreportfromthedVformatWWWWframeWframesWframeworkWWWfreeWfromWWWWWWWWWWWWWWWfunctionֶWWWWWWWWWWfunctionalityWWfunctionalpropertyWfunctionsWfunctonWgWWWWWgeneratedWWWgenericWWgeo-coordinateWWgeographicWgeographicalWgivenWgoingWgraphicalWgvenWhandWhandlingWhandoffWWWWWWWWWWWW:ctoֶWַWָWֹWֺWֻWּWֽW־WֿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWcaddingֵWadditionWWWadditionalWaddress֤W֫WWWWaddsWadedWadoptedWadvertisementWadvertismentWafterzWagainqWօW։W֬Wagainreplacewithhlehigherlayerentity։Vagainwhatpreventfromusingmy802.11interfacetotalktoօVagentքWWaimsWairzWalined֏Walink֜W֝WallWWWWWusagedefinedinthissectionaVallowWWalready|W֟W֡W֨WWWWalreadydescribedinsection5.3.3֡ValsoiW֌WWWalwaysmWzW֧WambiguousWWamongWanjWrWցWօW֙W֚W֜W֝WִWWandzW֍W֎W֏W֠WֵWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWjmih-activeentityacommunicationentityegalinkendpointֶVmnnWqWmobileiWnW|WօW֤WֹWּWֽWmobilenodenetworknodethatcanchangepointofattachmentּVmobile-nodeֹWmobilitymWqW։Wmobility-managementkWlWmode֬Wmodel֏WmorepWmostxWyWmotorola}Wname֠WneedֆW֤Wneedtoagreeonidentifiersmihidsmobileterminalids֤Vneeds֖WjconnectivityvWcontinuousyWcontinuouslynWcostyWcreationlWcriteriayWcurrentlyyWdata֕W֖WdefinepWdefineamoreappropriateterminologypVdefinedֺWdefining֫WdefinitionvWyWdeletedֱWdestination֪Wdestinationidentifiershouldbeprefered֪VdetectedvWdetectionֆWdeterminevWdevicesiW ַbAdopt the following new textc!Add a new definition to section 3iAndrea, Pererz, QiaobingjALink endpoint -- Link termination associated with a link-layer identifier, which is unique within the applicable operation scope. @A*  33  33* 2005/09/21 2005/09/14ָEQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textc!Add a new definition to section 3iAndrea, Pererz, QiaobingjATMIH Link Endpoint -- MIH-active endpoint of a link that falls within 802.21 scope. T@A*  33  33* 2005/09/21 2005/09/14ֹEQiaobing, Andrea, Peretz, Ajay^Technical, Binding_6a3b  PֹbAThe new Point of Attachment definition replaces current definition - Network Point of Attachment. It defines the point of attachment independently of the MIH capabilities of the link endpoint. The "with at least one mobile-node termination" is required by the sentence in the link definition that says: "each link is associated with a minimum of two endpoints". Since a link may have more than two endpoints, there can be more than one Mobile Node attached to the link that includes the poinBt of attachment. @A>  33  33  33>cApClarify Point of attachment in section 3. Required to further clarify the proposed communication reference modelp@A>  33  33  33>iAndrea, Pererz, Qiaobingj  ֹjAVPoint of Attachment -- Network-side endpoint of a link with at least one mobile-node termination. Serving Point of Attachment The point of attachment of the mobile node prior to a potential link-switch event. Target Point of Attachment The point of attachment of the mobile node that may result when a link-switch event takes place. V@A*  33  33* 2005/09/21 2005/09/14ֺEQiaobing Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the follwing textc!Add a new definition to section 3iAndrea, Pererz, QiaobingjAMIH Point of Attachment -- MIH-active point of attachment on a link that falls within 802.21 scope. Also defined as a network-side MIH link endpoint. @A*  33  33* 2005/09/21 2005/09/14ֻEQiaobing, Andrea, Ajay, Peretz^Technical, Binding_6a3bAdopt the following textc!Add a new definition to section 3YbinstanceֶWWinsteadWintegerWintelligentWinterchangeWinterchangetransactionidandmihfunctionidlengthpositiVinterfaceWWinterfacesWinterfacingWinterferenceWinternationalizationWinterruptedWinterworkingWintoWWintroducedWWinvolvedֶWirrespectiveWisֶWֹWּWWWWWWWWWWWWWWWWWissuedWWWitֹWWWWWkWkeyWknowledgeWl2Wl3Wl3mpWlacWWlanguageWlayerWWWWWWWWWWWWWlayersWWWWleastֹWlengthWWlikelyWWlineWWWWWline10WlinesWWlinkֶWֹWWWWWWWWWWWWWWWtbterminationֹWtextַWָWֺWֻWֽW־WֿWWWWWWWWWWWWWWWWWWWWWthanֹWthatֶWֹWWWWWWWWWWWtheֶWַWָWֹWֺWֻWּWֽW־WֿWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWthefollowingnewdefinitioncoversthecasewherethemobilּVthefollowingnewdefinitionemphasizesthedistinctionbetwֶVthenewpointofattachmentdefinitionreplacescurrentdefiֹVthe11thWtheirWthemWthenWthereֹWWWthereare3waystosolvethisVtheseWWWtheyWthingWW(jmih-activeֶWָWֺWֽW ֻiAndrea, Pererz, QiaobingjAENetwork Node -- Collection of physically collocated link endpoints. E@A*  33   33* 2005/09/21 2005/09/14ּEQiaobing, Andrea, Ajay, Peretz^Technical, Binding_6a3bThe following new definition covers the case where the Mobile Node is capable of maintaining multiple links simultaneously active.cAhClarify Mobile Node in section 3. Required to further clarify the proposed communication reference modelh@A>  33  33  33>jAMobile Node -- Network node that can change point of attachment for at least one of its links at any time. The mobile node can either be in close proximity of or coincide with the mobile terminal. @A*  33   33* 2005/09/21 2005/09/14ֽEQiaobing, Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textjlistsiWlocalցWlocationiWlowerqWlsap֌Wmac֌WmadeyWmaintainxWmake|WmanagementmWqW֕W֞WmapvWmayyW|W֕W֞WֹWmeansyWmechanisms|WmediaցWօWmerged֠WmihlWmWnW֌W֖W֤WֱWֶWָWֺWֽWֿWWmihinfrastructurenodeinfrastructurenodethatincludesanֿVmihlinkendpointmih-activeendpointofalinkthatfallswָVmihmobilenodemobilenodewithatleastonemih-activeendֽVmihnetworkaddressinformationshouldbedeletedandtheinֱVmihnodeofattachmentmihinfrastructurenodethatincludesVmihpointofattachmentmih-activepointofattachmentonaֺV@jlists@mih-active@mih-activeentityacommunicationentityegalinkendpoint@neighborhood@onemihpointofattachment@original@originaltextanarchitecturethatenables@originaltextthearchitecturereliesontheidentification@overall@radio@joriginaliWjWkWlWnWoWqW|WցWօW֌W֕W֖W֞Woriginaltextasetofhandover-enablingfunctionswithinthlVֽcAdd new definition to section 3jAoMIH Mobile Node -- Mobile node with at least one MIH-active endpoint on a link that falls within 802.21 scope. o@A*  33  33* 2005/09/21 2005/09/14־EQiaobing, Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textc!Add a new definition to section 3jAqInfrastructure Node -- Network node that cannot perform any kind of automated link switch for any of its links. q@A*  33  33* 2005/09/21 2005/09/14ֿEQiaobing, Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following textc!Add a new definition to section 3jAXMIH Infrastructure Node -- Infrastructure node that includes an MIH function instance. X@A*  33  33* 2005/09/21 2005/09/14EQiaobing ,Pererz, Andrea, Ajay^Technical, Binding_6a3bAdopt the following text ericiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WWրWցWւWփWքWօWֆWևWֈW։W֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֡W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭W֮W֯WְWֱWֲWֳWִWֵWericnjedjouiVjVkVlVmVnVoVpVqVrVsVtVuVvVwVxVyVzV{V|V}V~VVրVցVւVփVքVօVֆVևVֈV։V֊V֋V֌V֍V֎V֏V֐V֑V֒V֓V֔V֕V֖V֗V֘V֙V֚V֛V֜V֝V֞V֟V֠V֡V֢V֣V֤V֥V֦V֧V֨V֩V֪V֫V֬V֭V֮V֯VְVֱVֲVֳVִVֵVfederWjin bC8ocument number 21-05-0348-01-0000_Higher_layer_IS.doc] cDNo need to have such a descriptive introduction in Section 6.3.1, v5Resubmit after addressing comments from the discusson 2005/09/21ESubirFDas^Technical, Non-bindingbsInclude the text and figure from Section 3 of document number 21-05-0348-01-0000_Higher_layer_IS.doc to Annex ZZ. cHInclude the Information Service Use Case Scenarios as informative text v5Resubmit after addressing comments from the discusson 2005/09/216. 3.2 ). Information Elements provide information that is essential for a handover module to make intelligent handover decision. Depending upon the type of mobility support and use case scenarios, different types of information elements may be necessary for perfroming handovers. Such case scenarios are described in Annex YY and following subsection describes the reference model of MIIS. 6.3.1.1 MIIS Reference Model [nsert the text from Section 2 of dESubirFDasvEmptywRejected 2005/09/21EWolfgangFGroeting^Technical, Non-binding_120`30a8.3.1b- Interchange Transaction ID and MIH Function ID Length positions - Interchange MIH Function Identifiers with MIH Message ID cAProposal to change the present MIH General Packet Format (same applies for the MIIS packet format) - Use fixed header instead of variable header to avoid scheduling problems - Locate variable MIH Func. Destination/Source Identifier before MIH Message data - Change MIH Function Identifier Length from 4 octets to 1 octet - Unusual that MIH Function ID Length value > 255 -Examples: MAC address = 6, IPv4 = 4, IPv6 = 16 - Change Transaction ID from 1 octet to 4 octets - TransactionBls IDs do have a value greater than 255 - Examples: IP - packet ID = 2 bytes; TCP - sequence no. = 4 bytes ZvTo be resolved later 2005/09/2127 bAMove the introductory text and figure of section 6.3.1 to Annex XX. Include the following text in Section 6.3.1 instead. Media Independent Information Service (MIIS) provides a framework by which a MIH Function (Media Independent Handover Function) both in the mobile node (a.k.a UE or STA) and in the network can discover and obtain information of homogeneous or heterogeneous network within a geographical area to facilitate the handovers. MIIS includes support for various InformatBion Elements (IEs) (Section 6. 3.2 ). Information Elements provide information that is essential for a handover module to make intelligent handover decision. Depending upon the type of mobility support and use case scenarios, different types of information elements may be necessary for perfroming handovers. Such case scenarios are described in Annex YY and following subsection describes the reference model of MIIS. 6.3.1.1 MIIS Reference Model [nsert the text from Section 2 of dz8~bdecisionWdecisionsWdefineWWWdefinedWWWWWWWWWdeleteanexdVdeleteentriesforeventidentifiers7-11fromthetabledelVdeletelines22-43descriptionoflinksynchronouseventsanVdependingWdependsWdescribedWdescribesWdescriptionWWWWdifferenceWdifferentWWdiscoverWdistinctionֶWdnamicWdocWWdocumentWWdoesֶWdomainWdraftWdynamicWeWeachֹWWeitherWeitherdeletethefigure10ormodifyforconsistencyVelementsWWemphasizesֶWencapsulatesWencapsulatingWendpointֶWֹWendpointsֹWentitiesWentityֶWentriesWessentialWeventWeventsWWexampleֶWexchangeֶWexchangesֶWfacilitateWfailWfigWfigureWWWW bsuchWWWWWsupplementWWWsupportWWsupportedWWWWWsupportedcommandlistWsupportedeventlistWsupportsWsupposedWWswitchWsymmetryWsynchronousWsystemWWsystemsWtableWWWWWWWWWWWWWtable-1WtablesWWWWWWWtcp/ipWtechnologiesWtechnologyWterminalWWWObsubsectionWWWsubsequentWWsuccessWWngbreferenceWWWWregisterWWregisteringWregistrationWrelatedWWWrelationsWrelationshipWrelationshipsWremedyWWWWremoteWWremoveWWWWWWWWWWWWWWWremoveannexc2entirelyVremoveannexc3entirelyVremoveannexc4entirelyVremovefigure22Vremovemihmgmtsapfrom3gppreferencemodelVremovemihmgmtsapfrom3gpp2referencemodelVremovetable6Vremovetable7Vremovetextstartingatline20ofpage87andendingatlinVreorganizeWreorganizesapsinsection7basedonrevisedsapdefinitionVreplaceWWWWWWWWWWWWWWWWWWWreplace6.1.5primitivesforlinklayereventsby6.1.5primVhdcVreplacesֹWreportWWsubsectionEWolfgangFGroetingvEmptywRejected 2005/09/21EWolfgangFGroetingvEmptywRejected 2005/09/21EVivekFGupta^Technical, Non-binding_15`55a5.3.2bASReplace current section 5.3.2 by the section 5.3.2 in DCN # 21-05-0361-00-0000 " S@A>  7  O  >cThis is to add information about a general Communication Model and the specific interfaces/reference points within scope of IEEE 802.21 for the various services.wRejected-Duplicate 2005/09/21EVivekFGupta^Technical, Non-binding_16`11a5.3.3b bCEe with other MIH Functions in the network which may provide Information Service function or MIH Controller type functionality. This communication may typically occur over L3. The MIH Function on the terminal can communicate with multiple such MIH Functions in different networks using different available access networks. " !@A*  33&  33*c(Current section 5.3.3 is too ambiguous. vTo be resolved later 2005/09/2110EVivekFGupta^ Technical_19`62a5.5.1bVReplace section 5.5.1 with section 5.5.1 in contribution with DCN # 21-05-0361-00-0000cLUpdate the reference model for ethernet and make the description more clear.wAccepted 2005/09/21 bAReplace section 5.3.3 with text below. The relationships between different peer MIH Function entities depends on the specifics of interworking scenario between different access networks. " The MIH Function in the terminal communicates with one and only one MIH Function in the PoA for a single access network. This is true for both L2 and L3 mode of transport " The MIH Function in the PoA of a gven access network may communicate with other MIH Functions in the same or different networks.B However this communication is not visible to the MIH Function within the terminal. " In case of multiple active links supported through multiple access networks, the MIH Function in the terminal may communicate with one MIH Function for each access network (or a single MIH Function across multiple access networks when applicable, e.g. L3 transport in tight coupling scenarios where one MIH Function may serve multiple accesses in a domain). " The MIH Function in the terminal may communicat$2EVivekFGupta^ Technical_20`45a5.5.2bAVReplace section 5.5.2 with section 5.5.2 in contribution with DCN # 21-05-0361-00-0000V@A  33c@Update the reference model for 802.11 and associated description 2005/09/21EVivekFGupta^ Technical_21 with section 5.5.2 in contribution with DCN # 21-05-0361-00-0000V@A  33c@Update the reference model for 802.11 and associated description 2005/09/21EVivekFGupta^ Technical_215.5.1 with section 5.5.1 in contribution with DCN # 21-05-0361-00-0000cLUpdate the reference model for ethernet and make the description more clear. 2005/09/21EVivekFGupta^ Technical_20`45a5.5.2bAVReplace section 5.5.2 with section 5.5.2 in contribution with DCN # 21-05-0361-00-0000V@A  33c@Update the reference model for 802.11 and associated description 2005/09/21EVivekFGupta^ Technical_21ubonWWWWWWWWon-goingWoneֹWWWWWWWWoneofWWWWWWWorderWoriginatedWWoriginationWotherWWWWWoverWpageWWWparameterWWWWWWWWparametersWWpartWWpartnersWpassedWWpathWpayloadsWpeerWWperformWperfromingWphyWWphysWphysicalWplaneWplusWpoaWWWWWpoasWpointֹWWWpositionsWpppWWprepareWprimarilyWprimitiveWWprimitivesֶWWWWWWWprocedureWprocessWWWpropertiesWWprotocolWprovideWWWprovidedWprovidesWpurposesWqosWWqueriesWqueryWtS)btransportWWWtransportlayertrueWtwoֹWWWWWtypeWWWWWWWWWWWWWWWtypesWtypicallyWWWWtypingWuamWueWunauthenticatedWunderWunidirectionalWunitWunlikeWunsignedintWunsignedshortWupWupdatedWuponWWupperWWWWWWurisWurlWWWusageWuseWWWWusedWWWWWusefulWuserWusersWusesWWusingWWWWusngWvalidWvalidateWvalueWWWWvalueoflinkWvalueoflinkparameterWW5.3.3֡WW5.6W6ֵWW6.2.5.1֟W6.3.1W7W7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.4.10.2֭W֯W7.4.10.2.4֮WBFbactiveּWWWactuallyֶWaddWWWWWWWaddanoptionalparameterqueryresourcelistintomihhandoveVaddanothertableformiheventsorlistmiheventsinthetVaddedWWWWadditionalWadditionsWaddressWWWaddsWadoptַWָWֺWֻWֽW־WֿWWWWWWWadoptremedy5inthecontributiondcn21-05-0359-00-0000VxWannexWWapplicableWappliedWareWWWWareaWasWWassociatedֹWatֹWWattachedֹWattachmentֹWauthenticationWWavailableֶWWbasedWWbeֹWWWWbelowWWbetweenֶWWWWWbitmapWWbothWWbyֹWWWWWcWWcachingWcanֹWWWWcannotWcapabilitiesֹWcapableּWW{OcsecurezWsee֥W֦WִWֵWWseemWselectingWselectionxWyWselectsWsendingWsense}Wsentence֔WseparateWsequenceWserveWserviceֱWWWWWservicesWWWsetjWִWWWWWWWWWWWWWWWshoulddifferentiatephymacllcrlcevents֛VshowmWWshownWsignaling{WsimilarWsince֔WWWsincemihnetworkaddressinformationresponsecancarryrouVsinglerW֩W֪WsitsmWslalistWsmeWWsomWnW֓WWsome֟WֱWִWWWsource֩WspecificuW֍W֎W֖WWWWspecifictoonetechnology֖Vspecification~W֣WspecifiedWspecify֨WWspecifying֧WspeedWstackqWrWstandardWWstandardsWstateWstaticWstepoWW&`56a5.5.3bVReplace section 5.5.3 with section 5.5.3 in contribution with DCN # 21-05-0361-00-0000c3Update Reference diagram and description for 802.16 2005/09/21EVivekFGupta^ Technical_25`141a5.6bFReplace Fig 9 with Fig 9 in contribution with DCN # 21-05-0361-00-0000cGUpdate Fig 9 based on changes in Reference models for 802.11 and 802.16 2005/09/21Fig 9EVivekFGupta^ Technical_25`34a5.6bAReplace section 5.6 with section 5.6 in contribution with DCN # 21-05-0361-00-0000 ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description ---------------------------------------------------------------------------------------------Ucupdatereferencediagramanddescriptionfor802.16Vupdatethereferencemodelfor802.11andassociateddescripVupdatethereferencemodelforethernetandmakethedescripVupdatethesectionbasedonchangestosapsandreferencemoVupdatedWWWupperWրWւWփWևWWurlWusageWuse|WցW֍WWWWWWused֌W֍W֎W֒W֙W֥WWWWWWusefulWWWWWWWWuserִWWusesWusingjWօWWkparameterWvaluesWvariableWvariousWWWversionWveryWWWviewքWviewsrWvisibilityiWvocabularypWwantքW֧WwasWWWWwejWrW{W֣W֤W֧W֨W֬WWWWWwealreadyhavemihpollwhichdoesthesamething֨Vweneedtospecifythedifferencebetweenthetwo֨V$' bB------------------------------------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- Result | BITMAP | Indicates the result of Link setup process. C | | 0: Success | | 1: Authentication Fail | | 2: Link setup timeout | | 3~7: Reserved ---------------------------------------------&) bDs------------------------------------------------------------------------------------------------------------------ =@Az  33R  S  +      zc?Update the section based on changes to SAPs and reference model 2005/09/21Fig 10EVivekFGupta^Technical, Non-binding_31`22a6.1.2bAWDelete lines 22-43. Description of Link Synchronous Events and Link Transmission EventsW@A  cThe definition of these type of events is not clear and these events are not well defined in the draft. This just adds to confusion. 2005/09/21EVivekFGupta^Technical, Non-binding_35`22aTable-1b9blinksּWWWWlistWWlistedWWlistsWliteralWllcWlocalֶWWWlocationWWWWlongitudeWloresWlowerWWmWWWmacWWWmacmobileWmacsWmainWmaintainingּWmakeWWWWWmakethefollowingtextchangeVVmanagementWWWWWmanyWmarkWmaxcardinalityWmaximumWmaxinclusiveWmayֹWWWWWWWWWWWWmdiWWWmeaningWion6.3.1toanVmsecsWmultipleּWWnameWWnecessaryWneighborWnetworkֹWWWWWWnetworksWWnewֶWַWֹWּWnodeֹWּWWnotֶWWnsertWnumberWWobtainWoccurWofֹWּWWWWWWWW'* bADelete entries for Event Identifiers 7-11 from the table. Delete all subsequent reference to these events from all other corresponding sections of the draft ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description ------------------B---------------------------------------------------------------------------------------------------------------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- TimeDifference | Time in msecs )+ bC | When a PoA encapsulates Agent Advertisement | | or Router Advertisement in Network Address | | Information parameter, this parameter is time | | difference between the time of caching the D | | information and the time of encapsulating the | | information ---------------------------------------------------------------------------------------------------------------------------------------------------------------TAR  33  33  v  R*. b@AR  33  33  v  RcIt's not clear why these events are needed. They are not very useful in the generic handover case. In some cases the functionality specified by some of these events is already covered by other primitives. 2005/09/21EVivekFGupta^ Editorial_144`42aAnnex DbA Delete Anex D @A  cAnnex D contents are captured by other independent documents and it is difficult to keep the draft and those documents in synch. Besides those documents would be submitted independently to other standard groups. We dont need this info in 802.21 draft. 2005/09/2126EVivekFGupta^ Technical_42`41aTable-5b{cannexWannexdcontentsarecapturedbyotherindependentdocumentsVanotherWWWanyWnywhere֚WappliedWappliesWWapplyWWarchitecturejW}WarepW֏W֟WWWWWWWWWWWWWarqWasmWrWsWtWzW}W֗W֩W֪W֬W֭W֮W֯WWWWWWWWWWWWWasnWWassociated֌WWassociationoWzWatWattachedִWֵWattachmentֹWautomaticallyWavailableWavoidWbasedxWWWbasicWWWWWWWWWbejWmWnWwWxWzW~WWրW֌W֕W֗W֙W֠W֣W֥WֱWִWWWWWWWWWWWWWWWWWWWWWWWWWWWWWMcinthetablecan'tseethepurposeofhavingnetworkidint֦Vinthetablecommanddestinationdefinedasdestinationiden֪Vinthetablecommandsourcedefinedassourceidentifierin֩Vinthetablehandovermodeagainthereisnopointhavingth֬Vinthetablehandovermodewealwayswantmakebeforebreak֧Vinthetablemacmobileterminalthisimpliesthatweidentify֤Vinthetablemobilitymanagementprotocolsupporttypebitma֥Vinthetablesuggestedpoaidentifiernomacaddressforcel֫VincludeWWWincludetheinformationserviceusecasescenariosasinformVincludedWWincludingWWincorrectWincorrectlyWindependentWindependentlyWindicateWindicatesWWindicationWWinfoWW+1 bA For Neighbor Report IEs: remove measurement report from the description column. Measurement reports carry dynamic data and hence cannot be satisfied by Information Service For QoS: The elements listed in Comments column are dnamic values and cannot be supported be Information Service.@A  33cCDynamically changing IEs cannot be supported by Information Service 2005/09/21EVivekFGupta^ Technical_23`1a5.5.4b-Remove MIH_MGMT_SAP from 3GPP Reference ModelcMIH_MGMT_SAP is not defined 2005/09/21Figure 7EVivekFGupta^ Technical_24`1a5.5.5b.Remove MIH_MGMT_SAP from 3GPP2 Reference ModelcMIH_MGMT_SAP is not defined 2005/09/21Figure 8EVivekFGupta^ Technical_49`31a7)breportsWrepositoryWrepresentWrepresentationWrepresentedWrepresentsWreprovisionWrequestWWWWWWWWWWWWrequestthatanewparametertocarryabasicinformationelVrequestthatanewparametertoindicatethetypeofparametVrequesttoreconsidertheusecasesformihnetworkinformatVrequesttoremovesection7.2.13and7.2.14andrespectiveeVrequesttoremovesection7.2.157.2.16and7.2.17andrespeVresultsWretrievedWrevisedWrfcWricherWrightWroamingWWroaming-parnersWrouterWWrowWrrcWWsameWWsapWWWWWsapsWWsatisfiedWsaysֹWscalabilityWscanWscanningWscenarioWscenariosWWWschemaWWWschema-basedWschemalocationWscopeWWmnbcarryWWWcaseּWWWWcasesWWcategoriesWcellWchangeWWWWchangeallhandofftohandoverinthedraftVchangedWWcharacteristicsWWchoiceWchooseWclarifyWclassWWclassesWWclassifiedWclearlyWcmdWcodeWcollectionWcolumnWWWWcommandWWWWWcommanddestinationcommandinformationseWcommandresultsetWcommandsWWcommandsourceWcommandxxWcommentWWcomment9.1needtoverifyifhandovercommitisnotoverlapVcommentsWcommitWcommunicateWWcommunicatesWcommunicationֶWWWcompanionWcompatibilityWcomplementWcompleteWWcouplingWcoversּWcurrentֹWWWcurrentlinkidentifiecurrentlyWdWd00-02WW.3bReorganize SAPs in section 7 based on revised SAP definitions in section 5.6. Media Specific SAPs MIH_LINK_SAP C_SAP M_SAP MIH_RRC_SAP MIH_PPP_SAP MIH_LAC_SAP Network management SAPs MIH_SME_SAP Media Independent SAPs MIH_SAP cHMIH_MGMT_SAP is not defined and the overall SAP organization has changed 2005/09/21ERonnyFKim^Technical, Non-binding_20`1a5.5.3bAKAdopt the remedy 1 and 2 in the contribution " DCN # 21-05-0359-00-0000 " K@A>  33/  33G  33>cAIn order to reflect the discussion on the MIH reference model for 802.16 during Ad Hoc teleconference, it is necessary to change the figure as suggested in the contribution " DCN # 21-05-0359-00-0000 ". @A>  33  33  33> 2005/09/216ERonnyFKim^Technical, Non-binding_26`1a5.6bqcchangedWWWWchangesWWchangingWcheckWchoice֬Wchoose֩W֪WclairzWclarification֍W֎WclarifyֹWּWclarifymobilenodeinsection3requiredtofurtherclarifyּVclarifypointofattachmentinsection3requiredtofurtherֹVclassification֟WclassifiedWclear֍W֎WWWWWWWWclearlymWWcolumnWWWcommand֚W֩W֪WWWWWcommandonthetitlebelowfigure14thisisonlyanexample֚VcommandszW֟WWWW14 bAEither delete the figure 10 or modify for consistency; Make the following text change; 5.6.1 MIH_MGMT_SAP This SAP is defined in 802.11, 3GPP, 3GPP2. This defines the interface between the MIH Function layer and the management plane of different networks. This SAP can be used for sending MIH messages between MIH Function and local link layer entities as well as between peer MIH Function entities. Messages based on management frames can be sent in the unauthenticated state as well. BThe MIH_MGMT_SAP defines primitives for MIES, MICS and MIIS. 5.6.2 MIH_SME_SAP This SAP is defined in 802.11. This SAP defines the interface between MIH Function layer and the Station Management Entity or the Network Management System. This SAP defines the MIH interface with the system and is used for MIH configuration and operation. 5.6.3 MIH_SAP This SAP defines the interface between MIH and a L3MP, or a Handover Function MIH users which might reside at higher layer or a higher layer T35 bCransport as well. The interface between MIH and higher layers is a local interface which may depend on the choice of L3MP as well. The methods and other messages defined by this SAP result in local communication between peer layer entities. Definition of this SAP is required to define the scope and functionality of MIH Function. 5.6.4 MIH_MAC_SAP This SAP is defined in 802.3, and 802.11. This SAP defines the interface between MIH Functon and media specific MAC. The interfaces defined by Dthis SAP are primarily used to transfer data (MSDUs) between peer entities. No new interfaces and primitives need to be defined for this SAP. The interfaces defined by this SAP can be used to deliver MIH protocol based payloads to peer MIH entities usng the data plane. 5.6.5 MIH_PHY_SAP This SAP defines the direct interface between MIH Function and the media specific PHY. The MIH Function shall communicate with different media specific PHYs using the media specific MACs. There are no ne46 bEw primitives to be defined as part of this SAP. 5.6.6 MIH_LLC_SAP This defines the LLC interface to MIH. The MIH can directly use the existing LLC primitives to initiate connections and communicate with peer LLC entities and thus establish data path for sending MSDUs across different links. There are no new primitives to be defined as part of this SAP. 5.6.76 MIH_RRC_SAP This SAP is defined in 3GPP. This defines the interface between the MIH Function and RRC. 5.6.87 MIH_PPP_SAP This SAPF is defined in 3GPP2. This defines the interface between the MIH Function and PPP. 5.6.98 MIH_LAC_SAP This SAP is defined in 3GPP2. This defines the interface between the MIH Function and LAC. 5.6.9 M_SAP (Management SAP) This SAP is defined for management purposes in 802.16 and can be extended to define the interface between MIH Function and Management Entity. 5.6.9 C_SAP (Control SAP) This SAP is defined for control purposes in 802.16 and can be extended to define the interface betw57 bG)een MIH Function and Management Entity.  @A.  33X  33m    33  33    33>  ]  33    33    33     33}    33    33:  d  33    33   B 33 !  "  #  33 0  M  33       33     33       33   +  33 h    33   0  33 1    33c6< cAXIn 5.6, SAPs such as MIH_PHY_SAP, MIH_LLC_SAP are descibed but elsewhere they are not illustrated or defined. Some of SAPs only apply to some media specific type, e.g., MIH_SME_SAP only applies to 802.11, MIH_MAC_SAP applies to 802.3 and 11 only. For consistency, it is required to specify which SAP belong to which media specific interface. X 2005/09/2110ERonnyFKim^ Editorial_13`44a5.1.9b1change all "handoff" to "handover" in the draft. ci"Handover" and "Handoff" are used together in the draft. For consistency, use one term for same meaing.  2005/09/21ERonnyFKim^Technical, Non-binding_49`36a7.1, 7.2b:bdefinesֹWWWWdefiningWdefinitionֶWֹWּWWWdefinitionsWWdeleteWWWWWWdeleteanexdVdeleteentriesforeventidentifiers7-11fromthetabledelVdeletelines22-43descriptionoflinksynchronouseventsanVdeletesection7.2.13or7.2.14oraddmorehandoverrelatedVdeletesection7.2.157.2.167.2.17oraddmoretexttoclarVdeliverWdenyWdependWWdoesֶWdomainWdraftWdynamicWeWeachֹWWeitherWeitherdeletethefigure10ormodifyforconsistencyVelementsWWemphasizesֶWencapsulatesWencapsulatingWendpointֶWֹWendpointsֹWentitiesWWentityֶWWentriesWessentialWeventWeventsWWexampleֶWexchangeֶWexchangesֶWfacilitateWfailWfigWfigureWWWW(bmeasurementWmediaWWWWWWWmedia-dependentWWmedia-dependent-infoWmedia-independentWWmedia-independent-inWmedia-specificWmergeWWesWWmightWmihֶWֹWWWWWWWWWWWWWWWWWWWmihhandoverprepareresponseVmih-activeֶWmih-relatedֶWmihfWWmiiWmiisWWWWminimumֹWmobileֹWּWWWmobile-nodeֹWmobilityWmodeWmodelWWWWWmodifyWWWWmodifythefollowingtextVmodifythetextpage74line13Vmodifythe11throwintable14asindicatedbelowVmoduleWmoreֹWWWWmostWWmostlyWmoveWmovetheintroductorytextandfigureofsection6.3.1toanVmsdusWmsecsWWWWW8~LbdependingWWdependsWdescribeWdescribedWWWWWWdescribesWWWdescribingWdescriptionWWWWWWWWWdescriptionsWdestinationWdetailedWdetectWdetermineWdevicesWdhcpWWdiscoverWWWWdiscoveredWdistinctionֶWdnamicWdoWWdocWWWWdocumentWWdoesֶWdomainWdownWdraftWWduringWWdynamicWeWWWeachֹWWWWWeditorWeitherWWeitherdeletethefigure10ormodifyforconsistencyVelementWelementsWWWWemphasizesֶWencapsulatesWWencapsulatingWWendpointֶWֹWendpointsֹWenhancementsWentitiesWWWWWWentityֶWWWWWWWXchandoverandhandoffareusedtogetherinthedraftforconsVhandoversWhareWhasoWxW}WWրW֚WWWWhaveiWmW֠W֨W֬WWWWWWWhaving֦W֬WWWhavingadefinedprimitiveforbothlinklayerandmihcommaVhavingadefinedprimitiveforinformationservicemessagesVheaderWheldWhelpsnWhere֏WheterogeneousWhidingքWhigher։WWhigher-layerWhle։WhliWWhocWWholds֙WhomeքWhowwW֒W֥WWWhowcanyoudeterminebeforehandthatthehandoverwillbewVhoweverWWi|WցWքWWWid֦WWideaWidentifier֠W֩W֪W֫WWWidentify֤WidsW7= bAMake the following text change; 5.6.1 MIH_MGMT_SAP This SAP is defined in 802.11, 3GPP, 3GPP2. This defines the interface between the MIH Function layer 7.1 Introduction Following are the key SAPs MIH Function uses for interfacing other entities. 1) MIH_MGMT_SAP: The MIH Function uses this SAP for interfacing with lower layers of media specific access networks. Primitives defined as part of this SAP are recommended as enhancements to media specific SAPs. This SAP is not applied to 802B.16. In case of 802.16, M_SAP shall perform the same function as MIH_MGMT_SAP. 2) MIH_SME_SAP: The MIH Function uses this SAP for interfacing with the System Management Entity in 802.11. or Network Management entity. In case of 802.16, M_SAP shall provide interface between MIH Function and Network Control and Management System (NCMS). 3) MIH_SAP: This is the main SAP which upper layers use for interfacing with MIH Function and accessing the various MIH services. This is a new SAP. 7.2<? bC MIH_MGMT_SAP, M_SAP Primitives The key primitives defined as part of MIH_MGMT_SAP, M_SAP are described in the table below. Table 8.MIH_MGMT_SAP, M_SAP Primitives@A  33   335  a  33b  33    33  =  33    33    33  B  33    33.  5  33    33cIf the MIH reference model for 802.16 is accepted, section 7' s structure for 802.16 shall be changed accordingly. Since MIH_SME_SAP is only applied to 802.11 and MIH_MGMT_SAP is not applied to 802.16, restriction shall be added in the text.  2005/09/21ERonnyFKim^Technical, Non-binding_60`32a7.2.13cstructureWsubmittedWsubnetoWsuccessfulWsuchmW}WWWWWWWsufficientrWsuggestWsuggested֫WֵWWsupport֥WWWWsupportedWWWWsupportingWsure֓WsynchWsystemsnWt|Wtable֤W֥W֦W֧W֩W֪W֫W֬WWWWWWWWWtable7isjustinformativeandshouldnotbeincludedinthVtable-1Wtable-3WtablesWWWWtables2and3aremihcommandsforlocalandremotepurposeVtaken~WtalkցWօWtalking}WtargetWtcpWtechnology֖WteleconferenceWtellWterm֩W֪WW=AbCDelete section 7.2.13 or 7.2.14 or add more handover related text. cAIn section 7.2.13 and 7.2.14 SDU related event services are described. These triggers are for interaction between MAC and intermediate buffers (?). What is the purpose of these events? Are they related to the handover? This trigger is not very general enough to use for handover case. If there is no full context transfer including ARQ state from old PoA to new PoA, these trigger can not be used for handover case. 2005/09/21ERonnyFKim^Technical, Non-binding_62`14a7.2.15, 7.2.16, 7.2.17bDelete Section 7.2.15, 7.2.16, 7.2.17 or add more text to clarify the differences from Link_Going_Down, Link_Down, and Link_Up. c`bhandoversWhasWWhaveֹWWWhavingֶWheadWhenceWheterogeneousWhexbinaryWWhigherWWWWWhigher-layerWhomogeneousWhoweverWhttpWWiWWWiinsection1.2purposeisnotonlytoenablebetterusereVimodifycmdconfiguretoindicatethetypeofparameterandVianaWidWWidentifierWWidentifiersWWidentifyWWieeeWWiesWWifWWWWWiiWWiidefineanewcommandViiiWWimplementationWWWimportantWWinֶWֹWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWincludeWWWWWWsectionfollowinV?C 3cAIn section 7.2.15, 7.2.16, 7.2.17, Link_Handover_Imminent.indication, Link_Handover_Proceeding.Indication, Link_Handover_Complete.Indication are described repectively. What is the difference between Link_Handover_Imminent.Indication and Link_Going_Down ? What is the difference between Link_Handover_Proceeding.Indication and Link_Down? What is the difference between Link_Handover_Complete.Indication and Link_Up? I think there is overlap in event services.  2005/09/21ERonnyFKim^Technical, Non-binding_55`49a7.2.7.1bT"6b8W8-3W8.4W8.5.3W802.11WWWW802.16ֶWWWW802.21WWWW802.3W87W88W89W9W9.1W9.2W90WaֹWWWWWWWWWWWWWWWWWWWWWaabbccddeeffWabilityWableWaboutWWaboveWaccessWWWWWaccessesWaccessibilityWaccessingWacrossWWWWWAD bAInsert the parameter "result" in parameters of 7.2.7: ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description -------------------------------------------------------------------------------------------------------------------------B--------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- Result | BITMAP | Indicates the result of Link setup process. CE bC | | 0: Success | | 1: Authentication Fail | | 2: Link setup timeout | | 3~7: Reserved -------------------------------------------------------------------------DW-------------------------------------------------------------------------------------- !@A  335  336  7    x    cIn the draft, all successful cases are considered. During a link setup procedure, link setup may fail due to various reason, and failure shall be reported to upper layer. 2005/09/21ERonnyFKim^Technical, Non-binding_81`58DGva7.4.12bADAdopt the remedy 3 in the contribution " DCN # 21-05-0359-00-0000 " D@A>  33)  33A  33>cMIH Handover Commit is defined in Table 10. MIH_Handover_Commit.request/response primitives section shall be aded in the text.  2005/09/21ERonnyFKim^Technical, Non-binding_86`22a 7.47.13.2.2bAInsert the parameter "TimeDifference" in Semantics Table of 7.4.13.2.2 as indicated below: ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Description -----------------------------------------------------------------------------------"NWbadoptthefollowingnewtextַVadoptthefollowingtextָVֻVֽV־VֿVVVadoptthefollwingtextֺVadopttheremedy1and2inthecontributiondcn21-05-0359-Vadopttheremedy3inthecontributiondcn21-05-0359-00-000Vadopttheremedy4inthecontributiondcn21-05-0359-00-000VֶWandֶWWWWWWWWWWWWWanexWannexWWapplicableWappliedWareWWWWareaWasWWWassociatedֹWatֹWWattachedֹWattachmentֹWauthenticationWWavailableֶWWbasedWWbeֹWWWWbelowWWWbetweenֶWWWWWWbitmapWWbothWWbyֹWWWWWcWWcachingWWcanֹWWWWcannotWcapabilitiesֹWcapableּWEH bB----------------------------------------------------------------------- ................. | .............. | ................ ---------------------------------------------------------------------------------------------------------------------------------------------------------- TimeDifference | Time in msecs | When a PoA encapsulates Agent Advertisement C | | or Router Advertisement in Network Address | | Information parameter, this parameter is time | | difference between the time of caching the | GM bDI | information and the time of encapsulating the | | information ---------------------------------------------------------------------------------------------------------------------------------------------------------------@AR  33[  33]  5  RcSince MIH_Network_Address_Information.response can carry router advertisement or agent advertisment buffered at PoA, time difference for MS to check the freshness of the message shall be added.  2005/09/21ERonnyFKim^Technical, Non-binding_94`1a8.3bACAdopt the remedy 4 in the contribution " DCN # 21-05-0359-00-0000 "C@A>  33)  33A  33>cmBecause figure 26 only reflects the IPv4 case, it is necessary to update the figure to reflect IPv6 as well. 26R?a8.2.1ֲ8.38.3.1ֳ8.3.28.4dVdWtable-1table-5b0WW0successV1WWWW1authenticationfailV10W2WWWWWW2linksetuptimeoutV21-05-0348-01-0000WW21-05-0359-00-0000WWW21-05-0361-00-0000WWWWWW21-05-0370-00-0000W22-43W3WWWWW37reservedV3.2W3gppWWW3gpp2WWW4W5.3.2W5.3.3W5.5.1W5.5.2W5.5.3W5.6WW5.6.1WW5.6.1mihmgmtsapVV5.6.2W5.6.3W5.6.4W5.6.5W5.6.6W5.6.76W5.6.87W5.6.9W5.6.98W6W6.3.1W6.3.1.1W7WWW7-11W7.1W7.2W7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.2.7W7.4.13.2.2WbmultipleּWWWmustWWWWnameWWWWWWWWWnametypedescriptionVnamelyWnamingWnas-port-typeWWncmsWnecessaryWWneedWWWWneedexplicittextdefiningthescenariomobilegeneratedorVneededWneighborWneighborhoodWneighboringWWWWneighboring-networkWneighboring-poaWWֹWּWWWWWWnoWWnodeֹWּWWnoiseWnon-freeWnonnegativeintegerWnotֶWWWWWWWnoteWWnsertWnumberWWobjectpropertyWobtainWWWobtainedWWobtainingWoccurWofֹWּWWWWWWWWWWWWWWWWWWWWWWWWWWohbaWWWcmessageszW|WWmgmtWWWWmibWmicsWmiesWmightִWWmihmW{W}WցWօW֌W֎W֜W֝W֦W֨W֭W֮W֯WֱWWWWWWWWWWWWWWWWWWWWWWWWWWmihhandovercommitisdefinedintable10mihhandovercommVmihhandoverpreparerequestandresponseprimitivesarecapVmihmgmtsapisnotdefinedVVmihmgmtsapisnotdefinedandtheoverallsaporganizationVmihnetworkaddressinformationrequestandresponseprimitiVmih-capabilityWmih-switchWmihfWmiiWWWWmiisWWmissingWmmobilityքWmobileoWּWWWmobile-ipWmobilitylWmWqW֏W֥Wmode֧W֬Wmodel֏W֙W֚WֹWּWWWWWWWWmodelsWcmodification@neednotdetection@notnotaccurate@on@only@ooverall@primitives@kproblem@Uprocess@related@Orequest/response@save@secure@#setup@{sincegniandhliaremergedintomiithistableforhliis@structure@>terminal@terminology@theasn1representationofextendedschemaisnotneededas@positiontohaveoverallv@thesubnetassociationisnotastepthatamobilenodenece@thiscouldbeperformancedestructivefortheterminalince@toֶtobetakenoutofthespecification@updatereferencediagramanddescriptionfor802.16@%weshouldbecarefulonusingthewordarchitecture802.21d@whatdoweexactlydefinebyhandoversignalingisittheex@which@ad‚b֛japplication/layer@connectivity@different@event@information@is@HPH 2005/09/2126ERonnyFKim^Technical, Non-binding_96`41a8.4bAInsert "type column" in all tables in the 8.4 section following the example below; editor shall insert type column in all tables in the 8.4 section and assign subsequent values in ascending order: ---------------------------------------------------------------------------------------------------------------------------------------------------------- Name | Type | Length | Value ------FbadvertisementWWagentWWallWWWWWWallowWWalongWalsoWWWWWalternativelyWaltitudeWaltresWambiguityWWWWWWWWWWWWWWWWWWWanexWannexWWanyWapplicableWappliedWareWWWWWWWareaWasWWWWWWWWWascendingWassignWassociatedֹWatֹWWWWWattachWattachedֹWattachmentֹWWaugmentedWauthenticatedWauthenticatesWauthenticationWWavailableֶWWWbasedWWWbasicWWWbeֹWWWWWWWWWWWbeforeWWWbelongWbelongsWbelowWWWWWWWecrelatedWrelationshipsWremoteքW֟WWWWWremoteregistrationwouldbeequallyusefulforthemicsandVremovedWWWrenamedWWreorganisationִWrepectivelyWreplaceւWփWևW։WreplacewithupperlayersևVreplacewithupperlayersmultipleoccurencesofl3mpւVփVreplacedWրWWWWreportedWreposirotyWrepositoryWrepresentationWWWrequest֚WֱWWWWWrequestforaconsistentformofeventandcommanddefinitioVveWresponse֭W֮W֯WWWWresponsibleքWrestrictionWresultWrevisedWWWWWrlcrW֛WrncցWrouterWsWsamesWtWyW֨W֭W֮W֯WWWsameaspreviouscommentsVtVsap֌W֍W֎W֒WWWWWWsapsWWMQ bB---------------------------------------------------------------------------------------------------------------------------------------------------- SupportedEventList | 1 | 4 | ---------------------------------------------------------------------------------------------------------------------------------------------------------- SupportedCommandList | 2 | 4 | ---------------------C------------------------------------------------------------------------------------------------------------------------------------`@A  33    33  33      33        33      PVciIn order to make standard TLV (Type Length Value) format, type field shall be added in all tables in 8.4. 2005/09/21ERonnyFKim 2005/09/21EBenjaminFKoh^Technical, Non-binding_34`38a6.1.5bXTo replace: 6.1.5 Primitives for Link Layer Events With: 6.1.5 Primitives for Events cqPrimitives should apply for both Link Layer and MIH Events in order to provide extensibility to the MIH Function. 2005/09/21EBenjaminFKoh^Technical, Non-binding_36`3a6.2.2bATo insert: 6.2.2 Primitives for Commands The generic model of Command Service primitives specifies the format of commands that are passed from the MIH Function to the link layer and also from the upper layer entity to the MIH Function. The Command primitive is defined as: CommandXX. request (CommandSource, CommandInformationSet) where, - CommandSource: is used to identify the command source entity where the command originated; - CommandInformationSet: is an extensible parameter thatIaannexWWWWWannexc1Vannexc2Vannexc3Vannexc4VannexdVcWWWWdWtable-1table-5b0WWWWW0successV001122334455W0123456789abW1WWWWWWWWWW1authenticationfailV1.0WW1.2WWWWW2linksetuptimeoutV2.1W2.2W2.4W20W21-05-0346-0000WWW21-05-0348-01-0000WW21-05-0359-00-0000WWWW21-05-0361-00-0000WWWWWW21-05-0370-00-0000W22W22-43W23WW27W3WWWWWW37reservedV3.2W36W39W3gppWWW3gpp2WWW4WWWWW41W42W44WW45W46WW47W5WWWW!bvaluesWWvariableWvariousWWWverifyWversionWWWviaWWWvisibleWvocabularyWw3WWwaysWweWwerequesttomergethetwotablesandprovideaconsistentVֹWWWWWWWWWWWWWWWWWwithinWWxxWyoshihiroWWyyWzzWc1W10W11uW֕W֞WW14֚WW16W2rW֣WWW21}W21-05-0359-00-0000W22WW255W26W3֏WֶWַWָWֹWֺWֻWּWֽW־WֿWWW4WWW5W5.3.3֡WW5.6W6ֵWWW6.1.5W6.2.5.1֟W6.3.1W7WWW7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.4.10.2֭W֯W7.4.10.2.4֮W7.4.11.2.2W8.3W8.4WvBb6.1.5primitivesforlinklayereventsV6.2.2W6.2.2primitivesforcommandsV6.3.1W6.3.1.1W6.3.3W6.3.3primitivesforinformationV7WWWW7-11W7.1W7.2W7.2.11.3W7.2.13WW7.2.14WW7.2.15WW7.2.16WW7.2.17WW7.2.7W7.4.11.2.2W7.4.13.2.2W7.4.14.1.2W7.4.14.3W7.4.14.3.1W7.4.14.3.2W7.4.14.3.3W7.4.9W7.4.9mihscanV74WkLcproblemִWproblemsWprocedureWWproceedingWQW bB may contain implementation specific information and may be different across different commands. CommandInformationSet completely describes the command that is issued. Command primitives typically do receive a response defined as: CommandXX. response (ResponseSource, CommandResultSet) where, - ResponseSource: is used to identify the source entity where the response originated; - CommandResultSet: is an extensible parameter that may contain the result of the request and may be differenCt across different commands. cnHaving a defined primitive for both Link Layer and MIH Commands would allow the MIH Function to be extensible. 2005/09/21EBenjaminFKoh^Technical, Non-binding_46`25a6.3.3bVX bATo insert: 6.3.3 Primitives for Information The generic model of Information Service primitives specifies the format of information requests that are passed from the MIH Function to the link layer and also from the upper layer entity to the MIH Function. The Information primitive is defined as: InformationXX. request (RequestSource, InformationRequestSet) where, - RequestSource: is used to identify the source entity where the query originated; - InformationRequestSet: is an extensibBle parameter that may contain implementation specific information and may be different across different queries. InformationRequestSet completely describes the query that is issued. Information primitives typically do receive a response defined as: InformationXX. response (ResponseSource, InformationResultSet) where, - ResponseSource: is used to identify the source entity where the response originated; - InformationResultSet: is an extensible parameter that may contain the result of tWZ bC:he request and may be different across different queries. cjHaving a defined primitive for Information Service messages would allow the MIH Function to be extensible. 2005/09/21EBenjaminFKoh^Technical, Non-binding_93`25a8.3bATo replace: [2] MIH remote registration: Remote MIHF in different entities can register with each other to receive Media Independent Handover Messages including remote MIES. No registration is required for command services. With: [2] MIH remote registration: Remote MIHF in different entities can register with each other to receive Media Independent Handover Messages. The MIHF or an upper layer entity may choose to allow, deny or control the handling of messages from the MIES, MICS and BPMIIS, depending upon the information exchanged during the registration process. >cURemote registration would be equally useful for the MICS and MIIS as well as the MIES 2005/09/21EBenjaminFKoh 2005/09/21EJinFLeebentriesWWWenumeratedWequalityWequivalentclassWerrorWessentialWestablishWestablishingWeventWWWWWWWeventsWWWWWeventsourceWexactlyWexampleֶWWWWWexamplesWexchangeֶWWexchangedWexchangesֶWexistingWexpectedWWexperienceWexplainedWexplicitWextendWextendedWWWWWextensibilityWextensibleWWextensionWextractWfacilitateWfailWWfigWfigureWWWWWWfilterWfindingWflagWWX[)^Technical, Non-binding_75`60a 7.4.9.2.4bAModify the following text: [Modify the text, page 74, line 13]: 7.4.9 MIH Scan A MIH Scan command is issued by upper layer entities to discover the neighboring POA of the access networks. MIH Scan may contain the scan command for multiple links. The scan command for each link is defined in the related SDO and beyond the scope of the current version of the standard. If the currently active link is required to scan, it is most likely that the on-going session is interrupted. If the MIH caZ^ bBpability may be discovered during scanning procedure, MIH_Scan.response may include MIH capability parameter. [Insert the MIH Capability parameter, page 74, line 59]: MIH_Scan.response ( Source Identifier, Destination Identifier, Scan Response Sets, MIH Capability ) -------------------C---------------------------------------------------------------------------- Name | Type | Valid Range | Description ----------------------------------------------------------------------------------------------- .. | .. | .. | .. ----------------------------------------------------------------------------------------------- MIH Capabilit^] pcAMWhen MIH_Scan command is issued to request scanning for multiple links, each link may scan to find the neighboring PoAs. If the MIH capability delivery through broadcast message is adopted by SDOs, MIH capability can be discovered during scanning. It is natural to include MIH capability information in the scanning response. M 2005/09/21  B    ^          (  )                    T  r  w B  c\c5EJinFLee^Technical, Non-binding_58`54a7.2.11bA[Insert valueOfLinkParameter as one of parameters, Page 59, Line10 ]: Parameters ------------------------------------------------------------------------------------------------------------------------------------------ Name | Type | Description ------------------------------------------------------------------------------------------------------------[\ 2bDy | Flag | | 0: MIH Capability Not Supported | | | 1: MIH Capability Supported ----------------------------------------------------------------------------------------------- @A  33  33  @  B    ^          (  )                    T  r  w B  cbsdoWsectionWWWWWWWWWWWWWWWWWWWWsectionsWWsecurityWWseeWselectWWselectingWsemanticsWsendingWWsenseWsentWsentenceֹWserveWserviceWWWWWWWWWservicesWWsessionWsetWWsetsWWsetupWWshallWWWshouldWWshowWshownWWshowsWsignalWsimultaneouslyּWsinceֹWsingleWsmeWWWsmiWsoWsolveWsomeWWsomehowWWWspecifiesWWspecifyWspeedWstaWWWsta'sWstandardWWstandardsWstartingWWWWstateWstationWstrengthWstrictlyWstringWstructureWsubWsubsection@bincludethetextandfigurefromsection3ofdocumentnumbeVincludedWincludesֹWWWWincludingWindependentWWWindependentlyֹWindicateWWWWindicatedWWWindicatesWWindicationWinfoWWinfoqueryfilterWinfoqueryparametersWinformationWWWWWWWWWWWWWWWWWWWWinformationresultsetWinformationxxWinitiateWinsertWWWWWWWWWinsertthefollowingtextatline58ofpage46Vinserttheparameterresourcestatusinsubsection7.4.11.2.2Vinserttheparameterresultinparametersof7.2.7Vinserttheparametertimedifferenceinsemanticstableof7.Vinserttypecolumninalltablesinthe8.4sectionfollowinVinsertvalueoflinkparameterasoneofparameterspage59linVcwhich֍W֎W֙W֨WWWWWWwhileWwhyքW֏W֙WWWwhywouldiwanttopropagateeventtotheremotel3mpwhatքVwich֍WwillmWwWִWWWwirelineWwithnWWրWւWփWևW։W֤WWWWWWWWWWWwithin}WWWwithoutWWwon|WwordjWworkWworkscopeWwould|WքWWWWWWWwrongvWxxxWWWyouwWd i0j@kPl`mpnqpo‚!r‚"s‚#t‚$u‚%v‚&w‚'x‚(y‚)z‚*{‚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֚‚bcdiscussionWWdnsWdo{W֬WWWWdocִWֵWdocumentyWִWWWdocumentsWdoes}WքW֣W֨WWWWWdon't֬WdontWdownWWdraft֔W֕WWWWWWWdueWduringWWWWduringtheexerciseofl2requirementsitwasrealisedthatVdynamicallyWdynamicallychangingiescannotbesupportedbyinformationVeWWWWWWWWelsewhereWenablerslWenhanceWenoughpWWentireWentitiesWentity։WequallyWequipementsִWerrorWes/csִWessentialmWestablishingWethernetWevenzWքWevenaftersecureassociationtheeventscommandsandinformzVeventքW֚W֜W֝WWWWWWWeventszW֗W֛WWWWWWWevery֤Wexactly{W]d bB------------------------------ EventSource | Link_EVENT_SOURCE | The origination point from where the event is generated ------------------------------------------------------------------------------------------------------------------------------------------ MacMobile | MAC Address | MAC address of Mobile Terminal Terminal --------------------------------------------------------------------C---------------------------------------------------------------------- ValueOfLink | | Specify the value of link parameter Parameter ------------------------------------------------------------------------------------------------------------------------------------------ MIH Capability | Flag | 0: MIH Capability Not Supported cf bD 1: MIH Capability Supported ------------------------------------------------------------------------------------------------------------------------------------------ Examples of link layer parameters : Link Speed Link Bit Error Rate Link Received Signal Strength Indication Link Carrier to Interference plus Noise Ratio Modify the subsection 7.2.11.3 as shown below, Page 59, Line 36 ] : Upper layers include MIH Function may discover additional properties of the Elink before selecting it for establishing connectivity. If the 'ValueOfLinkParameter' is included, upper layers may select the link to connect based on the value of 'ValueOfLinkParameter. v@fh bcABy the current draft, when MIH Function receives Link_Detected.indication event from the active links, MIH Function may try to find out additional propoerties of the links before selecting new link for establishing connectivity. If the Link_Detected.indication is triggered as a result of PoA discovery procedure including scanning, 'valueOfLinkParameter' can be included. Therefore, we propose to add the parameter "valueOfLinkParameter" in Link_Detected.indication so that MIH Function sBelects the target connection link instantly without discovering additional link properties such as link speed, link bit error rate. r 2005/09/21EJinFLee^ Editorial_34`38a6.1.5bARReplace "6.1.5 Primitives for Link Layer Events" by "6.1.5 Primitives for Events"R@A  33csection 6.1.5 is to show the general primitive format for event service, not only for link layer events. Therefore, title should be changed. 2005/09/21de nbAV  33G  33  33    33"  #  /  o        33  '  33k  33l  33  Vbreplacecurrentsection5.3.2bythesection5.3.2indcn21Vreplacefig9withfig9incontributionwithdcn21-05-0361Vreplacefigure2withcontribution21-05-0370-00-0000Vreplacesection5.3.3withtextbelowVreplacesection5.5.1withsection5.5.1incontributionwitVreplacesection5.5.2withsection5.5.2incontributionwitVreplacesection5.5.3withsection5.5.3incontributionwitVreplacesection5.6withsection5.6incontributionwithdcVreplacetable23withtheonedescribedinsection2.4of21Vreplacetable4withtheonedescribedinsection2.1of21-Vreplacetable5withtheonedescribedinsection2.2of21-Vreplacetextbetweenlines20and44ofpage41withthefolVreplacetextstartingatline27ofpage89andendingatliVreplacethetextwithVreplacethetwoparagraphsstartingatline1ofpage47witVreplacesֹWreportWWejEJinFLee^ Editorial_96`20a8.3.2bAModify the11th row in table 14 as indicated below ---------------------------------------------------------------------------------------------------------------------------------------------------- 11 | MIH Command Discover MIH Event Discover | Request/Response | Event Service | ----------------------------------------------------------------------------------------------------------------------------------------------------@A  332  33    33  33      33cThe MIH message for 'MIH Command Discover' in table 14 does not exist in the current draft. In addition, MIH Event Discover message was omitted from this table. Therefore, we suggest that MIH command Discover should be replaced with MIH Event Discover 2005/09/2114EJinFLeeccurrentsection5.3.3istooambiguousVcurrentlyWdWdata֍W֎WWdcnWdedicated|Wdeeply֣Wdefine{Wdefined}W֚W֩W֪WWWWWWWWWWWWWWWWWdefinesjWlWdefinitionrWvWֶWַWָWֺWֻWֽW־WֿWWWWWWWdefinitionsyWֵWWWWdeliver֍W֎WdeliveryWdescibedWdescribe֟WWdescribed֡WWWWWWdescription֍W֎W֩W֪WWWWWWWWWWWdescriptiveWhlt^Technical, Non-binding_64`44a7.4.1bA@Adopt Remedy 5 in the contribution "DCN # 21-05-0359-00-0000" @@A  33cDetails of the MIH Capability Discover was left out. As the proposed contribution, MIH_Capabilty_Discover.request/response primitive should be defined. 2005/09/21EJinFLee^ Editorial_80`53a 7.4.11.2.2bAInsert the parameter "ResourceStatus" in subsection, 7.4.11.2.2 as indicated below: MIH_Handover_Prepare.response ( CommandSource , CommandDestination , CurrentLinkIdentifier , TranspoUcprimitivesֵWWWWWWWWWWprimitivesshouldapplyforbothlinklayerandmiheventsiVjp bBrtLayer, ResouceStatus , QueryResourseList ) @A  33U  33s  33  33)  3  D  33cone of parameters for MIH_Handover_Prepare.response is missing. For consistency with the table of section 7.4.11.2.2, 'ResourceStatus' should be added. 2005/09/21EJinFLee 2005/09/21E YoshihiroFOhba^Technical, Non-binding_41`20a6.3.2b0VbbetweenֶWWWWWWWWbeyondWbidirectionalWbindingWbitWbitmapWWbooleanWbothWWWWWbroadcastWbssidsWbuildsWbutWbyֹWWWWWWWWWWcWWWWWcachingWWcanֹWWWWWWWWWcannotWcapabilitiesֹWWcapabilityWWWWcapableּWcardinalityWcarnalityWcarriedWcarrierWcarriesWbqueryresourselistrWradiusWrangeWWWrateWWWratioWrdfWWWWrdf/xmlWrdfsWreadyWreceiveWWWreceivedWrecommendedWreconsiderWconlylWmWքW֕W֚W֞W֬WWWWWWWWonlyexistsfor11֞VoperationalnWoperator֠WWoperatorienetworkidentifierandoperatorinformationelem֠VoperatorsWWorwWWWWWWWWWorderWWWorganizationWother֍W֎W֚W֩W֪W֬WWWWout~W֒WWWoutsideWlWpacketWpackets֌Wparameter֥WWWparametersWWpartֱWWperformքWperformancenWphaseWphyrW֛WWpleaseִWֵWpoa֫WWWWWpoasWWWpointքW֧W֬WֹWpointsWpolicyxWpoll֨WpositioniWpossible֧WpowernWprecisepWprecised֙WprepareWpresentWWpreventօWprevioussWtWprimitive֦W֩W֪WWWWWWWls bAReplace text between lines 20 and 44 of page 41 with the following: " The information elements provided by the Information Service can be classified into two categories: 1) Media-Independent Information (MII): These information elements describe the media-independent properties of the network. MII includes of Point of Attachment, Neighboring Networks, Neighboring PoAs, Location of PoA, Network Operator, Roaming Partners, Cost, Higher Layer Security Support, and Higher Layer QoS SupportB . 2) Media-Dependent Information (MDI): These information elements describe the information related to link and physical layers. MDI includes of Data Rate, MAC Type, PHY Type, Link Layer Security, and Link Layer QoS . Each information element in MII and MDI belongs to one of the following two sets, e.g, , the basic set and the extended set. Information elements in the basic set must be supported by all MIH entities. Support for information elements in the extended set is optional. Tsr cA- General Network Information (GNI) and Higher Layer Information (HLI) should be merged into "Media-Independent Information (MDI)". Link Layer Information (LLI) should be renamed to "Media-dependent Information (MII)". - Tables 4, 5 and 6 should be reduced into two tables of MDI and MII, and revised with more detailed description. - Definition of basic set and extended set needs to be clearly described in this section. 2005/09/21e available via 802.21 information service frDamework, it is important to note that MDI will be mostly directly available via media specific technologies. In cases where media specific amendments are not available or possible, information elements in MDI can be carried over via higher layer transport. "cqwE YoshihiroFOhba^Technical, Non-binding_41`49a6.3.2bnReplace Table 4 with the one described in Section 2.1 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.cA- Media Types column is not meaningful. The Media Types column should be replaced with another column that indicates whether a given information element belongs to basic set or extended set. - "List of networks available" should be renamed to a less confusing name. - "Network standards supported" is ambiguous and should be removed. - "Network identifier" is similar to "Operator" and should be removed. - "Operator" needs to have not only a name but also a unique identifier. - "IP Verspq bCables 4 and 5 describe a set of information elements in both categories that include the basic and extended set. When new information elements are added to MII or MDI, they need to be most likely defined in the extended set. Information elements may be obtained via a PoA before the STA authenticates to the PoA irrespective of whether they belong to the basic or extended set. While all of the above information elements are necessary and will be available via 802.21 information service frDamework, it is important to note that MDI will be mostly directly available via media specific technologies. In cases where media specific amendments are not available or possible, information elements in MDI can be carried over via higher layer transport. "c !bthisWWWWWWWWthresholdWthroughWthusWtightWtimeWWtimedifferenceWWtimeoutWWtoֹWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWtoinsertVVtoreplaceVVtransactionWtransferWtransmissionW ;bonlyWWonpropertyWontologiesWontologyWWopennessWoperationWoperatorWWWoperator-idWoperator-nameWoptionalWWorWWWWWWWWWWWWWWWorderWWorg/1999/02/22-rdf-sWorg/2000/01/rdf-scheWorg/2001/sw/dataacceWorg/2001/xmlschemaWWorg/2001/xmlschema-iWorg/2002/07/owlWorg/assignments/enteWorg/assignments/radiWoriginatedWWoriginationWotherWWWWWWWWothersWWoutWoverWWoverallWoverlappingWowlWWpageWWWWWWWWWpanaWparagraphsWessWWWpropertiesWWprotocolWprovideWWWprovidedWprovidesWpurposesWqosWWqueriesWqueryWTlb5.3.2W5.3.3W5.5.1W5.5.2W5.5.3W5.6WW5.6.1WW5.6.1mihmgmtsapVV5.6.2W5.6.3W5.6.4W5.6.5W5.6.6W5.6.76W5.6.87W5.6.9W5.6.98W58W59WW6WWWW6.1.5WW6.1.5primitivesforeventsVrx cBion" is not useful information and should be removed from MII. - "SLAList" information is ambiguous and should be removed. - "neighbor information" contain only static and limited information such as a list of neighboring PoAs. Also it should be replaced to more specific name like "neighboring PoAs". - "AccessRouterInfo" is too detailed to be defined in the basic set. - More detailed description and comments are needed for each information elements.  2005/09/21Table 4E YoshihiroFOhba^Technical, Non-binding_42`39a6.3.2bnReplace Table 5 with the one described in Section 2.2 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.cw| ncA- Media Types column is not meaningful. The Media Types column should be replaced with another column that indicates whether a given information element belongs to basic set or extended set. - "Neighbor information" can contain MII and MDI, and can be obtained by querying the basic set and extended set of each PoA in the "neighboring PoAs" information element in MII. Thus, this is redundant and should be removed from MDI. - "AccessRouterInfo" is not MDI and should be removed. - More BLdetailed description and comments are needed for each information elements. : 2005/09/21Table 5E YoshihiroFOhba^Technical, Non-binding_43`6a6.3.2bRemove Table 6.cS- Since GNI and HLI are merged into MII, this table for HLI is not needed anymore. 2005/09/21Table 6E YoshihiroFOhba^Technical, Non-binding_43`42a6.3.2bLyoshihirobdataWWWWWWWdata-rateWdatatypeWWdatatypepropertyWdatumWdcnWWWWWWWWWW#csetupWshallWWWWWshouldjW֙W֛WֱWWWWWWWWWWWWWWWWWshoulddifferentiatephymacllcrlcevents֛VshowmWWshowingWshownWsideWsignaling{WWWWsignificantWsimilarWsimpleWsince֔WWWWWWWWVsincethebasicschemausesowlinadditiontordfschemaaVsinglerW֩W֪WsitsmWslalistWsmeWWsomWnW֓WWsome֟WֱWִWWWWsomedescriptionisneededastohowextendedschemacanbeVsource֩WspecificuW֍W֎W֖WWWWWspecifictoonetechnology֖Vspecification~W֣WspecifiedWspecify֨WWspecifying֧WspeedWstackqWrWstandardWWstandardsWstateWstaticWstepoWx} lbAReplace the text with: " MIHF entity (e.g., a STA or network entity) can extract the information elements in the basic set and the extended set either from media specific broadcast information or by sending a specific request/response primitive. On the other hand, before sending a request/response, the MIHF entity should have the knowledge that the network supports the 802.21 MIH standard (e.g., via a management frame that carries capability information). For example, MIHF entity in STA mBcay request the MIHF entity of PoA for such information. It is important to note that before a STA is authenticated to the PoA and ready to exchange data, it should be able to obtain all the information elements listed in Tables 4, 5 and 6. These information elements may then be used by the STA's handover function to determine the right PoA to attach. "Qc| @cAJ- The text can be described without referring Table 7 (which is refereed incorrectly to as Table 8.3) and Figure 22. - The text should be revised that information elements in both the basic set and extended set can be obtained either from media-specific broadcast information or by sending a specific request/response primitive.J 2005/09/21E YoshihiroFOhba^Technical, Non-binding_44a6.3.2bRemove Figure 22.cFigure 22 is not useful. 2005/09/21 Figure 22E YoshihiroFOhba^Technical, Non-binding_45`1a6.3.2bb- Remove Table 7 - Remove text starting from line 39 of page 45 and ending at line 23 of page 46.cGTable 7 is just informative and should not be included in this section. 2005/09/21Table 7E YoshihiroFOhba^Technical, Non-binding_46`58a6.3.3.1b:bdifferenceWWdifferencesWdifferentWWWWWWWdiffservWdirectWdirectionsWdirectlyWWdiscoverWWWWdiscoveredWdisjoint-nessWdistinctWdistinctionֶWdistributedWdnamicWdoWWdocWWWWWWdoctypeWdocumentWWWdoesֶWdomainWWWdownWdraftWWduringWWdynamicWeWWWWWWeachֹWWWWWWWearlierWeaseWeditorWeffectWeitherWWWeitherdeletethefigure10ormodifyforconsistencyVelementWWWelementsWWWWemphasizesֶWenableWencapsulatesWWencapsulatingWWendingWWWWendpointֶWֹWendpointsֹWenhancementsWWWWubparameterWWWWWWWWWWWWparametersWWWparsetypeWpartWWWparticularWpartnersWWpartsWpassedWWpathWpayloadsWpeerWWperformWperfromingWperiodicallyWphyWWphysWphysicalWplaneWpleaseWpleaseseethecompaniondocument21-05-0365-00-0000-cmodelVplusWpoaWWWWWWWWWpoa-idWWpoa-id'sWpoa-typeWWpoasWWpointֹWWWWWpointsWWWWWWWprivateWprocedureWprocessWWWpropertiesWWWWWpropertyWWprotocolWWprovideWWWprovidedWWprovidesWpurposesWqosWWqueriesWqueryWWWqueryparametersW} bAInsert the following text at line 58 of page 46: " In order to strictly define each information element in an RDF schema, the schema is augmented with Web Ontology language (OWL) [OWL]. OWL is a Web Ontology language. OWL uses both URIs for naming and the description framework provided by RDF to add the following capabilities to ontologies: - Ability to be distributed across many systems - Scalability - Compatibility with other Web standards for accessibility and internationalizationBR - Openness and extensibility OWL builds on RDF and RDF Schema and adds more vocabulary for describing properties and classes: among others, relations between classes (e.g. disjoint-ness), carnality (e.g. "exactly one"), equality, richer typing of properties and characteristics of properties (e.g. symmetry), and enumerated classes. "@ckSince the basic schema uses OWL in addition to RDF Schema, a brief description about OWL needs to be added. 2005/09/21E YoshihiroFOhba^technicalWWWWWWWWWWWWWWWWWWWWSqbwebWwellWwell-placedWwell-suitedWwhenWWWWWWWwhetherWwhichWWWWWwhileWWwillWwithֶWֹWWWWWWWWWWWWWWWWWWWWwithinWWwithoutWxxWyoshihiroWWWyyWzzWc1W10W11uW֕W֞WW14֚WW16W2rW֣WWW21}W21-05-0359-00-0000W22WW23WW255W26W3֏WֶWַWָWֹWֺWֻWּWֽW־WֿWWW4WWW5W5.3.3֡WW5.6W6ֵWWW6.1.5W6.2.5.1֟W6.3.1W6.3.3.1W7WWW7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.4.10.2֭W֯W7.4.10.2.4֮W7.4.11.2.2W8.3W8.4Wbc802@a@above@adding@allqueryfiltertypesanditsusagedefinedinthissectiona@annex@,anymore@at@be-cin5.6sapssuchasmihphysapmihllcsaparedescibedbutVinordertomakestandardtlvtypelengthvalueformattypeVinordertoreflectthediscussiononthemihreferencemodeVinsection7.2.13and7.2.14sdurelatedeventservicesareVinsection7.2.157.2.167.2.17linkhandoverimminentindicVinthedraftallsuccessfulcasesareconsideredduringaliV'^Technical, Non-binding_46`59a6.3.3.1bAReplace the two paragraphs starting at line 1 of page 47 with: " As described earlier, the RDF schema definition for MIIS consists of two parts; the basic and the extended schema. The basic schema is not supposed to be updated. An MIH entity is typically pre-provisioned with the basic schema for ease of implementation of schema-based query. In scenarios where the basic schema is not pre-provisioned methods such as DHCP may be used to access the URL of the basic schema. Unlike the basic s bBchema, the extended schema is expected to be updated periodically, e.g., when a new link layer technology is introduced. The extended schema can be retrieved from the specified URL via the IEEE 802.21 information service using the schema query capability described in Section 8.5.3 without any reprovision of such extended schema. The URL of the extended schema can also be obtained via the schema URL query capability described in section 8.5.3. Alternatively DHCP may be used for finding out Cthe URL of extended schema. The extended schema is defined as an extension of the basic schema and includes data structure and relationship of media-specific or higher-layer information. In that sense extended schema is the complement of basic schema. An extended schema may be automatically generated from various of media-specific or higher-layer MIB definitions such as 802.11 MIB, 802.16 MIB and TCP/IP MIB-II. Figure 8-3 below shows an example graphical representation of the 802.21 MIIS bD basic schema in which 'Network' 'MII', 'MDI', 'PoA', 'NAS-Port-Type', 'Location', 'Operator', 'Cost' , 'Geo-Coordinate' and 'Enterprise-Number' are represented as class, while all others are properties of classes. The lines indicate either the range or domain of a property or a sub class of a class. In particular 'r' represents the range of a property and 'd' represents domain of a property. 'Domain' defines the class that a particular property belongs to and 'range' defines a type of a Eparticular property. "cA- Some description is needed as to how extended schema can be created. - Use of DNS query for finding the FQDN part of the location of the extended schema is not useful because it does not tell the entire URL of the extended schema. Instead, use of DHCP might be better to tell the URL of the extended schema. - Since Figure 23 needs to be revised, the corresponding explanatory text in section 6.3.3.1 should be revised as well. 2005/09/21^technicaliWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WրWցWւWքWօWֈW֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֡W֢W֣W֤W֥W֦W֧W֨W֩W֪W֫W֬W֭W֮W֯WְWֱWֲWֳWִWֵWֶWַWָWֹWֺWֻWּWֽW־WֿWWWWWWWW˃̃̓΃WWӃԃՃWWWWWWWWWWWWWWWWWWWWWWWWWWWWW (bintroductionWintroductoryWinversefunctionalproWinvolvedֶWirrespectiveWisֶWֹWּWWWWWWWWWWWWWWWWWWWWWWWissuedWWWitֹWWWWWWWitsWkWkbpsWkeyWknowledgeWl2Wl3Wl3mpWlabelWlacWWlanguageWWlaresWlatitudeWlayerWWWWWWWWWWWWWWlayersWWWWlciWleastֹWlengthWWlikelyWWlineWWWWWWWWline10WlinesWWWWlinkֶWֹWWWWWWWWWWWWWWWWWlink-specificWNbamendmentsWamongWanֶWWWWWWWWWandֶWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWand/changesWanexWannexWWWWWanotherWanyWWWapplicableWappliedWappropriateWareWWWWWWWWWWWWareaWasWWWWWWWWWWWascendingWassignWassignedWWWauthenticationWWautomaticallyWavailableֶWWWbasedWWWbasicWWWbeֹWWWWWWWWWWWWbeforeWWWbelongWbelongsWWbelowWWWWWWWWW9bmessageWWmessagesWWmethodsWWmgmtWWWWmibWmib-iiWmicsWWmiesWWmightWmihֶWֹWWWWWWWWWWWWWWWWWWWWWWWWmihhandoverprepareresponseVmih-activeֶWmih-relatedֶWmihbaseWWmihfWWWmiiWWWmiisWWWWmincardinalityWminimumֹWmininclusiveWmobileֹWּWWWWWmobile-nodeֹWmobilityWmodeWmodelWWWWWWmodifyWWWWWWtpage74line13Vmodifythe11throwintable14asindicatedbelowVmoduleWmoreֹWWWWmostWWmostlyWmoveWWmovetheintroductorytextandfigureofsection6.3.1toanVmsdusWmsecsWW0zsbcompletelyWWconfigurationWWconfigureWconnectWconnectionsWconnectivityWWconsistencyWconsistentWconsistsWcontainWWWWcontainsWWcontentsWcontributionWWWWWWWWWWcontrolWWWcontrolledWcontrollerWcoordinateWcorrespondingWWWWWcostWWWcouplingWcoversּWcurrentֹWWWWcurrentlinkidentifiecurrentlyWdWWd00-02WWWACbdata@zdecision@defines@8depending@:difference@~enterprise@entries@Yfollowing@handover@handovers@@includethetextandfigurefromsection3ofdocumentnumbe@`informationrequestse@instance@ introduction@links@(measurement@9message@modifythefollowingtext@multiple@Jnetwork@on@ only@uparameter@positions@queryresourselist@nreference@replacecurrentsection5.3.2bythesection5.3.2indcn21@greplacetextstartingatline10ofpage116andendingatl@reports@/request/response@sdo@_source@subsectionsuch@termination@ this@ttransport@!values@Sweb@where@xx@{>6csincegniandhliaremergedintomiithistableforhliisVsincemihnetworkaddressinformationresponsecancarryrouVsincethebasicschemausesowlinadditiontordfschemaaVsinglerW֩W֪WsitsmWslalistWsmeWWsomWnW֓WWsome֟WֱWִWWWWWWWWsomedescriptionisneededastohowextendedschemacanbeVsource֩WspecWspecificuW֍W֎W֖WWWWWWspecifictoonetechnology֖Vspecification~W֣WspecifiedWspecify֨WWWspecifying֧WspeedWstackqWrWstandardWWWstandardsWstateWWstatesWstaticWstatusWWstepoWstoreWRE YoshihiroFOhba^Technical, Non-binding_47a6.3.3.1boReplace Table 23 with the one described in Section 2.4 of 21-05-0346-0000_Supplement_D00-02_Ohba_Yoshihiro.doc.cIFigure 23 should be updated to be consistent with the revised basic set. 2005/09/21 Figure 23E YoshihiroFOhba^Technical, Non-binding_89`27a 7.4.14.3.1bAReplace text starting at line 27 of page 89 and ending at line 42 of page 90 with: " A new InfoQueryFilter type "FILTER_INFO_DATA" is defined. When this InfoQueryFilter type is specified, the InfoQueryParameters must be a string which contains a SPARQL (Protocol and RDF Query language) query [2] where the SPARQL query is supposed to contain an appropriate query for obtaining expected RDF/XML data. The MIH_REPORT of the corresponding MIH_information.response must be a string which contains bB a SPARQL query result [3]. An example query request and response when FILTER_INFO_DATA is specified as InfoQueryFilter to obtain a list of poa-id's of neighboring 802.11 point of attachments (i.e., BSSIDs) at a given PoA is shown below. QueryParameters: PREFIX mihbase: SELECT ?poa-id WHERE { ?x1 mihbase:neighboring-poa ?x2 . ?x2 mihbase:poa-type 19 . ?x2 mihbase:poa-id ?poa-id . ?x1 mihbase:poa ?x3 . ?Cx3 mihbase:poa-type 19 . ?x3 mihbase:poa-id "001122334455" . } MIH_REPORT: aabbccddeeff 001122334455 0123456789ab "oc`The schema-based query example should be updated to be consistent with the revised basic schema. 2005/09/21E YoshihiroFOhba^Technical, Non-binding_116`10a Annex C.1bbwhereּWWWWWWWWwhetherWwhichWWWWWWWWwhileWWwillWwithֶWֹWWWWWWWWWWWWWWWWWWWWWWwithinWWwithoutWwwwWWx1Wx2Wx3WxmlWWxmlnsWWxsWxsdWWxsiW֞WW14֚WW16W2rW֣WWW21}W21-05-0359-00-0000W22WW23WW255W26W3֏WֶWַWָWֹWֺWֻWּWֽW־WֿWWW4WWW5W5.3.3֡WW5.6W6ֵWWW6.1.5W6.2.5.1֟W6.3.1W6.3.3.1W7WWW7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.4.10.2֭W֯W7.4.10.2.4֮W7.4.11.2.2W8.3W8.4WmbassociatedֹWatֹWWWWWWWWattachWattachedֹWattachmentֹWWWWattachmentsWattributeWaugmentedWauthenticatedWauthenticatesWauthenticationWWautomaticallyWavailableֶWWWWbWbaseWbasedWWWWbasicWWWWWbeֹWWWWWWWWWWWWWWWbeforeWWWbehaviourWbelongWbelongsWWbelowWWWWWWWWWbetterWbxxWxxxWyoshihiroWWWyyWzzWc1WWW1.2W10W11uW֕W֞WW14֚WW16W19W2rW֣WWWW2005W21}W21-05-0359-00-0000W22WW23WW255W26W3֏WֶWַWָWֹWֺWֻWּWֽW־WֿWWWWW3gpp/3gpp2W4WWW5WW5.3.3֡WW5.6W6ֵWWW6.1.5W6.2.5.1֟W6.3.1W6.3.3.1W7WWW7.2.12W7.2.13W7.2.14W7.2.15W7.2.16W7.2.17W7.4.10.2֭W֯W7.4.10.2.4֮W7.4.11.2.2W7.4.14.3W8.3W8.4WcthesubnetassociationisnotastepthatamobilenodeneceoVthetextcanbedescribedwithoutreferringtable7whichisVthetextshouldberevisedthatinformationelementsinbothVtheirzWthemWthenWthere}W֧W֬WִWWWWthereisaneedtoaddaninformationelementsetforusereִVthereisnomihboxassuchthathasbeendefinedtherefore}Vtherefore}WWWWWWtheseWWWWWWtheyWWWthing֨WthinkWthisnWpWrWuWvWxWWրW֍W֎W֏W֒W֕W֗W֙W֚W֜W֝W֟W֣W֤W֥W֧W֬WֱWWWWWWWWWWWWWWWWWWthisclassificationisnotconsistentbecause6.2.5.1alread֟V:abcd€€€€€€€#F Sreemanthula 2005/09/21 bAReplace text starting at line 10 of page 116 and ending at line 44 of page 112 with: " ]> Basic Schema for IEEE 802.21 Information Service This property contains a RADIUS NAS-Por;DbACEGIKMOQSUWY[]_ace^cAcAcAcAcAcAFbBcBF @a@ bCt-Type attribute value defined in http://www.iana.org/assignments/radius-types. This property contains an SMI Network Management Private Enterprise Code defined in http://www.iana.org/assignments/enterprise-numbers. 1 1 Network class has two properties, namely mii for media-independent information and mdi for media-dependent information. A distinct instanc bEe of this class must be assigned for each point of attachment. 0 Media-Dependent-Information class has properties that are specific to link layer or lower. The properties include data-rate. Any property can be added to this class in an extended schem bGa. Data Rate The data-rate property contains a maximum data rate of the link layer of the PoA in unit of Kbps. 1 0 0 0 1 0 1 0 1 0 1 0 2 PoA Neighboring Networks Neighboring PoAs Location of PoA Network Operator P Roaming Partners Cost Basic Higher Layer Characteristics UAM PANA Basic Higher Layer Characteristics Diffserv 0 1 This class has properties that indicate a location of PoA. The properties include geo-coordinate. Any Tproperty can be added to this class in an extended schema. 1 1 1 V 1 1 1 1 1 This class has properties that represent geographic coordinate. The format is based on the Location Configuration Information (LCI) defined in RFC 3825. 0 34 This property contains the latitude resolution. 0 3FFFFFFFF This property contains the integer part of latitude of the location. 0 34 This property contains the longitude resolution. 0 3FFFFFFFF This property contains the longitude of the location. 0 2 This property contains the altitude type. 0 30 This property contains the altitude resolution. 0 3FFFFFFF  b_ This property contains the altitude of the location. 1 2 This property contain`s the datum type. 1 1 This class has properties that represent a PoA. The properties are poa-type and poa-id. This property contains a RADIUS NAS-Port-Type attribute value defined in http://www.iana.org/assignments/radius-types. This property contains a link-specific identifier of PoA. 0 1 1 This class has prodperties that represent an operator. The properties are operator-id and operator-name. This property contains the name of the operator. "Ec.The basic schema definition should be updated. 2005/09/21E YoshihiroFOhba^Technical, Non-binding_122`48a Annex C.2bRemove Annex C.2 entirely.cfThe Basic Schema Representation in ASN.1 is not useful unless a schema-based query is defined for it. 2005/09/21E YoshihiroFOhba^Technical, Non-binding_123`47a Annex C.3bRemove Annex C.3 entirely.cThe extended schema representation in RDF/XML can be automatically generated from various lower-layer and higher-layer MIB definitions, and does not need to be described in this document. 2005/09/21E YoshihiroFOhba^Technical, Non-binding_132`24a Annex C.4bRemove Annex C.4 entirely.cThe ASN.1 representation of extended schema is not needed as it is not tied with a schema-based query language and should be removed. 2005/09/21E YoshihiroFOhbag/breplacetextstartingatline10ofpage116andendingatlVreplacetextstartingatline27ofpage89andendingatliVreplacethetextwithVreplacethetwoparagraphsstartingatline1ofpage47witVreplacesֹWreportWWRv`b10WW11W112W116W13W14W19W2WWWWWWWWWWWW2linksetuptimeoutV2.1W2.2W2.4W20WW21-05-0346-0000WWW21-05-0348-01-0000WW21-05-0359-00-0000WWWW21-05-0361-00-0000WWWWWW21-05-0365-00-0000-cW21-05-0370-00-0000W22W22-43W23WW27W3WWWWWWWWW37reservedV3.2W30W34W36W3825W39W3fffffffW3ffffffffW3gppWWW3gpp2WWW4WWWWWW41W42W44WW45W46WW47W5WWWW_bsourceWWWWsparqlWspecificWWWWWWWWspecificsWspecifiedWWspecifiesWWspecifyWspeedWstaWWWsta'sWstandardWWstandardsWstartingWWWWWstateWstationWstoreWstrengthWstrictlyWstringWWstructureWsubWsubclassofWsubpropertyofWsubsection~YbenterpriseWenterprise-numberWWentirelyWWWentitiesWWWWWWentityֶWWWWWWWWWnJbpositionsWpossibleWpppWWpre-provisionedWprefixWprepareWprimarilyWprimitiveWWWprimitivesֶWWWWWWWWprivateWprocedureWprocessWWWpropertiesWWWWWpropertyWWproposalWprotocolWWprovideWWWWprovidedWWprovidesWpurposeWpurposesWqosWWWqueriesWqueryWWWqueryparametersWqueryresourcelistWJ (bnetworkֹWWWWWWWWWWWWWWWnetwork-operatorWnetworksWWWWWWWnewֶWַWֹWּWWWWWWWWWWnoWWnodeֹWּWWnoiseWnon-freeWnonnegativeintegerWnotֶWWWWWWWWWWnoteWWnsertWnumberWWobjectpropertyWobtainWWWobtainedWWobtainingWobtainsWoccurWofֹWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWohbaWWWcthebasicschemarepresentationinasn1isnotusefulunlesVthedefinitionofthesetypeofeventsisnotclearandthesVtheextendedschemarepresentationinrdf/xmlcanbeautomatV8cbeWWWWWWWW^Technical, Non-binding_87`20a 7.4.14.1.2b- Remove text starting at line 20 of page 87 and ending at line 6 of page 88. - Move the contents of Sections 7.4.14.3, 7.4.14.3.1, 7.4.14.3.2, 7.4.14.3.3 to Section 7.4.14.1.2.cAll QueryFilterTypes and its usage defined in this section are not well-defined. Since we have another set of QueryFilterTypes for schema-based query in 7.4.14.3, why do we need all these QueryFilterTypes for schema-less query? 2005/09/21E YoshihiroFOhba 2005/09/21EQiaobingFXie^Technical, Non-binding_32`55a5.3bAhPlease see the companion document 21-05-0365-00-0000-communication_model_text.doc for detailed proposal.h@A  c -cnotWWWWWW,)canymoreWanywhere֚WapplicableWappliedWappliesWWWapplyWWarchitecturejW}WWarepW֏W֟WWWWWWWWWWWWWWWWWWWWWWarqWasmWrWsWtWzW}W֗W֩W֪W֬W֭W֮W֯WWWWWWWWWWWWWWWasnWWassociated֌WWassociationoWzWassumedWtachedִWֵWattachmentֹWautomaticallyWavailableWavoidWbasedxWWWbasicWWWWWWWWWbejWmWnWwWxWzW~WWրW֌W֕W֗W֙W֠W֣W֥WֱWִWWWWWWWWWWWWWWWWWWWWWWWWWWWWW'cneednotdetectionֆVneededִWWWWWWWneeds֕WWWWWneighborWWneighborhoodWneighboringWWWnetworknWyW֗W֠W֦WWWWWWWWnetworksWWnew֔WֵWֶWַWָWֺWֻWֽW־WֿWWWWWWWnewsentencesincethemaydraftok֔Vno}W֧W֫W֬WWWWnoneedtohavesuchadescriptiveintroductioninsection6VnodeoWּWnotjWkWmWoWpWqWrW|W}WցWքWֆW֍W֎W֏W֓W֗W֚W֟WִWWWWWWWWWWWWWWWWWWWW6EQiaobingFXie 2005/09/21ESrinivasF Sreemanthula^Technical, Non-binding_60`31a7.2.13bWRequest to remove section 7.2.13 and 7.2.14 and respective entries in the event tables.cLink_SDU_Transmit_xxx primitives are used to notify the transmission status of fragments, but these primitives are already supported by respective MAC layers (e.g MA.UNITDATA.xxx in 802.11). Therefore, will be redundant functionality in 802.21. 2005/09/21ESrinivasF Sreemanthula^ Editorial_34`55a6.1.6bAAdd another table for MIH events or list MIH events in the Table-1. Add a column for both tables to mark which are local, remote or both. make corresponding additions and/changes in the event message descriptions for MIH_Event_XXX and Link_Event_XXX and their respective parameters.cvents are classified as MIH events and Link events and are defined as primitives across different layers. However, only link events are defined. If it is assumed that Table-1 is also cAAt the last 802.21 face-to-face meeting, a proposal was made to add a top-level communication model to section 5 that would serve the purposes of showing the communication relationships among different MIHF entities. To further explore the idea, a 802.21 communications model Ad-hoc Meeting was held on July 19, 2005 at the meeting. There was general consensus from that ad hoc meeting that a communication model diagram and some text to explain the relationships would be very useful to enhancBe the architecture discussion in the spec. The present contribution is to propose such a communication model diagram and new text. q@A   2005/09/21yqiaobingandreaajayperetzֻVּVVqiaobingandreaperetzajayֹVqiaobingpererzandreaajayֶVַVָVֺVֽV־VֿVVronny׃؃كڃۃ܃݃ރ߃srinivassubirÃăvivekɃʃ˃̃̓΃σЃу҃ӃԃՃwolfgangƃǃyoshihiro_ i0jkl@mnoq`pprstuֶַָֹֺֻּֽ־ֿv‚#wx‚$yz‚%{|}~‚&ƒ‚'ր‚(ցւփքօֆև‚)ֈ‚*։֊‚1֋̃‚2֌֍‚4֎‚5‚6֏֐΃‚7֑֒‚8֖֓֔֕‚9֘‚Aֵ‚B֗‚C‚D֚֙‚E֛‚F֜֝‚G‚I֞‚Jִ֟ÂR‚S֠Ӄ‚T‚U‚V‚W֡‚X‚Z֢փ‚f֣֤֥‚i‚j‚qۃ‚s܃‚u‚֧‚‚֦‚֪֨֩֫֬‚‚‚֭‚֮֯‚‚ְ‚ֱ‚‚‚‚ֲ‚‚‚ֳ‚Ã"pÃ#Ã#0Ã#@Ã$0Ã%P` ԃՃ׃؃@֘kփք֣‚%֨`p։֓֟ywo‚!jցւְ‚"ʃ‚#kփք֣‚%֨܃‚& ]cALink_Event_Handoff_XXX primitives are defined to indicate the status of the handover but look like L2 handover signaling mechanism (which is outside the scope of 802.21). When a L2 handoff mechanism is present, the MAC protocol will already support equivalent signaling to indicate the status. In any case, the status of the handover are can be obtained directly from the other link events currently defined e.g. link_up, link_going_down and link_down. 2005/09/21ESrinivasF Sreemanthula^Technical, Non-binding_71`57a7.4.8.1bAThere are 3 ways to solve this. i) Modify Cmd.Configure to indicate the type of parameter and the corresponding threshold value and add to the table. ii) define a new command iii) Extend some other event.register to carry this information when registering for the parameter_change.cries in the event tables.^bindingiWjWkWlWmWnWoWpWqWrWsWtWuWvWwWxWyWzW{W|W}W~WրWցWւWքWօWֈW֊W֋W֌W֍W֎W֏W֐W֑W֒W֓W֔W֕W֖W֗W֘W֙W֚W֛W֜W֝W֞W֟W֠W֡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ֳWִWִWWִWִWִWִWִWֳWִWִWWִWִWִWִWWִWִWִWִWִWִWִWִWֳWִWִWWֳWִWִWִWִWִWֳWִWִWִWִWִWִWִWִWWִWִWִWWֳWִWִWֳWִWִWִWWִWִWִWLcthebasicschemarepresentationinasn1isnotusefulunles@theinfrastructureisalsointhepositiontohaveoverallv@thesubnetassociationisnotastepthatamobilenodenece@thiscouldbeperformancedestructivefortheterminalince@through@toֶtobetakenoutofthespecification@updatereferencediagramanddescriptionfor802.16@%utilizes@weshouldbecarefulonusingthewordarchitecture802.21d@whatdoweexactlydefinebyhandoversignalingisittheex@which@ad‚b֛japplication/layer@connectivity@different@event@information@is@specify threshold values for different parameters. It is not clear if the MIH_Configure and Link_configure command primitives are to be used for this purpose. But the`6a2220 2005/09/22EP802-21-D00-01.pdf^OZcrequest/responseWWWrequestedWrequiredֹWּWWWrequirementsWresourceiWWresourcesWresourcestatusWrespectiveWresponse֭W֮W֯WWWWWWresponsibleքWrestWrestrictionWrestrictiveWresultWrevisedWWWWWrlcrW֛WrncցWrouterWsWsamesWtWyW֨W֭W֮W֯WWWWsameaspreviouscommentsVtVsap֌W֍W֎W֒WWWWWWsapsWWWrequestthatanewparametertocarryabasicinformationelVrequestthatanewparametertoindicatethetypeofparametVrequesttoremovesection7.2.13and7.2.14andrespectiveeVrequesttoremovesection7.2.157.2.16and7.2.17andrespeVrespectiveWWWsectionWWsolveWtableWWWtable-1WtablesWWWbceachWWWeavesdroppedzWeciֵWeffectWeitherWWelement֠WִWWWelementsWWWWelsewhereWenablerslWenablingWenhanceWWenoughpWWentireWentitiesWentity։WequallyWequipementsִWequivalentWerrorWes/csִWessentialmWestablishingWetcWethernetWevenzWքWevenaftersecureassociationtheeventscommandsandinformzVeventքW֚W֜W֝WWWWWWWWWeventszW֗W֛WWWWWWWWevery֤Wexactly{W;hcformatWWWformatsWfqdnWfragmentsWframes֍W֎WfreshnessWfromքWօW֗WWWWWWWWWWWWWWfullWfuncWfunctionmWWWWWWfunctionalitiesjWfunctionalitymWWWWWfurtherֹWּWWgWWWWWWgeneralWWWWWWgeneralnetworkinformationgniandhigherlayerinformationVgenerallynWgeneratedWWWgeneric֕WWWgivenWWgniWWgooWrWgoingWWgreaterWgroupsWhandwWhandoff{W֜W֝WWWWhandoverwW{W֧W֬W֭W֮W֯WWWWWWWWWWWrespectiveWWWsectionWWsolveWtableWWWWtable-1WtablesWWWC^non-bindingWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW Wall W W Woverlapping W W W W W W W W W W WngWremoteWremoveWWWrequestWWWWWrequestthatanewparametertocarryabasicinformationelVrequestthatanewparametertoindicatethetypeofparametVrequesttoremovesection7.2.13and7.2.14andrespectiveeVrequesttoremovesection7.2.157.2.16and7.2.17andrespeVrespectiveWWWscenario WsectionWWshouldWshowWsolveWsomeWWsomehowWtableWWWWtable-1WtablesWWWW}ctheasn1representationofextendedschemaisnotneededasVthebasicschemadefinitionshouldbeupdatedVonding effect._For remote MIH commands in Table-3 that are bi-directional, the correspongin "Effect of Receipt" section must reflect which scenario is considered e.g mobile generated or network generated. This is important since not all commands are supported by the ter`8a2224 2005/09/22 tation formats. In the first table some commands are both local and remote. In the second table, we hare remote commands. `7a2221 2005/09/22 EP802-21-D00-01.pdf^nNeed explicit text defining the scenario (mobile generated or network generated) and the corresponding effect._For remote MIH commands in Table-3 that are bi-directional, the correspongin "Effect of Receipt" section must reflect which scenario is considered e.g mobile generated or network generated. This is important since not all commands are supported by the ter`8a2224 2005/09/22  cADuring the exercise of L2 requirements, it was realised that some link types are able to provide some basic information elements either in the broadcast or by specific query mechanism. This information is beyong a simple MIH-capability flag. When this information is obtained in the MAC layer at the link detect phase, the primitive Link_Event_Detect and MIH_Event_Detect must have means to support the information elements. 2005/09/21ESrinivasF Sreemanthula^Technical, Non-binding_59`41a7.2.12.1bfRequest that a new parameter to indicate the type of parameter that has changed is added to the table.cThe parameters table must include the type e.g. bandwidth, QoS etc of the parameter that has changed in addition to just providing old and new values of the parameter. 2005/09/21ESrinivasF Sreemanthula^Technical, Non-binding_62`14a7.2.15b_Request to remove section 7.2.15, 7.2.16 and 7.2.17 and respective entries in the event tables.cucatWWWWatthelast802.21face-to-facemeetingaproposalwasmadeVattachedִWֵWattachmentֹWWattentionWautomaticallyWavailableWWavoidWbWbandwidthWbasedxWWWWWbasicWWWWWWWWWWbejWmWnWwWxWzW~WWրW֌W֕W֗W֙W֠W֣W֥WֱWִWWWWWWWWWWWWWWWWWWWWWWWWWWWWW Wswitch WtableWtablesWWWWWWch Wswitch WtableWWtablesWWWWWWWWWWWWWWWWWWWWWWtable-1WtablesWWWWWWWWW 8cARequest for a consistent form of event and command definitions. 802.21 Events are classified as MIH events and Link events and are defined as primitives across different layers. However, only link events are defined. If it is assumed that Table-1 is also applicable to MIH events then it would be clear if it is explicitly state. Also a consistent notation for the two types of events is requested e.g. Link_ Event_XXX and MIH_Event_XXX. Also request to add a column in the tables to mark whiBmch of Link_Event_XXX and MIH_Event_XXX are local, remote or both. Also applies to discovery and registration.[ 2005/09/21T1ESrinivasF Sreemanthula^Technical, Non-binding_59`11a7.2.11.1bbRequest that a new parameter to carry a basic information element is added to the parameter table.cnnectivity." iii) Section 1.2, b) 3) un/_brequest/responseWWrequestsWrequestsourceWrequiredֹWWWWreservedWWresideWresolutionWresoucestatusresourceWresourcestatusWrespectiveWWWresponseWWWWWresponsesourceWWrestrictionWresultWWWWWWresultbitmapindicatestheresultoflinksetupprocessVresultsWretrievedWrevisedWrfcWricherWrightWroamingWWroaming-parnersWrouterWWrowWrrcWWsameWWsapWWWWWsapsWWsatisfiedWsaysֹWscalabilityWscanWscanningWscenarioWWscenariosWWWWschemaWWWschema-basedWschemalocationWscopeWWokcoveralliWWWoverlapWoverlappingWowlWpacketWpackets֌Wparameter֥WWWWparametersWWWpartֱWWperformքWperformancenWperspectiveWphaseWphyrW֛WWpleaseִWֵWpoa֫WWWWWpoasWWWpointքW֧W֬WֹWpointsWWpolicyxWpoll֨WpositioniWpossible֧WWpowernWprecisepWprecised֙WprepareWWpresentWWWpresentationWpreventօWprevioussWtWprimitive֦W֩W֪WWWWWWWWWW cA`According to definition in 7.2.12 Link Parameters Change utilizes a separate command to specify threshold values for different parameters. It is not clear if the MIH_Configure and Link_configure command primitives are to be used for this purpose. But the current parameter list in the primitive do not support the parameter type and threshold values. ` 2005/09/21ESrinivasF Sreemanthula^Technical, Non-binding_38`46a6.2.5.1bA@We request to merge the two tables and provide a consistent format and remove any ambiguity. Also request to add a new information column to clearly show which commands are unidirectional and bidirectional. Also, if some commands have somehow a different meaning /behaviour on the two directions, it should be explained.@cTables 2 and 3 are MIH commands for local and remote purposes with different presentation formats. In the first table some commands are both local and remote. In the second table, we hare remote commands. JGbmodifythefollowingtextVmodifythetextpage74line13Vmodifythe11throwintable14asindicatedbelowVmoduleWmoreֹWWWWmostWWmostlyWmoveWWmovetheintroductorytextandfigureofsection6.3.1toanVmsdusWmsecsWW%cutilizesWvalueWWvalueoflinkparameterWvaluesWWvariableWvariousWWWversionWveryWWWWviewքWviewsrWvisibilityiWvocabularypWwantքW֧WwasWWWWwejWrW{W֣W֤W֧W֨W֬WWWWWWWwealreadyhavemihpollwhichdoesthesamething֨Vweneedtospecifythedifferencebetweenthetwo֨VcthroughoWWthusWtiedWtimeWtitle֚WWtlvWtoiWmWoWpWrW|W~WWրWցWքWօW֌W֍W֎W֕W֖W֙W֠W֣W֨W֩W֪WִWֵWZT2 T3ESrinivasF Sreemanthula^Technical, Non-binding_76`1a7.4.10bnNeed explicit text defining the scenario (mobile generated or network generated) and the corresponding effect.cA'For remote MIH commands in Table-3 that are bi-directional, the correspongin "Effect of Receipt" section must reflect which scenario is considered e.g mobile generated or network generated. This is important since not all commands are supported by the terminal. The current text reads ambiguous.'@A  33 2005/09/21ESrinivasF Sreemanthula^Technical, Non-binding_39`26a6.2.5.3bComment 9.1: Need to verify if handover commit is not overlapping with MIH switch. If so, request to merge the primitives. Comment 9.2: Validate the usage scenarios of handover complete and remove it, if not useful.c 2005/09/21` <binformationrequestseWinformationresultsetWinformationxxWinfrastructureWinitiateWWinsertWWWWWWWWWinsertthefollowingtextatline58ofpage46Vinserttheparameterresourcestatusinsubsection7.4.11.2.2Vinserttheparameterresultinparametersof7.2.7Vinserttheparametertimedifferenceinsemanticstableof7.Vinserttypecolumninalltablesinthe8.4sectionfollowinVinsertvalueoflinkparameterasoneofparameterspage59linV,scallqueryfiltertypesanditsusagedefinedinthissectionaVallowWWWalready|W֟W֡W֨WWWWWalreadydescribedinsection5.3.3֡ValsoiW֌WWWWalwaysmWzW֧WambiguousWWWamongWanjWrWցWօW֙W֚W֜W֝WִWWandzW֍W֎W֏W֠WֵWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW cA[Comment 9.1:MIH Handover Commit is not defined in the primitive description. Based on current understanding the Handover Commit has overlapping functionality with MIH-Switch. Comment 9.2: Not clear of MIH Handover complete is useful. We see significant overlapping with current L3 handover signaling. This may be redundant from 802.21 perspective.[@A  33 2005/09/21T3ESrinivasF Sreemanthula^Technical, Non-binding_76`1a7.4.10bQAdd an optional parameter "QueryResourceList" into MIH Handover Initiate request.cAIMIH Handover prepare request and response primitives are capable of querying for required resources for the handover. However, it is not clear based on what information the resource query is generated. It is be beneficial to provide that information to in the Handover initiate request primitive when generated from the terminal.I@A  33 2005/09/21ESrinivas2ccapturedWcarefuljWcarriedִWcarryWcaseWWWWWcasesWWcauseWcellWcellularnW֫WcertainֵWcertainlyrWchangeքWWWWF Sreemanthula^Technical, Non-binding_83`15a7.4.13b^Request to reconsider the use cases for MIH network information and remove them if not needed.cAMIH Network Address Information request and response primitives seem to have the same functionality already defined for fast mobile-ip handover signaling. This may cause some redundancy in 802.21 definitions.@A  33 2005/09/21ESrinivasF Sreemanthula^ Editorial_1`40a1.2bAi) In section 1.2, purpose is not only to enable better user experience but also to enable network controlled handoff ii) Modify the text along the lines of "The mobile terminal is well-placed to detect available networks and make decisions about connectivity. The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists and the location of mobile devices, and to make decisions about mobile terminal connectivity." iii) Section 1.2, b) 3) un bBder IS The mobile terminal obtains information from the repository using its current network points of attachment. Must be changed to allow also MIHF in network to access info cAThe introductory/overview/purpose section must describe all the possible objectives of the work scope within 802.21. In this regard, while the rest of the document discusses about how network controlled handovers are possible, it is important that the introductory sections make explicit references to them. These scenarios are very important for the 3GPP/3GPP2 operators to provide attention to the 802.21 workscope. i) The introduction states that "The purpose of the IEEE 802.21 standard is  cBto enhance user experience of mobile devices by supporting handovers between heterogeneous networks." This is a restrictive description. The text does not convey the more generic set of scenarios 802.21 aims at enabling. ii)The text states that "The mobile terminal is well-placed to detect available networks" and "The network infrastructure is well-suited to store overall network information, such as neighborhood cell lists and the location of mobile devices." This conveys the incorrect meCssage that the network is used only as reposiroty for information, therefore only for IS, and that the 802.21 standard does not consider scenarios where the network can control the handoff. iii) Section 1.2, b) 3) under IS The mobile terminal obtains information from the repository using its current network points of attachment. is terminal-centric and restrictive. Should also allow network side to fetch this info.@A  33 2005/09/21ESrinivas@DbhandoverWWWWWWWWWcterminologyuWtextzW֭W֮W֯WWWWWWWWWtextisthatsameasin7.4.10.2mihhandoverinitiaterespo֭V֯Vtextisthatsameasin7.4.10.2.4mihhandoverinitiateres֮VthanWthatmWnWoWwW{W}W֟W֤W֭W֮W֯WִWWWWWWWWWWWWWWtheiWjWmWnWoWqWrWwWyWzW{W~WցWքWօW֌W֍W֎W֏W֔W֕W֗W֙W֚W֤W֥W֦W֧W֨W֩W֪W֫W֬WֱWִWֵWֹWּWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWoj|Original Text: (i.e., with the type of the serving and target point of attachment and the respective subnet associations). v%Submit again with correct Page numberwRejected 2005/09/21 2005-09-14pE Eric NJEDJOU^Technical, Binding_5`41a2.1cpThis reference is not adapted to IEEE 802. IETF vocabulary is not precise enough when link layers are consideredd8j%define a more appropriate terminologyvNo specific text changewRejected 2005/09/21 2005-09-14qE Eric NJEDJOU^Technical, Binding_3`55a1.3cANot accurate Again what is the mobility management protocol stackd7jA&Original Text: This information typically originates at lower layers of the mobility management protocol stack, within the MN or other network elements. Proposed Text: This information typically originates at differents layers of the protocol stack, within the MN or other network elements. &mAccepted 2005/09/21 2005-09-14rE Eric NJEDJOUvnospecifictextproposedrVsVtVuVwVzV{V֍V֎V֒V֓V֕V֖V֗V֙V֚V֛V֜V֝V֞V֟V֡V֣V֥V֦V֧V֨V֫V֭V֮VnotօW֌W֏W֏Wr~WproposedrWsWtWuWwWzW{W֍W֎Wre-submit~Wre-submitwithproperfields~VreplacedyWscope|WselectingyWselectionyWshouldyWspecificpWrWsWtWuWwWzW{W֍W֎WsubmitoWsubmitagainwithcorrectpagenumberoVtextpWrWsWtWuWwWyWzW{WօW֌W֍W֎WtextnotavailableinthenewversionօVtheyWօWthisyWtimeyWto}Wupdated֌WuseryWversionօWwithoWyW~WցWworkցWworkwitheditorցVwacceptedւփaccepted-modifiedvy}ցrejectedoprstuwxz{|~քօֈ֊֌֍֎€vanyyWappropriateyWarchitecture}WatyWavailableօWbeyWWWchangepW}Wchangearchitecturetoframework}Vcheck։Wcheckforconsistency։VcommentsWWconsistency։WcorrectoWdefer֠Wdefertoinformationelementtableredefinition֠VdefinitionyWdeletevWdeletedetectedvVdetectedvWdiscussonWWeditorցWֆeditorialրelement֠WemptyŃǃentityvWfields~Wfigure֏WforyW։Wframework}WfromWWgivenyWinօW֌Winformation֠WisyWlaterWWoned֏WmostyWnetworkvWyWnetworkselectionistheprocessofselectingthemostapproyVnewօWnopWrWsWtWuWwWzW{W֍W֎W֒W֓W֕W֖W֗W֙W֚W֛W֜W֝W֞W֟W֡W֣W֥W֦W֧W֨W֫W֭W֮WnospecifictextchangepVzcEven after secure association, the events, commands and information messages can always be eavesdropped as long as their content travels the air interface in clair textd18vNo specific text proposedwRejected 2005/09/21 2005-09-14{E Eric NJEDJOU^Technical, Binding_14`37a5.2cWhat do we exactly define by handover signaling? Is it the exhange if MIH information that determine wether a handoff is imminent?d19vNo specific text proposedwRejected 2005/09/21 2005-09-14|E Eric NJEDJOU^Technical, Binding_14`37a5.2cIf i would like to transition between two links I won"t use already existing messages because intra-romaing messages were not dedicated for inter-system d20j}ֆ 2005-09-14ևE Eric NJEDJOU^ Editorial_17`27a5.4.1cReplace with "upper layers" d31jReplace with "upper layers"  2005/09/21 2005-09-14ֈE Eric NJEDJOU^Technical, Binding_18`24a5.4.3d32wRejected 2005/09/21 2005-09-14։E Eric NJEDJOU^ Editorial_19`6a5.4.3c+Again replace with HLE =Higher Layer Entityd33jLReplace Higher Layer Mobility Protocol (HLMP) with Higher Layer Entity (HLE)vCheck for consistency 2005/09/21 2005-09-14֊E Eric NJEDJOU^Technical, Binding_19a5.5d34wRejected3 2005/09/21 2005-09-14ֵ@cַb ֹbA jA ֻiֽccbAC@@bAC@`$bB&D'bA)C*@+bA.b1bA3C4E5G6cA7bA