Standard Jet DBnb` Ugr@?~1y0̝cßFNj7՜]('`{6n߱eCT>3y[ $|*J|C1 f_Љ$g'DeFx -bT4.0BWN%%`Y Y DataIDdmn%YAOIndexCommentSuggestedRemedyResponse SubclauseText50 {\}eOhW{\}eOhW{\}eOhW?hI2")}RJBh9b!nK¯? fFinalReports afDBO(XդOhWkWKhDESTդOhW ClauseListcmdWEBasciiReportcmdFancyCommitteeReportLabel16cmdEditorsASCIIReportcmdSummaryReportLabel22cmd_tildereportLabel26cmd_StatusReportLabel28TypeListLabel9cmd_StatusReport_ClickcMeasurecmd_tildereport_ClickcmdEditorsASCIIReport_ClickcmdSummaryReport_ClickcmdWEBasciiReport_Click cASCIIReportb:?QN)!HcmdFancyCommitteeReport_ClickcSummaryReport  4SELECT * FROM ClauseList ; ClauseList CHECK 6WHERE ResponseStatus = "O"  NoWritten rWHERE CommentStatus In("X","D") AND ResponseStatus = "W"  NoAction 2WHERE CommentType = "TR" rFoO I nAND CommentStatus In("A","R") AND ResponseStatus = "W"  NoSig 2AND ResponseStatus = "U"  TRproblem zWHERE ((CommentType = "TR" AND ResponseStatus In ("C","Z")) ! ~OR (CommentType <> "TR" AND ResponseStatus In ("C","U","Z")) + OR (CommentType <> "TR" AND ResponseStatus = "W" AND CommentStatus In("A","R")))  Done ,Record counts complete StatusReport ,ClauseList <> "CHECK"  ALL  AND Clause In( ) 4SELECT COUNT(*) AS rcount  FROM Main  bcMeasure: horrible error, could not count records rcount Summary DPlease select from the Clause List TypeList @Please select from the Type List zChecking for records that don't match any known clause number fHoundDogging Committee report rIsNull([Clause]) OR [Clause] Not In ("00","01","02","03",, "04","05","06","22","30","30A","30B","31","31B","34","35","36","36A","36B","37","38", N"38A","38B","38C","38D","39","41","42") 4WEB Ascii report generator TPreparing to print report for all clauses 2SELECT * FROM Main WHERE  BNo Comments Match Search Criteria AND  2Ready t"@>@` @r E? Yj0S  Y   Y sY  Y Y  Y  ]Y  Y  V Y  Y  Y ] Y ]V Y 2VY  Y  ] Y  Y ConnectDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeIiimmmiCmEmYYIdParentIdName         G1@ĿD`̿ P1TypeList      d   hÿ Ŀhÿ Ŀhÿ dĿhÿ ĿhÿP1hÿ$hƿ ƿ ƿ ƿ TypeListCommentSubjectHeaderPĿhÿ +ƿ ƿ ƿ hÿ @hÿ @hÿ d@hÿ @hÿhÿ$ 4 P/ $ ɿpɿ  p̿p̿hÿ$    d   hÿ$ stͿͿhÿte4hÿP1hÿ$@ֿ@ֿ $      d  d  d    daOYP Settings\alSY Y Y  Y 2moACMFInheritableObjectIdSIDmeCWNst3c OMEDYObjectId        &'()*+,-. / 0 1 2 3456789:;<=>?@ABCDE F!G"H#I$J%K&L'M(N)O*P+Q,R-S.T/U0V1W2X3Y4Z5[6\7]8^9_:`;a<b=c>d?e@fAgBhCiDjEkFlGmHnIoJpKqLrMsNtOuPvQwRxSyTzU{V|W}X~YZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-. / 0 1 2 3456789:;<=>?@ABCDE F!G"H#I$J%K&L'M(N)O*P+Q,R-S.T/U0V1W2X3Y4Z5[6\7]8^9_:`;a<b=c>d?e@fAgBhCiDjEkFlGmHnIoJpKqLrMsNtOuPvQwRxSyTzU{V|W}X~YZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~     /U0V1W2X3Y4Z5[6\7]8^9_:`;a<b=c>d?e@fAgBhCiDjEkFlGmHnIoJpKqLrMsNtOuPvQwRxSyTzU{V|W}X~YZ[\]^_`abcefghijklmnopqrstuvwxyz{|}~ YSY  Y Y Y  Y  Y Y  Y AttributeExpressionFlagLvExtra Name1 Name2ObjectId Ordernzf edY"ObjectIdAttributeRoot EntrysM @&VBA@QYVBAProjectCA@pCLtVBA@pCLt 2   !=u /01CD6789:;<=>?@BIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghiS wxyz{|}~Root EntryGS @&VBA@QYVBAProjectCA@pCLtVBA@pCLt 2  E=C D6789:;<=>?@BjIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghilS mnpqrstuwxyz{|}~YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE: PROJECTB/PROJECTwmOaAcessVBADataaDirData*PropDataReports@ϗ(0                          ! " # $ % & ' ( ) * + 0 > / 3 = 4 5 6 7 8 9 : ; < ? G Q @ A B C D E F H P I J K L M N O R \ o S T U V W X Y Z [ f h ^ _ ` a b c d e  -YSY Y Y  Y  Y  Y  Y  Y ccolumn grbiticolumnszColumnszObject$szReferencedColumn$szReferencedObjectszRelationship@ ;;;; ;;;; ;YYYszObject$szReferencedObjectszRelationshiph1`pabcicmd_prop_accept"ACCEPT""[Event Procedure](ڭ ڭ лڠ лڭ ڭHk5`ab>cfi$"Option_ViewWindow1"[Event Procedure]i2` aOption177d5`abWceLabel178Commenti2`aOption179d5`pabdceLabel180SuggRemedyi2`\aOption181d5`BabceLabel182Responsek125`abci($option_status_mode2i2W`ha(Option194d5`Na bVcLabel195proposaCustomGroupsDataAccessPages 12pX(pe(Blob  Main.ClauseMain.SubclausePageLineMain.CommentTypeSuggestedRemedyResponseCommentStatusResponseStatusTopicCreateDateLastModDateDispatchDateWrittenDateAccept_RejectDate Closed_UnsatisfDate!VoterStatusResponse_LabelRe087:<=Babc$e gMain.CommentID@νt3@_GetAllComments_GetA A 2   i % 0:=Babc;e gRh<ij+kD([CommentType] In("TR", "T", "E"))+e@MainMainTable Arial8l|)h Brother HL-1440 seriesH CdX%bN   : k & W  C T  @q# $ % & ' ( ) , - . / 0 1 2 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R T  V W X Y Z [ \ ] ^ _ ` a b c d e f g h * k l m n o p q vs t u v w x y z { | } ~  D6 D ,rU H$` $A`P(`0A&nn ,:]4)xd`6<,rU  Aq@4 A I@8Y  ppp @ <aarrr[W<  $  d0+:h%x$ `x ,x0$  xT x$ @  f x$ `x TxH $ ! "xhTd0   488@5hH$  "xhTd0   488 hh!ppx"(&v @  @    @@ @@ @ @ SOYkfJmMWSSYbJ^iQfdimkSWdobOOdUUYbUSYbfomS`JYbSfYMmoiQ8SfYMmoiQ86SfYMmoiQ88SfYMmoiQ8:SfYMmoiQ8<SfYMmoiQ8>SfYMmoiQ:SfYMmoiQ<SfYMmoiQ>SfYMmoiQ@SfYMmoiQB SfYMmoiQD!SfYMmoiQF"SfYMmoiQH#SidoUW$SkmJmokfdfof%kmJim&Md``dbomY^YmYQk'+UQmJ^^Md``Qbmk(+UQmJ^^Md``Qbmk8)LYUSdbmMd``YmmQQiQfdim*Md``QbmQiSo^^++Md``YmmQQiQfdim,WdmYmQ`k-bQs+qdmQ+Mdobm+Lv+Uidofy'bQs+qdmQ+Mdobm+Lv+Uidof8y(bQs+qdmQ+Mdobm+Lv+Uidof:y)iQfdimLvMd``QbmYO.idoUWY`fdimMWQM\iQfdim/kYUbJmoiQiQfdimkmJmokiQfdimko``JivmiMd``QbmQiqdmQibJ`QkqdmQikmJmok`Md``YmmQQiQfdimJO`YbOJmJJMMQkkfJUQkOJmJLJkQkSdi`k `dOo^Qk iQ^JmYdbkWYfkiQfdimk kMiYfmk kvkiQ^ mJL^Qk+UQmJ^^Md``Qbmk+kh+MSSYbJ^iQfdimk+kh+MM^JokQ^Ykm +kh+MSSYbJ^iQfdimk+kh+MmvfQ^Ykm +kh+MSWdobOOdUUYbU+kh+MMdbSYi`JmYdb^Ykm +kh+MSWdobOOdUUYbU+kh+MmvfQ^Ykm +kh+SSOYkfJmMW +kh+SS`JYb9+kh+SSidoUW+kh+iLYUSdbmMd``YmmQQiQfdim'+kh+iMd``YmmQQiQfdim+kh+iWdmYmQ`k+kh+iiQfdimLvMd``QbmYO+kh+iidoUWY`fdimMWQM\iQfdim+kh+ikYUbJmoiQiQfdim+kh+ikmJmokiQfdim+kh+iko``Jiv+kh+iqdmQibJ`Qk+kh+iqdmQikmJmokJff^YQO+QOYmky*M+kM+fU+^b8M^JokQ^YkmM^dkQQJbOmMd``QbmkMd``QbmQiSo^^++OYkfJmMWYbOQu`JYby`JYbdomfom `kvkJMMQkkdL[QMmk!`kvkJMQk`kvkY`QuMd^o`bk"`kvkY`QukfQMk#`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkbQs+qdmQ+Mdobm+Lv+Uidofy&bQs+qdmQk+bdy%bQs+qdmQk+vQky$idoUW$mQkmYbU:y1miMd``QbmQi%mvfQ^Ykm&qdmQ+Mdobm+Lv+UidofyqdmQibJ`Qk'qdmQikmJmok(qdmQk+bdy#qdmQk+vQky"JMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQOqdmQibJ`Qk`JYby4qdmQikmJmokqdmQibJ`Qky5mQikmJmokqdmQibJ`Qky5qdmQikmJmokqdmQibJ`Qky525]7a<bce Label1#m7U`ahb fkCommenterNameCommenterNamed5U7`<ahbdc Label3CommenterNamem7`a|)b fkCommenterEmailCommenterEmaild57`<a|)bdc Label5 Emailm7`a*befkCommenterPhoneCommenterPhoned57`<a*bdc Label7 Phonem7`a+befkCommenterFaxCommenterFaxd57`a+bc Label9Cell phonem7`a-b efkCommenterCoCommenterCod57`<a-bdcLabel11Companym7U`a<befk Clause Claused5U7`a<bcLabel13 Clausem7U`ahbdfkSubclauseSubclaused5U7`ah  @ @ @ @ @ @ @ @ @ @ @ @ @           !"#$%&' (!)"*#+$,%-&.'/()*+,-./01 2 3 4 5 789:;<=>?@ABCD%F8G9LyNy"Oy#Py$Qy%Ry&Sy'Ty(Uy)Vy*Wy1Xy4Yy51yD" !_#c$h&l'p(fghijmnruvwxyz{|}~TypeInfoCopy Form_fPIcture9P/3 Sub gofFinalReports_"CError GoTo_' Dim stDoBcAs Sng LinkCri=Babc0*e gh6i*j1kDispatch.MessageSubject鍫e@DispatchDispatchAriald2e12f5g237hgh MS Sans Serifi1ghj1ghk1l23:m4n2o2p5r35zij MS Sans Serif{5`DDetailm7U`<a<b e fEmailEmailm 27U` a<bcefkMsgBJ#      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIeNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ttttttttt t t t ttttttttttttt$t% t& t' t( t) t* t+ t, t- t. t/ t0 t1 t2 t3 t4t5t6t7t8t9t:t;t<t=t>t?t@tAtBtCtDtEtFtGtHtItJtKtLtMtNtOxxxxxxxxxx x x x x xxxxxxxxxxxxx x x x!x!x!x "x!"x""x##x$#x%#x&$x'$x($x)%x*%x+%x,&x-&x.&x/'x0'x1'x2(x3(x4(x5)x6)x7)x8*x9*x:*x;+x<+x=+x>,x?,x@,xA-xB-xC-xD.xE.xF.xG/xH/xI/xJ0{0{0{1{1{1{1{2{2{2{ 2{ 3{ 3{ 3{ 3{4{4{4{4{5{5{5{5{7{7{7{7{8{8{ 8{!8{"9{#9{$9{%9{&:{':{(:{):{*;{+;{,;{-;{.<{/<{0<{1<{2={3={4={5={6>{7>{8>{9>|?|?|?|?|@|@|@|@|A| A| A| A| B|B|B|C|C|C|D|<D|=D|>F|GF|HFFGGGHGIGJL[L\L]NdNeNfOgOhOiPjPkPlQmQnQoRpRqRrSsStSuTvTwTxUyUzU{V|V}V~WWWXXXYYY|/|0|1|2|&|'|(|3|4|5|6|7|8| ||||||||1C1D1ED|)D|*D|+|| |!|"|#|$|%_|,_|-_|.c|9c|:c|;h|?h|@hlllppptttt tt tttt!t"t#t#t#t#t#t#t#]                        \    ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L D 000000 0  0  0  01 111 2222333334444555 57%7'7(7&8)8+8,8*9-9/909.:1:3:4:2;5;7;8;6<9<;<<<:===?=@=A=>>B>D>E>C?F?H?I?G@J@L@M@KANAPAQAOBRBTBUBVBWBXBSCYC[C\C]C^C_C`CaCbCcCdCC C CC CZDDDD D D D D DDDDD D DD DFcF|F}F~F F F F F FdGGGGHHHHH H H H H HLLLLLLL LNNNNNNN N NOOOOOOO O OPPPPPPP P  PQQ Q Q QQQ  Q QR R(R)R*R,R-R +R!V.V0V1V2V3V4V5V6V7V8V9V:V ;V V/  qdmQibJ`Qk`JYboqdmQikmJmokqdmQibJ`QkoirData                          ! " # $ % & ' ( ) * + 0 > / 3 1 2 = 4 5 6 7 8 9 : ; < ? G Q @ A B C D E F H P I J K L M N O R \ o S T U V W X Y Z [ f h ^ _ ` a b c d e g i m j k l n v p q r s t u w x z { | } ~  Root Entry0=tVBA@0VBAProjectCA@0VBA@0                             ! " # $ % & ' ( ) * + 0 > / 3 1 2 = 4 5 6 7 8 9 : ; < ? G Q @ A B C D E F H P I J K L M N O R \ o S T U V W X Y Z [ f h ^ _ ` a b c d e g i m j k l n v p q r s t u w x z { | } ~  . ,                      \    ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ ^ a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~  ]  _`JYboqdmQibJ`Qko] & " of " & [Pages]l51DetailmCommentIDdLabel1mClausedLabel13mSubClaused Label15m Paged Label17m Lined Label19mCommentTypedLabel21mCommentmSuggestedRemedydLabel25mResponsedLabel29mCommentStatusdLabel31mResponseStatusdLabel33fLine60mText66mCommenterNamemCommenterCoPageFooterdLabel65mText72d Label73m!Text74d"Label75m#Text53$CommenterEmail%CommenterPhone&CommenterFax'Topic(CreateDate)LastModDate*DispatchDate+WrittenDate,Accept_RejectDate-Closed_UnsatisfDate.VoterStatusemedy LabelmResponsedResponse_LabelRe Commenter-FullHotItems&ReportByCommentID6Rough import   check report"SignatureReportStatusReportSummaryTR CommenterVoterNamesVoterStatus 6Big-Font Committee report $Committee report w odXX 11CB0 10CB0 9CB0 8CB0 7CB0 6CB0 5CB0 4CB0 3CB0 2CB0 1CB0 0CB0PropDataScriptsww0wwBlob 22.Committee report03DBDumpReport1d28Arialm5<Arial Com` PageHeaderd8"`xb` c,d eLabel5Vote$mCommitteeReportentor name  0CB0er name`Detailm`<b CommenterNameij k VoterName VoterName`x PageFootMSysDbNPropData  DirData *PropData PropData^ qdmQibJ`QkoqdmQikmJmokoption_status_moded }mText72d Label73m!Text74d"Label75m#Text53$CommenterEmail%CommenterPhone&CommenterFax'Topic(CreateDate)LastModDate*DispatchDate+WrittenDate,Accept_RejectDate-Closed_UnsatisfDate.VoterStatusemedy LabelmResponsedResponse_LabelRe$Committee report 6Big-Font Committee report VoterStatus ENGLISHBRRBATOM_1440opt_1440.inicop_1440.iniHL144ini.datts $_GetAllComments1 3Clm7S<"`lauseSubclaused25Q8"`ͬ" fEW-bUvPageHeaderSectionDetailPageFooterSectionReportHeaderReportFootermCommentdComment_LabeldLabel2mText3m Text4f Line5 CommentID Main.CommenterName CommenterEmailCommenterPhoneCommenterFaxCommenterCo   !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPSTUVWXYZ[\]^`abcdefghijklmnopqrstuvwxyz{|}~|>?ͬ;@Detaild Label0eBox2h gofHoundDoggingd Label23d Label24d Label25h gofMainh gofRoughh gofDispatchh gofStatusPopUph gofInputd Label31h gofFinalReportsgImage32?}023=Babc$e g!hi:jk61`@ Arial8hHP LaserJet 4 Plus(Local)@w XX@MSUDNHP LaserJet 4 Plus;d X$WINSPOOLHP LaserJet 4 Plus\\Server\hp4plusd2e12g237hghMS Sans Serif` Detaild5]`a<b4cd e Label0L802.15.3/D09r1 Comment Resolution DB e1235ab chBox2d25]`a bcHLabel23rAccept new input in ASCII format -- WEBMAIL or EDMAILd25_`a\ bcLabel24ݒSend email to editors about newT0d _ Z g  ~K w  z 1 :AN[ noBA3L' {{3@ {{3@Rough import check reportR'e@,@Rough import check reportm>TTTTTTTTTTR &k@,@ReportByCommentIDm>DDDDDDDDDDB %¡{n@,@HotItemsm>22222222220 y#}@,@Commenter-Fullm>>>>>>>>>>>< "m@,@Big-Font Committee reportm>TTTTTTTTTTR !LDt3@LDt3@_GetAllComments1m>BBBBBBBBBB@  m=ͽt3@m=ͽt3@_GetAllCommentsm>@@@@@@@@@@> ̋Ru`@,@Common utilitiesm>BBBBBBBBBB@ D61`@,@STARTm>,,,,,,,,,,* 0Ǣe@,@fStatusPopUpm>::::::::::8 Vĭe@,@fRoughm>.........., t@t@fPIcture9m>44444444442 V@V@fPicture8m>44444444442 ͜>@͜>@fPicture7m>44444444442 \A@\A@fPicture6m>44444444442 XPM@XPM@fPicture5m>44444444442 J@J@fPicture4m>44444444442 eXG@eXG@fPicture3m>44444444442 LD@LD@fPicture2m>44444444442 b@b@fPicture14m>66666666664 ͜n@͜n@fPicture13m>66666666664 #j@#j@fPicture12m>66666666664 y^@y^@fPicture11m>66666666664 /VZ@/VZ@fPicture10m>66666666664 P@P@fPicture1m>44444444442  Y=^q@,@fMainm>,,,,,,,,,,*  H͗e@,@fInputm>..........,  Vߗe@,@fHoundDoggingm><<<<<<<<<<:  ڗe@@fFinalReportsm><<<<<<<<<<:  獫e@@fDispatchm>44444444442  @g\@@g\@UserDefinedm>88888888886  @g\@,䴡8@SummaryInfom>@DDD88888886 @)g\@g\@SysRelm>.........., g\@g\@Scriptsm>0000000000. g\@g\@Reportsm>0000000000. g\@g\@Modulesm>0000000000. g\@g\@Formsm>,,,,,,,,,,*  @ @DataAccessPagesm>@@@@@@@@@@>  g\@ g\@MSysRelationshipsl@=:::......., @ g\@ g\@Relationshipsl<<<<<<<<<<<:  g\@ g\@Databasesl<44444444442  g\@ g\@Tablesl<.........., Z:LU L L % !K ʂJ I* &IkG)%G'EMę8-B[WWWWWWWWWWWWWWW@EGGB@bGB@~sq_ffMainm>6666666yFB@0hB@c_sc_pg_lnm>A)@#|@zZNNB6666664 ` @s\@q3T@AccessLayoutm>4MR2KeepLocal TF4zz:::::::8 @p~Nh@_O@VoterStatusm>@< DDD88888886 @l@Eh@.wO@VoterNamesm>~@> BBB66666664 @ yDy@y@TR Commenterm>@w@zRFF:::::::8 @ckC]@^;y4@Roughm> @888,,,,,,,* @_g\@g\@MSysIMEXSpecsm><<<<<<<<<<: Dg\@ԂZ_@MSysIMEXColumnsm>@@@@@@@@@@> =s{3@gw{3@MSysAccessObjectsm>DDDDDDDDDDB ʲw@ٞ2|8@MainOutputm>u-|BBB66666664 @gb~b@[B@Indexm>E@888,,,,,,,* @^*ue@f@Dispatchm>h@}>>>22222220 @yBln@ ln@0CloseEandTcommentsm>@w@z^RRFFFFFFFD @LG0f@y8@ClauseListm>M@BBB66666664 @A8+wז@8+wז@~sq_rVoterStatusm>4MR2KeepLocal TBBBBBBB@ @y?"Q@"Q@~sq_rSummarym>4MR2KeepLocal Tzzz:::::::8 @y=f^!Q@!Q@~sq_rSignatureReportm>4MR2KeepLocal TJJJJJJJH @<WQ@Q@~sq_rRough import check reportm>4MR2KeepLocal T^^^^^^^\ @y:8Q@lQ@~sq_rHotItemsm>4MR2KeepLocal T|||<<<<<<<: @y8Q@Q@~sq_rBig-Font Committee reportm>4MR2KeepLocal T^^^^^^^\ @y5_@_@~sq_ffDispatchm>4MR2KeepLocal T~~~>>>>>>>< @y3c"@c"@~sq_cfHoundDogging~sq_cConfirmationListm>c@4MR2KeepLocal T|ppppppn `2ݨ @ݨ @~sq_cfFinalReports~sq_cTypeListm> @u4MR2KeepLocal Tl``````^ `y0 ۏe@Ҋ#f@_GetAllCommentsm>{ :@O5@zdXXL@@@@@@> `/ oc`@aUO@Adminm>@8,,,,,,,,,* .y(7a@,@mCommitteeReportm>BBBBBBBBBB@ -h@,@VoterStatusm>88888888886 ,M wh@,@VoterNamesm>66666666664 +})y@,@TR Commenterm>::::::::::8 *wVf@,@Summarym>0000000000. )C l@,@StatusReportm>::::::::::8 (H%l@,@SignatureReportm>@@@@@@@@@@> hl5J  v X :  b D & b 4  ʬʬʬʎ p R * n P * nP* lFsA#g5kM/ lN0r8]]]]Cd  CE T GE T GED T Cd  Main.Line( gCd  Main.Page( gCd Main.Subclause- gCd  Main.Clause* gCd Main.CommentID- gCd Main.CommentType/ gCd Main.CommenterName1 gCd Main Cd  GCd  GCd  Cd  GBd @ 'Bd Main.ResponseStatus"C"H7 wBd Main Bd  GBd  GBd  Bd  GAVoterStatus''' A  GA A G@VoterNames%%% @  G@ @ G?Main ?  G? ? G>ClauseList%%% >  G> > G=(((Main.CommentType)="TR")): '=Main.*% g=Main = = G<Rough <  G< < G;Main ;  G; ; G:Main :  G: : G9Main 9  G9 9 G8Main 8  G8 8 G7Rough 7  G7 7 G5Dispatch!!! 5  G5 5 G4TypeList!!! 4  G4 4 G3TypeList.Comment/ g3TypeList!!! 3 G3 3 G2TypeList!!! 2  G2 2 G1ClauseList%%% 1  G1 1 G0 Main.CommenterName1 '0 Main.Subclause- '0 dMain.CommentType1 /0  Main.Clause* '0Main.CommenterName1 g0Main.Subclause- g0Main.CommentType/ g0 Main.Clause* g0Main.*% g0Main 0 0 G%Y <N   Y d Y d Y dY Y Y Y Y Y  Y  ClauseList Editor Email Owner ChiefNoWrittenNoAction NoSigTRproblemDone00000000 0  0  0  01 111 22223333344445LwA  GA A G@VoterNames%%% @  G@ @ G?Main ?  G? ? G>ClauseList%%% >  G>1Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@@@@@@@@ - {{3@ {{3@VoterStatus66666666666 , {{3@ {{3@VoterNames44444444444 + {{3@ {{3@TR Commenter88888888888 * {{3@ {{3@Summary........... ) {{3@ {{3@StatusReport88888888888 ( {{3@ {{3@SignatureReport>>>>>>>>>>> dv @ @ @ @ @ @ @ @ @ @ 00000000 0  0  0  01 111 2222333334444555 56!6#6$6"7%7'7(7&8)8+8,8*9-9/909.:1:3:4:2;5;7;8;6<9<;<<<:===?=@=A=>>B>D>E>C?F?H?I?G@J@L@M@KANAPAO ]Vp]V ]Vx]V @]V]V h]V]V ]V]V ]V]V ]V]V  ]V]V  ]V]V  ]V]V  @]V]V  p]V]V ]V]V ]V]V ]V]V ]V]V ]V]V @]V]V h]V]V ]V]V ]V]V ]V]V]V]V]V]V@]Vh]V]V]V]V]V]V ]V@]Vp]V]V]V]V]V]V@]Vh]V]V]V]V]V~]V~~]V~"]V~  J]V~ r]V~ ]V~ ]V~ ]V~]V~x5 G4TypeList!!! 4  G4 4 G3TypeList.Comment/ g3TypeList!!! 3 G3 3 G2TypeList!!! 2  G2 2 G1ClauseList%%% 1  G1 1 G0 Main.CommenterName1 '0 Main.Subclause- '0 dMain.CommentType1 /0  Main.Clause* '0Main.CommenterName1 g0Main.Subclause- g0Main.CommentType/ g0 Main.Clause* g0   O8OΞG  N  Y   Y d Y d Y XdY Y Y Y Y Y  DoneClauseList Editor Email Owner ChiefNoWrittenNoAction NoSigTRproblemY ConnectDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeIiimmmiCmEmYYIdParentIdName        45FpGqHrIsJtKuLvA G@VoterNames%%% @  G@ @ G?Main ?  G? ? G>Cj{{3@|{3@ClauseList44444444444 Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@ -----CHECK ALL "A","B"David Cypherdavid.cypher@nist.govD- "10"Gregg RasorGregg.Rasor@motorola.comC) "08"Jay Bainjay.bain@timedomain.com?&%"06","09"Allen Heberlingaheberling@xtremespectrum.comQ2!*"00","01","02","03","04","05","07","08"David Cyphergilb@ieee.org\M? LVAL (((( @ @ @ @ @ @ @ @ @ @ @00000000 0  0  0  01 111 2222333334444555 56!6#6$6"7%7'7(7&8)8+8,8*9-9/909.:1:3:4:2;5;7;8;6<9<;<<<:===?=@=A=>>B>D>E>C?F?H?I?G@J@L@M@KANAPAQAOBRBTBUBVBS  !"#$%&()*+,-./012345789:;<=>?@ABCDEGHIJKLMNOPQRSUVWXYZ[\]_`abcdefghijklmnoqrstuvwxyz{|}~0* pHd 802_3z.mdb4@j = r ̗; J< ADAO>BDAO *\G{00025E01-u0C  0046}#5.0#0#C:\PROGRAM FILES\COMMON MICROSOFT SHA0RED\w350.DLL#Microsoft  3.5 Object LibraryHTstdole>fstdole]f\]043[V-]2]WINNT\System32\12.tlb#OLE Automation/VBIDE>VBIDECaCE157C5.3Program Files\CommonHShared\VBA6E6E@XT.OLBRVisual Basic for @Applic1s Extensibility +  @Report_Big@-Font %i@ttee rBGUR`pbrd_Cig-FE@n@ (((lb14.VOTE)="yes" Or (lb14.VOTE)="yes with comments"))(((lb14.VOTE)="yes"[lb14]![LAST] & ", " & [lb14]![FIRST](((Main.CommenterName)=[Input Commenter Name]) AND ((Main.CommentType)="TR"))(((Main.CommenterName)=[Input Commenter Name]))(((Main.CommentType) In ("E","T")) AND ((Main.CommentStatus) In ("A","R")) AND ((Main.ResponseStatus) In ("W")))O%sM b ( F ˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩ˋ m mmmmmmmmmmmmmmmmmmmmmmmO 1 e 0 x xxxxxxxxxxxxxxxxxxxxZ < <<<<<< ȦȈȈȈȈȈȈjL&VVVVVVVVVVVVV8xCOCountOfN  N  NLrdLrdLrdlb14.OrLrdlb14.Original_VOTE1 gLrdlb14.Original_VOTE1 gLrdlb14.Original_VOTE1 gL rLrdLrdLrdlb14.OrLrdlb14.Original_VOTE1 gLrdlb14.Original_VOTE1 gL rdlb14.Original_VOLrdlb14.Original_VOTE1 gLrdLrdLrdLrdlb14.OrLrdlb14.Original_VOTE1 gLrdlb14.Original_VOTE1Lrdlb14.Original_VOTE1 Lrdlb14.Original_VOTE1Lrdlb14.Original_VOTE1LrdLrdlb14.Original_VOTE1 gL rdlb14.Original_VOTE1 gLordlb14 Lrd GLrd GPCountOfNew_VoteCount(lb14.New_Vote)Q// oPlb14.New_Vote, gP lb14.New_Vote, gPlb14 P GP GP P GO O GN N GL L GGMain G  GG G GF Main.Comment+ 'F  Main.Line( 'F  Main.Page( 'F Main.Subclause- 'F  Main.Clause* 'FMain F GF GF F GD Main.CommentID- 'D@ 'D Main.Response, gD Main.SuggestedRemedy3 gDMain.Comment+ gD Main.Line( gD Main.Page( gDMain.Subclause- gD Main.Clause* gDMain.CommentID- gDMain.CommentType/ gDMain.CommenterName1 gDMain D GD GD D GC d Main.CommentID- 'Cd ^@ 'Cd Main.Response, gCd Main.SuggestedRemedy3 gCd Main.Comment+ g[Y Settings\alN Y d Y  Y Y  EmailMessageSubjectMsgBodyFull YY Email           !"#$%&' (!)"*#+$,%-&.'/()*+,-./01 2 3 4 5 6789:;<=>?@AB```YY```````]Y``````]``````YY````````]Y```````````````Y```````````````Y``````G:X``````XY112243#&]263'*]3;32Y"Y]Y*YY&12]Y]*/28D]21Y236?W``````Y(````Y``]````````YY``````````````````````````````````]``````````````Y````````]````````Y```````Y`````````Y````]YYY````]``P'YYF%YY+`P/YD7`G!129R(YY`````````]```Y````YYY]```````````]Y`````````````````````````````````YY````````YY`````````````````````````Y`````````````YYY```````Y````````Y``````Y````'Y````````Y````````````````Y````````````]Y```````Y````````]````````Y```````Y``````]Y`]Y`````YY``````YY```````]Y````````Y```````]````````````YY``````YY``Y```Y`Y````` ]``````Y`YY````Y```Y```````YY`````````YY``````]`````````````````````````````````````YY````````````````````````````````YY```````]Y`````YY`]Y````]Y``]``````````YY```;YY``````YYY``````````]````````Y```````YY``````YY`````````]````````Y```````Y``````]``````````]````````````````Y`````````````````````````````````````````YY```]Y````YYY`````YY`]```]Y````Y`````````Y`]YY`]Y```````````````````````````````````````````````]``````````````Y````````]`````````Y```````]`]``YY`]Y````````]Y`````````Y``YY` DD2```]Y````````````]Y````````]Y`YYY``````````YY``````````````````````````YY``````Y``````````]Y`````````````````````````Y````````````]Y``]``````````````YY``````Y``]]YYY`Y``````]Y`````````YY``````````````Y```````Y``````````]````````Y```````Y``````]Y```]``````YY``````YY````````Y`````````YY`````]Y```````````````YYYY````Y``]Y`````, YYD8````YY``````Y```Y`````````Y``````````````]YY```````````````````````````````````````Y``````````````````````````````````]````````````````Y``````````````````````]``DD``````````YY``````````Y````````````]Y`````````````````Y````````]Y``````]Y``````]````````````]`````````````````]``````````YY````YY````````````YY````YY``YYY]````````Y5``Y```Y``````YY`YY```````]```````````````]Y``````````````````````````````````````` LvExtraMSysQueriesLvExtraLL>((n FlagMSysQueriesFlag@@8""n  ExpressionMSysQueriesExpressionXXD..n  Name2MSysQueriesName2DD:$$n  Name1MSysQueriesName1DD:$$n AttributeMSysQueriesAttributeTTB,,nv1  h  c  0 p3&t p R ,  n P * nP* nP( M/gA#y[' 4 l.G eCd  Main.Line( gCd  Main.Page( gCd Main.Subclause- gCd  Main.Clause* gCd Main.CommentID- gCd Main.CommentType/ gCd Main.CommenterName1 gCd Main Cd  GCd  GCd  Cd  GBd @ 'Bd Main.ResponseStatus"C"H7 wBd Main Bd  GBd  GBd  Bd  GAVoterStatus''' A  GA A G@VoterNames%%% @  G@C|{3@|{3@Commenter--Full>>>>>>>>>>> B|{3@|{3@0CloseEandTcommentsDDDDDDDDDDD j{{3@|{3@ClauseList44444444444 Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@@@@@@@@ - {{3@ {{3@VoterStatus66666666666 , {{3@ {{3@VoterNames4444444444 SOYkfJmMWSSYbJ^iQfdimkSWdobOOdUUYbUSYbfomS`JYbSfYMmoiQ8SfYMmoiQ86SfYMmoiQ88SfYMmoiQ8:SfYMmoiQ8<SfYMmoiQ8>SfYMmoiQ:SfYMmoiQ<SfYMmoiQ>SfYMmoiQ@SfYMmoiQB SfYMmoiQD!SfYMmoiQF"SfYMmoiQH#SidoUW$SkmJmokfdfof%kmJim&Md``dbomY^YmYQk'+UQmJ^^Md``Qbmk(+UQmJ^^Md``Qbmk8)LYUSdbmMd``YmmQQiQfdim*Md``QbmQiSo^^++Md``YmmQQiQfdim,WdmYmQ`k-iQfdimLvMd``QbmYO.idoUWY`fdimMWQM\iQfdim/kYUbJmoiQiQfdimkmJmokiQfdimko``JivmiMd``QbmQiqdmQibJ`QkqdmQikmJmok`Md``YmmQQiQfdimJO`YbOJmJJMMQkkfJUQkOJmJLJkQkSdi`k `dOo^Qk iQ^JmYdbkWYfkiQfdimk kMiYfmk kvkiQ^ mJL^Qk+UQmJ^^Md``Qbmk+kh+MSSYbJ^iQfdimk+kh+MM^JokQ^Ykm +kh+MSSYbJ^iQfdimk+kh+MmvfQ^Ykm +kh+MSWdobOOdUUYbU+kh+MMdbSYi`JmYdb^Ykm +kh+MSWdobOOdUUYbU+kh+MmvfQ^Ykm +kh+SSOYkfJmMW +kh+SS`JYb+kh+SSidoUW+kh+iLYUSdbmMd``YmmQQiQfdim'+kh+iMd``YmmQQiQfdim+kh+iWdmYmQ`k+kh+iiQfdimLvMd``QbmYO+kh+iidoUWY`fdimMWQM\iQfdim+kh+ikYUbJmoiQiQfdim+kh+ikmJmokiQfdim+kh+iko``Jiv+kh+iqdmQibJ`Qk+kh+iqdmQikmJmokM^JokQ^YkmM^dkQQJbOmMd``QbmkMd``QbmQiSo^^++`kvkJMQk`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkJMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQOaCbCcCdCC C CZcmd_prop_reject box_commentcmd_prop_accept_in_principlebox_suggested_remedy box_responsecmd_prop_accept Option177 Option179 Option181 Option194 Option196HC7?Option_Filter1Option_Filter2AdditionalCriteriaOption_OrderByBox173Box172Box66TopicAccept_RejectDate CommentStatus LastModDate CommentTypeResponseStatusOption_ViewWindow ViewWindowoption_status_mode WrittenDatecmd_SetDefaultsLabel54Label56cmd_comm_accept CommentIDcmd_comm_rejectLabel62cmd_reac_closedcmd_reac_withdrawnText98cmd_reac_unsat cmd_QuickFindcmd_applyfiltersortClosed_UnsatisfDate Option135 Option137 DispatchDateAdditionalCriteria_DblClickcmd_applyfiltersort_Clickcmd_comm_accept_Clickcmd_comm_reject_Clickcmd_prop_accept_Click "cmd_prop_accept_in_principle_Clickcmd_prop_reject_Clickcmd_QuickFind_AfterUpdatecmd_QuickFind_DblClickcmd_reac_closed_Clickcmd_reac_unsat_Clickcmd_reac_withdrawn_Click cmd_Fun_Clickcmd_SetDefaults_ClickCommentStatus_AfterUpdateCommentTKYNY Y NextCommentIDOldCommentIDYY0LastIndexNumberIHaveUsedOldCommentIDr output file nameZ`LJ7h& ,c:\mydocs\WEBascii.txt General >Editor's Ascii report generator 4c:\mydocs\EDITORSascii.txt Tilde :Editor's Tilde-file generator 4c:\mydocs\EDITORStilde.til ^Error in module cASCIIReport. Invalid argument.i)VG C։}wxgrCp Tjh lA valid filename is required. Use OK to accept default zWarning! Output file already exists. Do you wish to continue? "Output file error$ "04","05","06","22","30","30A","30B","34","35","36","36A","37","38", PageHeaderaC7? L RPreparing to print report for all clauses SELECT *  WHERE ,ORDER BY Main.Clause,  JMain.Subclause, Main.Page, Main.Line; 4Committee Report By Clause *WHERE Main.Clause In( )  AND WC7?Reportz? PageFooter tORDER BY Main.Clause, Main.Subclause, Main.Page, Main.Line  2SELECT * FROM MainOutput; Subclause :MainOutput Export with Tildes MainOutput report complete Y 04.B2դOhW0ńUW@դOhWwhDESTLfa8DXr5cmdClearDispatchTablecmdClearMainTablecmdUnlockDangerousButtonscmdAllToEditorsseSummaryReportsseGeneralReportsseCreateTildeFilescmdNewToEditorssnSummaryReportsBox76Box77snCreateTildeFilessnSendConfirms snSetStatussnGeneralReports cmdSendEmailLabel69ConfirmationListLabel68Label70cmdRequestChangeBox74Box75 cmdAllToChiefscCreateTildeFilesscSummaryReportscmdRequestChange_ClickcmdClearDispatchTable_ClickcmdAllToChief_ClickcmdAllToEditors_ClickcmdClearMainTable_ClickcmdNewToEditors_ClickcmdSendEmail_Click cPrepareMail cSendSummary cSendGeneralcSendConfirmations cSetStatusXD cSendTildecmdUnlockDangerousButtons_ClickscSummaryReports_ClickscCreateTildeFiles_ClickseCreateTildeFiles_ClickseGeneralReports_ClickseSummaryReports_ClicksnCreateTildeFiles_ClicksnGeneralReports_ClicksnSendConfirms_ClicksnSetStatus_ClicksnSummaryReports_Click cmdAllToEditors seSummaryReports seGeneralReports $seCreateTildeFiles cmdNewToEditors snSummaryReports CommentType: snGeneralReports $snCreateTildeFiles snv1SendConfirms snSetStatus cmdSendEmail "cmdClearMainTable *cmdClearDispatchTable*=H87kpNv,LaE6/LB  Email XSummary of all comments to date, by editor ( Comment:  0SELECT * FROM ClauseList ) AND  8All summary reports complete File Datafile  exists. 2Do you wish to overwrite? cSendSummary &SELECT * FROM Main  Subject:  NThe following records were produced on lL<"AFY :The selection criteria were:  jCommentStatus has been changed to "D" for this report  2Summary report complete ( D CL:  Type: / SC:   # .SELECT * FROM Dispatch WHERE Email = " WrittenDate:  0" AND MessageSubject = " " AND Full= MessageSubject @- - - - - < message > - - - - -  MsgBody Full XPlease enter prefix for NEW records report: ,scSummaryReports_Click c:\mydocs\ DispatchDate:  Line: 2 A filename prefix is required. It should include the directory pathname. Use OK to accept default XDetails of all comments to date, by editor ( _ _readable.til Warning: File _ 0 exists. Overwrite file? ,scGeneralReports_Click NAll general (readable) reports complete vORDER BY Main.Clause, Main.Subclause, Main.Page, Main.Line  FGeneral (readable) report complete( CommentStatus: "ResponseStatus:  Topic:  CreateDate: LastModDate: `q]Is (Accept_RejectDate: ,Closed_UnsatisfDate:  VoterStatus:  ----------- CommentID: CommenterName: "CommenterEmail: "CommenterPhone: CommenterFax: CommenterCo:  Clause:  Subclause:  Page:  CommentEnd: $SuggestedRemedy:  RemedyEnd:  Response: ResponseEnd:  PPlease enter prefix for Summary report:  to_ _tilde.til 4All tilde reports complete 6The dispatch table is emptyI qO\Uw}FJc p  NY Y OldCommentIDNextCommentID1\VBA\VBA6\VBE6.DLLVBA  10J_N? 3C:\Program Files\Microsoft Office\Office\MSACC9.OLBAccess  1@^F=C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO\DAO350.DLLDAO QP0FgofHoundDoggingC:\WINNT\System32\stdole2.tlbstdole  Q`WFCC:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLBVBIDE y pJդOhWLդOhW;@KդOhWEC7?gofFinalReportsAC7?Label3131?FormSC7?DetailLabel0BC7?Box2Label2B|{3@B|{3@Index*********** |{3@B|{3@Dispatch00000000000 C|{3@|{3@Commenter--Full>>>>>>>>>>> B|{3@|{3@0CloseEandTcommentsDDDDDDDDDDD j{{3@|{3@ClauseList44444444444 Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@@@@@@@@ - {{3@ {{3@VoterStatus66666666666 , {{3@ {{3@VoterNames44444444444 + {{3@ {{3@TR Commenter88888888888 * {{3@ {{3@Summary........... ) {{3@ {{3@StatusReport88888888888 ( {{3@ {{3@SignatureReport>>>>>>>>> ConnectDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeIiimmmiCmEmYYIdParentIdName        @ABConseStatus = 'O' _tilde.txt hCommentStatus In('X','D') AND ResponseStatus In('W')& CommentStatus In('A','R') AND CommentType = 'TR' AND ResponseStatus = 'W' VCommentType = 'TR' AND ResponseStatus = 'U' bProgram error: too many options in Option_Filter2LBKdvk :Clause, SubClause, Page, Line Page, Line bProgram error: too many options in Option_OrderBy <PROPOSED ACCEPT IN PRINCIPLE. *ACCEPT IN PRINCIPLE.  PROPOSED  REJECT.  ACCEPT.  T &snSetStatus_Click() from_ TDoes the commentor accept this resolution? 6Confirmation from commenter "PROPOSED ACCEPT.  fDispatch>FG[gxGh̨aK:[q*z: !N_Ȯ ^This operation will modify your Main database.  VIt will change all status codes from X-->D.'DHu{xg4 >WHERE Main.CommentStatus = "X"; LStatus flag operation complete: X-->D HDetails of NEW comments, by editor ( ,snSummaryReports_Click 0scCreateTildeFiles_Click >) AND Main.CommentStatus = "X"  4All Tilde reports complete nBack to you, chief -- details of all comments to date ( ) from  RPlease enter filename for Detail report: &c:\Comments\tildes\TP٤DfROPߪ­sH&Bj3N鞰J;M .r׶=Ԓ@c{ΖO ޴H,AD!Z>d*H   :Clause, Page, Line, SubclauseL3d08G=bBa "PROPOSED REJECT. |BIYVO fPicture! ONB@Vb+)m,L5xvX (=Mϭc-ɧ_.u8F5qYxlLabel200 `X (=Mϭc-ɧ_.u8F5qYxlLabel200 `hWyFhDESTդOhWCommentSuggestedRemedyResponse SubclauseText50 {\}eOhW{\}eOhW{\}eOhW?hI2")}RJBh9b!nK¯? fFinalReports afDBO(XդOhWkWKhDESTդOhW ClauseListcmdWEBasciiReportcmdFancyCommitteeReportLabel16cmdEditorsASCIIReportcmdSummaryReportLabel22cmd_tildereportLabel26cmd_StatusReportLabel28TypeListLabel9cmd_StatusReport_ClickcMeasurecmd_tildereport_ClickcmdEditorsASCIIReport_ClickcmdSummaryReport_ClickcmdWEBasciiReport_Click cASCIIReportb:?QN)!HcmdFancyCommitteeReport_ClickcSummaryReport  4SELECT * FROM ClauseList ; ClauseList CHECK 6WHERE ResponseStatus = "O"  NoWritten rWHERE CommentStatus In("X","D") AND ResponseStatus = "W"  NoAction 2WHERE CommentType = "TR" rFoO I nAND CommentStatus In("A","R") AND ResponseStatus = "W"  NoSig 2AND ResponseStatus = "U"  TRproblem zWHERE ((CommentType = "TR" AND ResponseStatus In ("C","Z")) ! ~OR (CommentType <> "TR" AND ResponseStatus In ("C","U","Z")) + OR (CommentType <> "TR" AND ResponseStatus = "W" AND CommentStatus In("A","R")))  Done ,Record counts complete StatusReport ,ClauseList <> "CHECK"  ALL  AND Clause In( ) 4SELECT COUNT(*) AS rcount  FROM Main  bcMeasure: horrible error, could not count records rcount Summary DPlease select from the Clause List TypeList @Please select from the Type List zChecking for records that don't match any known clause number fHoundDogging Committee report rIsNull([Clause]) OR [Clause] Not In ("00","01","02","03",, "04","05","06","22","30","30A","30B","31","31B","34","35","36","36A","36B","37","38", N"38A","38B","38C","38D","39","41","42") 4WEB Ascii report generator TPreparing to print report for all cla0LVALQ,ZZΰ |   L H R^\6herence manual 6th ed. anACCEPT IN PRINCIPLE. Frequency Nulling is process a programmable notch filter.Terminology to be added.ACCEPT. (deleted entire sentence)ACCEPT IN PRINCIPLE. If copyright permission is not obtained, all of these definitions will be deleted.ACCEPT. This was due to a formatting error caused by an excessively long title.ACCEPT IN PRINCIPLE. Will be change to a numbered list.REJECT. Will redraw figures 43, 45, and 46ACCEPT IN PRINCIPLE. Bluetooth (BT) to be replaced by 802.15.1ACCEPT IN PRINCIPLE. Will either add curve or correct title by removing 802.15.1REJECT. There is no need, since the words "a checking" precedes.ACCEPT IN PRINCIPLE. Figure XXX to be replaced by Figure 53ACCEPT IN PRINCIPLE. Change WLA to WLANACCEPT IN PRINCIPLE. Cross with #171ACCEPT. Editor's note about 2 Mbit/s will be removed, since 2 Mbit/s is now included.ACCEPT. This was due to a formatting error caused by an excessively long title.REJECT. According to The Gregg Reference manual 6th ed. and the IEEE standards style manual, the current text is correct.REJECT. No change required No.ACCEPT. No change required. YesREJECT. Figure will be deleted, so nothing to compare with.ACCEPT IN PRINCIPLE. Will change must to shouldREJECT. New text should better explain the comment.ACCEPT IN PRINCIPLE. Clause needs to stay, will rewriteACCEPT IN PRINCIPLE. Delete orthogonal and find a better equation.REJECT. Text to be added that noise is negligible.REJECT. Text to be added that noise is negligible.REJECT. No need to redefine master slave when 802.15.1 is a normative reference listed in clause 2.ACCEPT IN PRINCIPLE. Editor's note will be removed, since 2 Mbit/s is now included.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.LVALR4B Ͳ ( ^ ^ Fp(xACCEP According REJECT. AACCEPT IN PRINCIPLE. InclusionREJECT. Since these two discussions are in twREJECT. No requirement for IEEE 802 style.REJECT. Since these two discussions are in two separate clauses, there is an advantage of having them be self-contained.ACCEPT IN PRINCIPLE. Figures 43, 45, and 46 will be redrawn with black and white only.ACCEPT IN PRINCIPLE. Inclusion of the last name with a reference is IEEE standard Style manual 9/2002 clause 19.REJECT. Not a requirement for IEEE style.REJECT. Not a requirement for IEEE sytle.ACCEPT IN PRINCIPLE. Coexistence follows a different set of rules, while Interoperability follows the same set of rules.ACCEPT IN PRINCIPLE. Change to greek phi in the bj row block and make multiplication of "t" clearACCEPT. Will either add curve or correct title by removing 802.15.1REJECT. Checked word usage in Webster's New Collegiate Dictionary. Ensure: To insure Insure: To ensureACCEPT IN PRINCIPLE. Further investigation to confirm descrepencies between figure and textACCEPT IN PRINCIPLE. change to -10 to 10 dBACCEPT IN PRINCIPLE. The application's requirements determine if these degradations are tolerable.REJECT. Although by vendor we mean there is a different implementation, we think it is clear enough.ACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eACCEPT IN PRINCIPLE. All parameters are included, simulation time was sufficient for accurate results.ACCEPT IN PRINCIPLE. Will delete orthogonal and modify equation for better fit/approximationACCEPT. Remove line 54 from page 13 and replace with noise is considered negligible.ACCEPT. We will re-write sentenceACCEPT IN PRINCIPLE. 802.15.1-2002 and 802.11-1999 are currently in clause 2 as normative references.lLVAL|.D@ X X @M?X @Bj0XBj   ȅ  d   !TypeList.TypeListTypeListTypeList.CommentTypeList.SubjectTypeList.HeaderHX x "@ x3+ @aH PB@a hj@a  xG1@=~sq_cfHoundDogging~sq_cTypeList p x 0 X0X @aA@aB@aj@axTypeList   B j0X (  x8HXhxh0  0  0    $z xc      H     ȃ  d  H 8PX`h   H  TypeListv ((q(((((((((((((((((((((((((((( PTypeList (8 1 l􋓊tȀN@@, YunxinYunxin.Li@mo"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661@@I@nxinI@I@i@moI@"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola044.1.2738E`@Z@AC@!)VB>?@huster, Tomtom.schus"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec1212.1.1.47147EF@z@{XOT:6߿ ?@H@s, RH@H@oberI@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum1212.2.1775E Figure xxxShould it be figure 53?AC ACCEPT. figxxx\\T=;99bB>9f ?@H@s, RH@H@ober"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum00Table of ContentsT@]@fAC@+#00, Z:6^>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1212.1.27152El@fRCF@&&&  Z>> \>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1111.36646EN@ fRC@||"Z>> V>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.55338E!....backoff has been completed.RCN@GGG;977  Z>> N>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.1424EP@fAC ACCEPT. +++Z>> 5`<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1212.1.2.47322Eextra comma.Delete comma.AC ACCEPT. BBB+)'' X@>1`<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola10Table 215242E@ Sp@VAC ACCEPT. %%%   X@> @@berts, Williamrobert"0Roberts, Williamroberts.william@microlinear.com(801) 617-2524Micro Linear055.4.42828-34T@4XWNo.   Z:6ߟ LVALB^^^^^^^^^^^^^^^^^^^^^^ό Z ~ ~ r \\\J~:| ACCEPT IN PRINCIPLE. Will dACCEPT IN PRIREJECT. New dACCEPT IN PRINCIPLE. Not enough resourACCEPT IN PRINCIPLE. Will correct title by removing 802.15.1ACCEPT IN PRINCIPLE. Not enough resources to do more.REJECT. New disposition on TM for WPAN, that it is not enforceable, so it will be withdrawn.ACCEPT IN PRINCIPLE. Cross with #189ACCEPT IN PRINCIPLE. Change ""physical layer models"" to ""simulated PHY layer models"" in subclause 6.4 page 30 line 32.ACCEPT IN PRINCIPLE. Both will be broken out of the text.ACCEPT IN PRINCIPLE. Will delete orthogonal and modify equation for better fit/approximationACCEPT IN PRINCIPLE. Reworded to correctly remove the commented on problem.ACCEPT IN PRINCIPLE. Formatting will be done by IEEE editing staff later.REJECT. No harmonize, leave text and mark as informative.REJECT. TU is standard IEEE 802.11 terminology, no need to repeat here, which is listed as a normative reference in clause 2.ACCEPT. Will align TBTT to lineREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.ACCEPT. Will add text to clarify thisACCEPT IN PRINCIPLE. Will delete orthogonal and modify equation for better fit/approximationACCEPT. Add "dB" to both rows in column EquationACCEPT IN PRINCIPLE. Will add in 2.4 GHz after path lossACCEPT IN PRINCIPLE. Must consider the consistency of the terms through-out the draft.ACCEPT IN PRINCIPLE. Must consider the consistency of the terms through-out the draft.ACCEPT. The contents of these clauses should be informative. Also accept the suggested remedy to move clauses to Annexes.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.ACCEPT IN PRINCIPLE. Clause will be moved to an Annex and marked as informativeLVAL. . p The definitions of the parameters do not match the current partition sequence structure.QPSK: Change ""phase shift"" to be ""phase-shift""Change ""differentiated quadrature phase shift keying"" to differential quadrature phase shift keying.spelling of ""collocated"". Also in Clause 3.1, ""colocation"" is spelled with one l.Figure 5: The notations in the box of exp(j(wd(t)+fd))) does not match the equations in 5.4.1.2Check grammar and wording of this paragraph. For example, first sentence uses ""both"" twice and ""use"" followed by ""using"".Check the document for compliance with IEEE style manual. Examples: 1) Clause 3.1: After a colon leave at least one space 2) Tables appear to have a problem (may be just a PDF setting), but observe the vertex of several of then, they look as they were draw by hand. 3) Frontmatter is in very bad shape (see cover page) 4) Copyright footer is not centered 5) Before the TOC there is an empty page called "Contents"??? 6) recommend leaving an empty page per section, to make an even number of pages per section (recommended for printing purposes, so there is no coupling between one section and the other)@ "08","09","10","11","12"David Cypherdavid.cypher@nist.govU>0  !@LVALR0FD, ,h  ~?0( , P ( c    " J r      * J z     " J r        @ h       @ p      @ h                               " J r      * J z     " J r                d     d   d                 d        d Main.CommentIDMain#Main.CommenterName%Main.CommenterEmail%Main.CommenterPhone!Main.CommenterFaxMain.CommenterCoMain.ClauseMain.SubclauseMain.PageMain.LineMain.CommentTypeMain.Comment'Main.SuggestedRemedyMain.Response#Main.CommentStatus%Main.ResponseStatusMain.TopicMain.CreateDateMain.LastModDate!Main.DispatchDateMain.WrittenDate+Main.Accept_RejectDate/Main.Closed_UnsatisfDateMain.VoterStatus x  `    bGB@       "  J  r            *  J  z x}         "  J  r        Main    X"  jW!B@~sq_ffMain   `   h   p   x  @   h                         @    p                  @   h               @ h        @ p      @ h          "  J  r            *  J  z          "  J  r        Main          "   J   r                  *   J   z               "   J (  r 0   8   @   H     @ h        @ p      @ h      ) $   8   X  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P  P   !@LVAL/000Ϫ J  : 8J L w l a V K @ 5 *   z o d Y N C 8 - "   PROPOSED REACCEPT IN PRINCIACCEPT IN PRINCIPLE. Clauses 7 andACCEPT IN PRINCIPLE. B is typo of BLK. Change B to BLK.ACCEPT. Reference changed to 10.3.6ACCEPT IN PRINCIPLE. Sentence to be rewritten to better express why LDI was chosen.ACCEPT IN PRINCIPLE. Clauses 7 and 8 are to be moved into an Annex(es).ACCEPT. Since this was the resolution for TG1's draftACCEPT. For space and hyphen, but third item is still open.ACCEPT IN PRINCIPLE. It provides clarification on just what is meant by this and other acronyms that are used.ACCEPT IN PRINCIPLE. B is typo of BLK. Change B to BLK.ACCEPT. Figure 46 will be redrawn in black and white only.ACCEPT. Figure 45 will be redrawn in black and white only.ACCEPT. Figure 43 will be redrawn in black and white only.REJECT. Piconet is defined in the normative reference 802.15.1. No need to repeat it here.REJECT. The word, cycle, is not used. Code is used. If copyright permission is not obtained, the definition will be deleted.ACCEPT IN PRINCIPLE. can lead to an increase in packet collisionsACCEPT IN PRINCIPLE. Will be corrected by changing from 119 to 11b.ACCEPT IN PRINCIPLE. Will add to bibliography, if copyright permission is obtained for the defintions that reference it.ACCEPT IN PRINCIPLE. Cross with #175ACCEPT IN PRINCIPLE. Correction of error is to change from 119 to 11b.ACCEPT. Editor's note about 2 Mbit/s will be removed, since 2 Mbit/s is now included.ACCEPT IN PRINCIPLE. Figures 43, 45, and 46 will be redrawn with black and white only.ACCEPT IN PRINCIPLE. The application's requirements determine if these degradations are tolerable.ACCEPT IN PRINCIPLE. Change to 802.11bREJECT. Channel classification is not required for interoperabilityACCEPT. Take the alternative to take the least-numbered channels.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e "00","01","02","03","04","05","06","07"David Cypherdavid.cypher@nist.govdM?1 Ǝd>GT"݀?@I@d, II@I@di@iI@"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self044.1.3749-50En@^@ AC ACCEPT. |ZB> % @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies000040ED@@AC@LrXB>9?@I@d, II@I@di@iI@"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self1010.4.16041-42E@@ AC ACCEPT. |ZB>  @@I@s, WI@I@bertI@"0Roberts, Williamroberts.william@microlinear.com(801) 617-2524Micro Linear033.2441E@$adopt text aboveAC ACCEPT. +++bB>߿ @@I@nxinI@I@i@moI@"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola1010.3.15138E@ @AC ACCEPT. VB>I@?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.1.174E@lRemove comma.AC ACCEPT. ZB>߿ ~ ?@`E@s, R`E@rdrrober"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum1111.2.265Ej@lN@ kDWPROPOSED ACCEPT. ---   Z:60Q>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.2.35013E WLA=WLANACT@E000$"    Z>> 6@>@iak, Kaikai.siwiak@t0Siwiak, Kaikai.siwiak@timedomain.com954-755-6828256-990-9062Time Domain00001ED@SFixXOpdfN86;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil033.3549ED@K"Replace with 802.15.1 hop kernelAC ACCEPT. bt_11\@>߿ ;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil000043E@KFix.AC@"2\@>߽ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola099.032E@x"Specify which PHY model is used.AC@<#   ZB>߻91 гN7ʇ|żÅ:qf[PE:/$ti^SH=2;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil1212.2.1775EReferenc;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil1212.2.1775EReference to Figure xxxF@PAC ACCEPT. figxxx \@>߿9;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil044.064ED@KRemove one of themAC ACCEPT. \@>߿  @@rry, Stuart J."stuar0Kerry, Stuart J.stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips1010.4.36038En@"Remove additional ""t""."XOt_the33,,*((X86 @@I@ StuI@I@tuar0Kerry, Stuart J.stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips09Figures3424E@|@AC ACCEPT. )))X86 @@I@pol,I@I@chinJ@"0Chindapol, Aikaik.chindapol@icm.siemens.com858-521-3546Siemens055.3.6.2157Ez@ correct it.AC ACCEPT. ^B>߿  @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.3.5557E@Fix font size and add space.AC ACCEPT. 777 rXB>is @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.2.6.44844E@:@AC ACCEPT. ###  rXB> o @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.2.2.14442E@ Please change as indicated.AC ACCEPT. @@@)'%%rXB> M @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies055.1950E|@@AC ACCEPT. rXB>@ @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies044.1629EMbit/s splits across linesT@ AC ACCEPT. ///rXB> 0 @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies033.1.6327EX@@AC ACCEPT. rXB> wLVAL|NMR2OrderByOnOrientationColumnWidthColumnOrderColumnHiddenRequiredAllowZeroLengthDisplayControl$UnicodeCompressionValidationRuleValidationText FormatInputMaskDecimalPlaces FilterOrderByDescriptionCaptionDefaultValue  l CommenterName      m n"CommenterEmail      m VComment      f$SuggestedRemedy      ZPage      m ZLine      m  CommentStatus      m0 (In ("X","D","A","R")` XAllowed value for Comment Status: X, D, A, R  "ResponseStatus      m@ 8In ("O","W","S","C","U","Z")r jAllowed value for Response Statuss: O, W, S, C, U, Z XResponse      CreateDate    Short Date   99/99/00;0;_LastModDate    Short Date   99/99/00;0;_DispatchDate    Short Date   99/99/00;0;_WrittenDate    Short Date   99/99/00;0;_("Accept_RejectDate    Short Date   99/99/00;0;_,&Closed_UnsatisfDate    Short Date   99/99/00;0;_CommentID       m$ General Number\ Topic      m n"CommenterPhone      m jCommenterFax      m hCommenterCo      m dSubclause      m CommentType      m* "In ("TR","T","E")X PAllowed valuesfor Comment Type: TR, T, E  Clause      m In ("00","01","02","03","04","05","06","07","08","09","10","11","12","A","B") Allowed value for Clause: 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, 12, A, B hVoterStatus      m 71 qފ=ކH]N  ti^SH @@H@ StuH@H@H@@0Kerry, Stuart J.stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips055.0942TR@@RU@T`@> @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.4.1608E@@AC ACCEPT. rXB>v @@H@JameH@H@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.3494TRZ@d@ AC ACCEPT. rXB> d @@H@JameH@H@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.04049T@B@AC ACCEPT. rXB> S @@I@JameI@I@D@J@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies066.0298EB@Lower case please.ACr@*)  rXB>k@@I@ ErwI@I@noblI@"0Noble, Erwinerwin.noble@philips.com(408) 617-4768(408) 206-7386Philips1010.2.45023Emissing word`@AC ACCEPT. )))ZB>@@I@nxinI@I@i@moI@"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola1212.2.1775Ep@ n@AC ACCEPT. figxxxVB> @@H@ammeH@H@enshI@"0Shellhammer, Stephenshell@symbol.com(631) 738-4302Symbol Technologies, Inc.022.0248TF@N@AC ACCEPT. jB>߿ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.1.3749-52E@$Check wording and grammar.AC @ZB>߿g ?@H@s, RH@H@oberI@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum011.127Tl@Z@fAC@6ed_note%%  bB> Z>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.6 Table 26578E`@ fAC ACCEPT. AAA*(&&Z>>9@?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola099.032E*@xL@kAC @ZB>߻ 1 mʈx\ŭXX$N% @@lb, Jamesgilb@ieee.o"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies000040ED@@XO'`<@H@y, EH@H@away@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola0000E@SR@RC&@X@>  @@I@ammeI@I@enshI@"0Shellhammer, Stephenshell@symbol.com(631) 738-4302Symbol Technologies, Inc.055.31125E@@ AC ACCEPT. jB>߿ @@I@ammeI@I@enshI@"0Shellhammer, Stephenshell@symbol.com(631) 738-4302Symbol Technologies, Inc.033.2520EWording could be improved@AC ACCEPT. 888!jB>߿@@`F@nxin`E@in.Li@mo"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola1111.1.16152ER@N@DWH@ #zN:6?@fford, Iangiffordi@i"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self1111.3.16968E@@XOtR:6 @@I@s, WI@I@bert@"0Roberts, Williamroberts.william@microlinear.com(801) 617-2524Micro Linear033.1.7332Ep@adopt text aboveRC@")$$$bB>߿ @@I@rdp,I@I@k.sh@"0Shepherd, Nicknick.shepherd@philips.com+44 1293 815 057Philips044.1.2735EThis sentence has no verb.B@ RC*@affects!!  ^B>߿ @@I@nxinI@I@i@moI@"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola10Figure 3348E@ Redraw.AC ACCEPT. VB>@@I@nxinI@I@i@moI@"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola055.3.6.51654E@@AC ACCEPT. VB>8@>@H@r, BH@H@H@@0Treister, Bijanb.treister@bandspeed.com.au+61396146299+61414854414Bandspeed1212.28023T@X@Inclusion of Bluetooth SIG's AFH is highly unlikely to be available, since no agreement exists between IEEE 802 and Bluetooth SIG beyond version 1.1 of the Bluetooth specification. Therefore are choices are to leave in the section knowing that they are IRC@bt_afh^@> LVAL      P  P  P  P  8  , x& " X" ` X"   X"   X"   X"   X"   X"   X"   X"   X"   X"  @ X"  $@ X"  $@ X"  $ X"   X"   X"   X"   X"   X"   X"   X"   X"   X"   z ' + '   P p#  #  #  # 0 # h #  #  #  # H $   $   $   0$ ( @$ ` P$  `$  p$ ! $ @! $ x! $ ! $ ! $  " $   P        0  dh    d  d  H        (  `  d  ! @! x! ! !  d " _' ' ' ' ' (' 0' 8' @' H' P' X' `' h' p' x' ' ' ' ' ' ' ' '  P    0 h    H    ( `   ! @! x! ! !  " X" Main( ( PrimaryKeyCommentID8(  v P+ (+ 8+  ) )q ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) +  P + + , ( MainPrimaryKey ( P+ $ P+  ) + + + + X"  QYderByONJJ&Y  Y Z Y i Y   Y r Y n Y td Y n Y  rd Y td Y C Y l Y o Y n Y  Y [ Y tdY Y  Y Y Y $Y , Y dCommentIDCommenterNameCommenterEmailCommenterPhoneCommenterFaxCommenterCo ClauseSubclausePageLineCommentTypeCommentSuggestedRemedyResponseCommentStatusResponseStatus TopicCreateDateLastModDateDispatchDateWrittenDate"Accept_RejectDate&Closed_UnsatisfDateVoterStatusoeStJJsnS Jrs YYYCommentID"MainCommenterNamePrimaryKey JJ JJ J JaryKey JJ JJ J JLVAL)0 , < >ݹ ?@H@t, TH@H@ierr@"0Walrant, Thierrythierry.walrant@philips.com408-617-4676408-887-7765Philips0000TR@p@RU@*#std_vs_rp bB> ?@H@aialH@H@ocomAllen Tsaiallen@inprocomm.com+886-3-5165106 ext 870InProComm, Inc.033.1.2316-17E@z@{AC@Jdefinition  pJ66ݿ LVAL8L   There is no equation for SIR calculation, only a written description.Subclause title is ""SINR computation"" however, noise is not includedHow can we be sure these LMP commands will be accepted by BT SIG at all?So, are you saying a Viterbi reciever should be part of a recommended practice.Add new sub-clause regarding performace in regulartory domains with fewer than 79 hopping channels, smaller bandwidth.I don't understand the headings on this table 1, 2, 3 other Also, the entries in the table need to be clarified.Definition of co-located antennas seems strange. Should it be defined as also being in the same device? i.e., a PCIt looks to me that this is based in a particular scenario and does not cover more general cases. There were closed form analyzes not based on simulations (See Howitt et al) in the IEEE proposals. Why these were not mentioned in this work? I do not see an clear explanation that justify the scenarios used as "representative" of all (or a majority) of them, that is, what makes these scenarios "generic" I would like to see an explanation of the simplifying assumptions. The entire validity of theThere is no equation for SIR calculation, only a written description.Subclause title is ""SINR computation"" however, noise is not includedHow can we be sure these LMP commands will be accepted by BT SIG at all?So, are you saying a Viterbi reciever should be part of a recommended practice.Add new sub-clause regarding performace in regulartory domains with fewer than 79 hopping channels, smaller bandwidth.I don't understand the headings on this table 1, 2, 3 other Also, the entries in the table need to be clarified.Definition of co-located antennas seems strange. Should it be defined as also being in the same device? i.e., a PC LVALc  Q QQQQQQQQQQ͂ ̂̂̂̂̂̂̒ J@ 044.1610?J@033.259?J@033.2524MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOn1  <  MR2OrderByOnColumnWidthColumnOrderColumnHiddenRequiredAllowZeroLengthDisplayControl FilterOrderByValidationRuleValidationTextOrientationDescription FormatInputMaskCaptionDefaultValue$UnicodeCompressionN   0 (Main.[applied edits]l CommenterName      m n"CommenterEmail      m n"CommenterPhone      m jCommenterFax 6     m hCommenterCo      m dSubclause      m hCommentType      m l CommentStatus Y     m n"ResponseStatus      m MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOn1  <  MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOn1  <  MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  <   K1 ̎u2Ŗ8فsN'  w @@I@JameI@I@ee.o"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.34926E@Please change as indicated.AC ACCEPT. 000jP:6K @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies044.4928EN@Lower case the word.AC ACCEPT. )))rXB>P @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies055.4.2.22240EZ@ Add spaceAC ACCEPT. (((  rXB> R @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies055.4.2.32332E,@@ AC|@))rXB> W @@lb, Jamesgilb@ieee.o"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies066.2301EB@t@XOjP:6] @@lb, Jamesgilb@ieee.o"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies099.13521E@ Change as indicated.XO     jP:60D @@I@JameI@I@ee.o@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies044.1.1710EB@@ RC*@affects rXB> > @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies044.1610E @ h@AC ACCEPT. rXB> 7 @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies033.259EPN has an extra comment.@AC ACCEPT. +++rXB>2 @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies033.1.8414Ef@Lower case the words.AC ACCEPT. ...rXB>i/ @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies033.1312E@D@AC ACCEPT. rXB> ) @@I@JameI@I@ee.oI@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies011.124E@ @ ACD@OrXB> LVAL Change formula so it is for 802.15.1 non-orthogonal FSK.It should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types of transmitters should be split, and the table of content should be modified according to the above frequency offset definition.1 бd@׊N @@rry, Stuart J."stuar0"Kerry, Stuart J."stuart.kerry@philips.com+1 (408) 474- @@rry, Stuart J."stuar0"Kerry, Stuart J."stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips1111.3.1691EF @@rry, Stuart J."stuar0"Kerry, Stuart J."stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips1111.3.1691EF@ Replace 24 by 20 and 19 by 15.XO22220..\86 @@I@ StuI@I@tuarJ@0Kerry, Stuart J.stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips1010.2.2.1.24420ESME has not been defined.^@RC@smeLLG;977+`@>  @@indapol, Aikaik.chin"0Chindapol, Aikaik.chindapol@icm.siemens.com858-521-3546Siemens055.3.313E`@ Rearrange them.XOV:6߻ @@I@pol,I@I@chinI@"0Chindapol, Aikaik.chindapol@icm.siemens.com858-521-3546Siemens055.4.2.32337Et@ correct it.AC ACCEPT. ^B>߿ y @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.3509E!Change ""till"" to be ""until""Please change as indicated.AC ACCEPT. WWW@><<rXB> @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.45816E@l@AC ACCEPT. rXB>  @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1111.1.26250ESentence doesn't flow.@AC ACCEPT. 333 rXB>a @@lb, Jamesgilb@ieee.o"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies099.33949Ev@@XOjP:6g @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.14148E@T@AC ACCEPT. rXB>l @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.1435E@ |@AC ACCEPT. rXB> YNMM1|qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~                      ~} | { z y xwvutsrqpon m l k j ihgfedcba`_^ ] \ [ Z YXWVUTSRQPON M L K J IHGFEDCBA@?> = < ; : 9876543210/. - , + * )('&%$#"! ] @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies099.13521E@ Change as indicated.AC ACCEPT. +++rXB>91VV|qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,! s                                         ~}|{zyxwvu t s r q ponmlkjihg f e d cba`_^]\[ZYX W V U T SRQPONMLKJIHG F E D C BA@?>=<;:9 8 7 6 5 43210/.-,+*) ( ' & % $#"! @@I@nxinI@I@i@moJ@"0Li, YunxinYunxin.Li@motorola.com61-2-9666 053661-409786820Motorola11Figure 4666EThe figure is blurred. Redraw.ACz@&)fig43454666+VB> LVAL%&ZZή p ~ Z 6  w U 3  c?]7\6zQ/ oGY1 mE_9055.41831  055.418 o05PROPOSED ACCEPT IN PRINCIPLE. Inclusion of the lPROPOSED ACCEPT IN PRINCIPLE. Inclusion of the lPROPOSED ACCEPT IN PRINCIPLE. Inclusion of thePROPOSED ACCEPT IN PRINCIPLE. Inclusion of the last PROPOSED ACCEPT IN PRINCIPLE. Inclusion of thPROPOSED ACCEPT IN PRINCIPLE. Inclusion of the last name with a reference is IACCEPT. Do not know anybody that uses coherent for 1MbACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we used non-coherent.REJECT. New text should remove the need for calculationACCEPT IN ACCEPT. Do not know anybody that uses cohereACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we used non-coheACCEPT. Do not know anybody that uses coherACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we used non-ACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we used noACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we usedACCEPT. Do not know anybody that uses coherent for 1Mb/s, so ACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we ACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we ACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we uACCEPT. Do not know anybody that ACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we used non-coherent.REJECT. New text should rACCEPT. Do not know anybody that uses coherenACCEPT. Do not know anybREJECT. No requirement for IEEE 802 style.ACCEPT. Bluetooth should be spelled correctly on line 47. Remove the paragraph space between lines 47 and 49.ACCEPT. Do not know anybody that uses coherent for 1Mb/s, so we used non-coherent.REJECT. New text should remove the need for calculationACCEPT. Will delete 802.15.1 from caption.REJECT. 23 was not done, since it is expected that the 23 limit will be dropped and then use 79 world wide.; LVALK MR2JAccessVersion BuildAppTitleStartUpForm&StartUpShowDBWindow(StartUpShowStatusBarStartUpMenuBar$AllowShortcutMenusAllowFullMenus(AllowBuiltInToolbars&AllowToolbarChanges$AllowBreakIntoCode AllowSpecialKeysAppIcon,StartupShortcutMenuBar"Show Values Limit,Show Values in Indexed4Show Values in Non-Indexed*Show Values in Remote6Track Name AutoCorrect Info0Perform Name AutoCorrectCpgConversionHijriCalendarProjVerg 08.50  Form.START                p hIEEE P802.15 WG for WPANs - Comment Resolution Tool      LVAL       AA.0890 12all69-87 h1212.3.38443 h1212.3.38441 1212.3.38410 1212.3.384 1212.382ACCEPT IN PRINCIPLE. This is a property of the Barker Code as shown in Figure 7 (Power spectrum of the Barker Code) on Page 22 of D05. No further explanation is necessary to be added to the draft recommended practice. As Figure 7 shows, the Barker spreading code has a null at DC; thus, when Bluetooth is exactly in the middle of the band, the despreading correlator will attenuate it. LVAL y^C( j@! e F )  e C ! x V 4  l I '  a E # lH$tT4a?sQ/ tR0dB `>kG047104.1.1 y046-74.1.1, 4.1.2 046544.1.1  y046544.1.1  R046544.1.1 i046544.1.1 0464-54.0  m046434.1 046434.1 046424.1 m04644.0  y04644.0  W04644.0 L04644.0  04644.0  04644.0 i046334.1 046294.1 046284.1 L046234.1  y046234.1 046144.1 046134.1 046134.1  046104.1  y046104.1  04614.0  W0454.1 [04  W039233.1.4 03593.2 L035493.3 035493.3  h035483.3  035333.3 035243.2 035203.2 035203.2  035153.2 034523.2 034413.2 034403.2 }034353.2 034353.2 034153.1.18 034143.1.8 034143.1.8 R03383.1 }03353.0  03353.0 R033363.1.8 033323.1.7 R033313.1.7 }033293.1.6 033283.1.6 033273.1.6 }033233.1.4 L033213.1.3 R033213.1.3 y03316-173.1.2 R033163.1.2 033123.1  W033.1  022482.0 022482.0  022342.0  h01271.1 W01271.1  y01271.1  }012471.1  }0124-51.1 01241.1 R01231.2  h012211.2 i012211.2 L012211.2 m012211.2  }012211.2  012211.2 012201.2  012121.2  W0121.2 m01149-521.1 011491.1 R011471.1 011441.0  }01143-541.0 }01140-411.0REJECT. We can not simulate protocols that are in draft form. It would be a waste of resources. If deemed necessary, future revisions could include this work when the protocols are finalized. Coexistence definition has been debated for over 3 years in TG2 alone, and who knows how long in other groups. First the entire IEEE 802 must agree on a qualitative definition, before a quantitative definition can be agreed to.LVAL{tmf_XQJC<5.'  The structure can not be generalized easily to allow other incoming standards to be in a future version of this document. The actual structure is not only unclear (as stated in my previous comment) but it is too 802.15.1 centric. This structure needs to be improved in order to make it scalable for the other standards. This is a very important goal for the future! I recommend expending the time right now, in order to create an structure that is easily scalable for future revisions of this material. This will add a lot of value and furthermore will make the document to be more consistent with its title, since this analysis covers only two standards. An statement in the Introduction Clause (non-existing right now) can make clear that this is the first generation of a set of recommendations. Note: In few words: Imagine you were asked to do the same with 15.1, 15.3, 15.4, and all the dot11's, what would be the structure of that document? Given that, now trim down to dot15.1 and dot11, this is an structure that will be scalable.LVAL)BFDxP% P% ~? P% 0 x ů     * R z      * Z z  x     H p       P p                      * R z      * Z z              d     d   d                Main.CommentIDMain#Main.CommenterName%Main.CommenterEmail%Main.CommenterPhone!Main.CommenterFaxMain.CommenterCoMain.ClauseMain.SubclauseMain.PageMain.LineMain.CommentTypeMain.Comment'Main.SuggestedRemedyMain.Response#Main.CommentStatus%Main.ResponseStatus     0hB@   x   x   x   x  * x  R x  z x   x   x   x   x    x  * x  Z x  z x   x  Mainp ` ` x  =B@c_sc_pg_ln  x          H   p          (    0   8    @   P H  p P   X x      H p        P p   x   x   x   x  * x  R x  z x   x   x   x   x    x  * x  Z x  z x   x  Main             *   R   z                  *   Z   z    ( x      H p        P p        8 x   8 0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  0  8 `%   x ` x   x   x   x   x   x   x   x   x   x  @ x  $@ x  $@ x  $ x   x   z  $  "  0  h        H        (   ` 0   @   P  ` @ p   0  h        dH    d  d  (  `        @ h?     ( 0 8 @ H P X ` h p x  0 h    H    LVAL( @ @ @ @ @ @ @ @ @ @ @ @ @ @00000000 0  0  0  01 111 2222333334444555 57%7'7(7&8)8+8,8*9-9/909.:1:3:4:2;5;7;8;6<9<;<<<:===?=@=A=>>B>D>E>C?F?H?I?G@J@L@M@KANAPAQAOBRBTBUBVBWBXBSCYC[C\C]C^C_C`CaCbCcCdCC C CC CZDDDD D D D D DDD ( `    @ x Main  PrimaryKeyCommentID  v   0ů  q                             #  0 h# " % x Main x   x   x   x  @ x   x   0! H" h! X" ! h"  ! x" " "  d  0!  dh!  d!  ! " d@ @ d@ d@ @             @     h# " # $ # $ $ $  H$ $ $ $ 0          $ % x S                                                                                                                                         !"#$%& '!(")#*$+%,&-'.(/)0*1+2,3-4.5/60718293:4;5<6=7>8?9@:A;B<C=D>E?F@GAHBICJDKELFMGNHOIPJQKRLSMTNUOVPWQXRYSZT[U\V]W^X_Y`Za[b\c]d^e_f`gahbicjdkelfmgnhoipjqkrlsmtnuovpwqxryszt{u|v}w~xyz{|}~           !"#$%& '!(")#*$+%,&-'.(/)0*1+2,3-4.5/60718293:4;5<6=7>8?9@:A;B<C=D>E?F@GAHBICJDKELFMGNHOIPJQKRLSMTNUOVPWQXRYSZT[U\V]W^X_Y`Za[b\c]defghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOpqrstuvwIPJQKRLSMTNUOVPWQXRYSZT[U\V]W^X_Y`Za[b\c]defghijklmnopqrstuvwxyz{|}~      qYGNEEGGGGY `Y  Y Y Y Y Y Y AttributesDataTypeFieldNameIndexTypeSkipColumn SpecID Start WidthddEGdddE^dYY Index1PrimaryKeyv1X@@@DG|W.Z/ i G ! ~ U &  W -  [ 3 v J # R.Y._5 vO"  @  @@@ @ SOYkfJmMWSSYbJ^iQfdimkSWdobOOdUUYbUSYbfomS`JYbSfYMmoiQ8SfYMmoiQ86SfYMmoiQ88SfYMmoiQ8:SfYMmoiQ8<SfYMmoiQ8>SfYMmoiQ:SfYMmoiQ<SfYMmoiQ>SfYMmoiQ@SfYMmoiQB SfYMmoiQD!SfYMmoiQF"SfYMmoiQH#SidoUW$SkmJmokfdfof%kmJim&Md``dbomY^YmYQk'+UQmJ^^Md``Qbmk(+UQmJ^^Md``Qbmk8)LYUSdbmMd``YmmQQiQfdim*Md``QbmQiSo^^++Md``YmmQQiQfdim,WdmYmQ`k-iQfdimLvMd``QbmYO.idoUWY`fdWrittenDate%   VoterStatus%  vTopic%  }SuggestedRemedy%"  Subclause%  gResponseStatus%!  }Response%  Page%  Line% LastModDate% DispatchDate% CreateDate%  CommentType%  YCommentStatus%   CommentID%  3CommenterPhone%!  CommenterName%   DCommenterFax%  CommenterEmail%!  T%CommenterCo%  }Comment% Closed_UnsatisfDate%&"  yClause% Accept_RejectDate%$ Z WrittenDate  VoterStatus  2Topic  }SuggestedRemedy"  2Subclause  ResponseStatus!  }Response   Page   Line 4 LastModDate G DispatchDate ! CreateDate  CommentType  CommentStatus   CommentID  2CommenterPhone!  CommenterName   <2CommenterFax  CommenterEmail!  n2CommenterCo  }Comment  Closed_UnsatisfDate&"  Clause m Accept_RejectDate$ 6 WrittenDate  Topic  }SuggestedRemedy"  x Subclause  ResponseStatus!  }Response  Page  Line  LastModDate ) DispatchDate  CreateDate  CommentType  CommentStatus   CommentID  3CommenterPhone!  CommenterName   DCommenterFax  CommenterEmail!  RCommenterCo  }Comment TClosed_UnsatisfDate&"  qClause BAccept_RejectDate$  DF  FF3FDFRFqFxFFFF FFFF F FF F)F 6FBFTFF  F F F<FnFFF*F'F&F"FF+F(F!F)F,!F#4F%GF$ZF.mFFF-%F8% F6%F4%3F7%DF5%TF3%yF0%FB%F?%F>%F:%F2%FC%F@%YF9%gFA%vFD%F;%F=%F<%FF%F/%F1%FE1cyzzzz z z z z zzzzzzzzzzx x x x x xxxxxxxxllll l l l l llllllllllfff f f f f ffffffffffbb b b b b bbbbbbbbbb]] ] ] ] ]]]]]]]]]][[ [ [ [ [ [[[[[[[[[[ W W W W WWWWWWW~W}W|W{Uz Uy Ux Uw Uv UuUtUsUrUqUpUoUnUmUlRkRj Ri Rh Rg Rf ReRdRcRbRaR`R_R^R]R\L[LZ LY LX LW LV LULTLSLRLQLPLOLNLMLLHKHJ HI HH HG HF HEHDHCHBHAH@H?H>H=H<@;@: @9 @8 @7 @6 @5@4@3@2@1@0@/@.@-@, <+ <* <) <( <'<&<%<$<#<"<!< [ @@I@JameI@I@ee.oL@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies099.0345E@ R@ACACCEPT IN PRINCIPLE. !!!rXB> LVAL J@J@J@J@J@J@J@J@J@J@ J@ J@ J@J@J@J@J@J@ J@ J@ J@J@J@J@J@J@J@J@J@J@J@J@J@ J@ J@ J@J@J@J@J@J@J@ J@J@J@MR2OrderByOnColumnWidthColumnOrderColumnHiddenRequiredAllowZeroLengthDisplayControl FilterOrderByValidationRuleValidationTextOrientationDescription FormatInputMaskCaptionDefaultValue$UnicodeCompressionN   0 (Main.[applied edits]l CommenterName      m n"CommenterEmail      m n"CommenterPhone      m jCommenterFax 6     m hCommenterCo      m dSubclause      m hCommentType      m l CommentStatus Y     m n"ResponseStatus      m VComment Y     f$SuggestedRemedy      ^ Clause      m ZPage X     m ZLine      m ?CommentID   XResponse      \ Topic      m JCreateDate    LLastModDate    NDispatchDate    LWrittenDate    X("Accept_RejectDate    \,&Closed_UnsatisfDate    hVoterStatus      m P applied edits     ku E  p<'($'(@ A@0AD"@5JI@5KI$@H DP U 8C' "0H ѤȈr0J2HU 8C' "0LVALdF P l x  ˘  | |@.LwdP.LwP"frequency nulling" has not yet been defi"frequency nulling" has not yet been defined; since this term usually refers to matching the frequencies of two independent sources, it's quite a puzzle what this means here without a definition. (As an aside, the definition given later in the text more closely resembles an adaptive notch filter ... why not call it that?)""respectively"" is confusing here, since there are three precedents bu"frequency nulling" has not yet been defined; since this term usually refers to matching the frequencies of two independent sources, it's quite a puzzle what this means here without a definition. (As an aside, the definition given later in the text more closely resembles an adaptive notch filter ... why not call it that?)""respectively"" is confusing here, since there are three precedents but only two sequels.commas needed before and after ""say""While I know this is the definition in the IEEE dictionary, defining ""interference"" using the word ""interfere"" doesn't provide much light on the matter--especially since ""interfere"" is not in the IEEE dictionary.Style error: Definition is a complete sentence; all others are not.The phrase ""set of rules"" is used in many definitions, and is undefined.Line 3 says 2 MHz is included; line 7 says it is not.Figure shows Bluetooth devices instead of 802.15.1 devices.It's not clear to me why a narrowband interferer will be attenuated more at the middle of the spectrum than at 1 MHz away.This sentence doesn't make sense.I don't see the curve for 802.15.1.The word ""required"" doesn't make sense here.Should be 802.11 instead of 802.15.1.Table number shouldn't include em-dash.Table numbers should not include the em-dashes.This paragraph is poorly written.Two periods at the end of the lineRefers to Bluetooth 1.1 hop kernelMissing period at the end of the sentence.""Committee of the IEEE Society"", and ""Abstract"" are in incorrect position..1O MM0 iK* [BBFAd@`@0Seals, Michaelm0Seals, Michaelmseals@intersil.com321-724-7172Intersil6298E!Bad citation of Bluetooth spec.^@PXO|zxttrbbJ$߾0Seals, Michaelmseals@intersil.com321-724-7172Intersil54.2.1226TR@ KR@PXO~trbbJ$߿10Seals, Michaelmseals@intersil.com321-724-7172Intersil54.2.12152EB@ K@PXO~trbbJ$߿0Seals, Michaelmseals@intersil.com321-724-7172Intersil54.1191EWhy is there (23)?!Remove this or add explanation.XO~ztrbbJ$߿ ;@I@MichH@H@I@I@0Seals, Michaelmseals@intersil.com321-724-7172Intersil05Figure 41828EF@ KAdd the 802.15.1 curve.AC~@A#figure4 \@>߿ ;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.6.31620E\@KRemove the word ""required"".AC ACCEPT. \@>߿  ;@H@MichH@H@H@I@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.6.21544E"Missing parentheses in equation.Add parentheses.ACACCEPT. Q is a function.>>>\@>߿; ;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.6.21539EJ@K Replace.ACT@)\@>߿  ;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.5143EN@KRemove the em-dash.AC ACCEPT. \@>߿;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.3139E^@KRemove the em-dashes.AC ACCEPT.   \@>߿ 0Seals, Michaelmseals@intersil.com321-724-7172Intersil44.1.48EB@K@PXO~trbbJ$߻;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil044.1623E!Remove this one line paragraph. Remove it.AC ACCEPT. \@>߿ ,+;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil033.1.3321ET@K Add it.AC ACCEPT. \@>߿ ;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil011.2221E802.119 WLAN 802.11 WLANAC ACCEPT.   \@>߿ +1`<@H@y, EH@H@awayL@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola033.1.8336T@K@PAC.@X@>9h1xN  A0-5F99-101B-AF4E-00AA003F0F07}#9.0#0#C:\Program Files\Microsoft Office\Office\MSACC9.OLB#Microsoft Access 9.0 Object Library*\G{00025E01-0000-0000-C000-000000000046}#5.0#0#C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO\DAO350.DLL#Microsoft DAO 3.5 Object Library*\G{00020430-0000-0000-C000-000000000046}#2.0#0#C:\WINNT\System32\stdole2.tlb#OLE AutomationZ*\G{0002E157-0000-0000-C000-000000000046}#5.3#0#C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB#Microsoft Visual Basic for Applications Extensibility 5.3 1=  8PWDOPXMCJFYYIETRRDVRERANSHQ_013da931af@Report_Big-Font Committee reportY8IHXNTKHMOBNBIELLNZBVGFUNIEKN023da931af$Form_fFinalReports78ZJUZAACTHZOJGEWLVNXBBFBCKNGK033da931afForm_STARTu08FHZJDUHLXIVLZDLLYKVSIXIDHVYG043da931afForm_fRoughH8KTJXXD_BEXSTCEPRRXTKKUNGHEJE053da931af Common utilitiesR+`?8QDIFHQLDRXXYXDAYTXOEKAJXRGTL063da931afIForm_fInputxD8QHZWENKNJFREAEUZWJHPNSXPZTTK073da931af$Form_fHoundDoggings8RDDGEBEXXEWDUDWWKMTVDEIOVOFJ083da931af%.Report_Committee reportNY8YMGUNXBUGJPWMDVRVNXUIEOZFCEN093da931af'Form_fPIcture9a8OVDWETNJDGTFEEYAOCJWEHEPMLC_0:3da931af1Form_fPicture1U8TJJVUDFZFIXLWDCHEQEGHWUBIYKN0;3da931af3Form_fPicture2a8CSKLRJGABJRGBEJQXUDECBGAONUM0<3da931af5Form_fPicture3a8BMSKIRLVCLVXIEFHCRCOCZRKQTBL0=3da931af7Form_fPicture4 a8HWKQRDDWWMARQDGVASNXCOAGMSIC0>3da931af9Form_fPicture58a8XICELKKNRMSSXDMMIKWBDPUCPRJJ0?3da931af;Form_fPicture6Pa8XUAAEVKECWXXIEDEHDVGHIZMOWG_0@3da931af=Form_fPicture7ha8WOUASYHICSPWHEZVEALJGDVQRVNE0A3da931af?Form_fPick @@I@JameI@I@ee.oJ@"0Gilb, Jamesgilb@ieee.org858-538-3903858-229-4822Appairent Technologies1010.2.1431EAccess Point should be APPlease replace with acronym.AC ACCEPT. RRR;977 rXB> LVALZ~  : H p .D`Pf¤2          say, ""Mb/s WLAN"" not just ""Mbit/s."" say, ""Mb/s WLAN"" nUse change to read: The impact of interference on WLAN etc..Use complete sentences to describe the scope of the document.Improve the explanation in the text.Fix the Bluet{99} citation error.Define phi2 as deviation, and as a function of t and b, like the BT case in 5.4.1.1.Should be ""symbol intervals,"" not ""symbols.""Keep a single style format thoughout the symbol list. Include units in all definitions.To define A, mention that it is the peak amplitude.""The GFSK signal can be represented as ([B1], [B6], [B9])...""""Bandwidth"" should be lower case.Delete the reference to orthogonal FSK, and ensure that the following technical derivation is still valid without the assumption of orthogonality.""The intended transmission is attenuated by the path loss as defined in subclause 5.2 to the receiver. The transmitted signal power, less the path loss, is the signal power at the receiver.""change to, ""due to near-field and implementation effects.""Either change the sentence to ""An adaptive notch filter can be used to ..."" or define the term ""frequency nulling"" prior to its use.The coexistence modeling approach used is based on detailed simulation models for the Radio Frequency (RF) channel and the Medium Access Control (MAC) and Physical (PHY) layers developed in OPNET and ANSI C, respectively.Avoid using ""interfere""--for example, ""...that might reduce the quality of desired received signals ...""""The ability of each of a set of (perhaps disparate) systems to perform specified tasks in a given shared environment.""As I understand the draft, 2 MHz is not included. If so, remove it from line 3.Replace with reference to Figure 53Clean up the reference to Bluetooth (802.15.1?)Provide an explanation of this reasoning.Replace with ""The power spectrum of the Barker codes is: Lee [B11]""Please rewrite this section using better English and a more coherent flow of ideas. LVAL |qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,!                  ~| y wuspol k ihgecba`_^ ] \ [ Z WUTSRQPM L K HGFEDB@?> = < 9874210/. , + )(&%             }}}ACCEPT IN PRINCIPLE. Will contact IEEE editor for clarification on items. 1) There is a special formatting symbol (might be tab) currently after the colon as part of the FrameMaker template. 2) Tables are not drawn by hand, they are drawn with the FrameMaker IEEE template. 3) This is due to the long title and the fact that the temple has the title in a large font. Since the title can not be shorten, then the font must be change, but then this would violate the IEEE 802 template. 4) Did not change IEEE 802 template on centering Copyright. 5) Contents will be deleted, as it was part of the IEEE 802 template. 6) No IEEE style requirement for this action.@1NNC IxHGF\EkDvCBAn@0Callaway, Eded.callaway@mot0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola5Table 3, 4, 513T@SAdd a sample calculation.XOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.3.21145TR@S@ PXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.21035Tf@Sx@ PXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.3.2922E@K@ PXOnP m0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.2826E@K@ PXOnP l0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.1.3749E""exact same"" is redundant.delete ""exact""XOnP k0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.1.1654EL@K Add commas.XOnP N0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.1.8336T@K@PXOnP U0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.1.7331E@KDelete ""it is.""XOnP V0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.1.3321Eperiod missing. add period.XOnP `<@H@y, EH@H@away@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola033.1.2316TR@ @PRU@definition  X@> `<@H@y, EH@H@away@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola033.138TR@KDefine ""set of rules.""RU@definition44(X@> `<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola011.223Tj@K@PAC@ 2ed_note X@> S ,;@H@MichH@H@s@inI@0Seals, Michaelmseals@intersil.com321-724-7172Intersil09Table 103310-20E BT is used instead of 802.15.1Replace BT with 802.15.1.AC ACCEPT. <<<%#!!\@>߿9LVALH  z  p ǰ(4t`    0Seals, Michaelmseals@intersil.com321-724-7172IntersilSome text in Bold is overwriting the existing text.Variables from equations that appear in text need to be italicMany 'PDF' Artifacts on first page""vendor specific"" is not what is intendedSome text in Bold is overwriting the existing text.Variables from equations that appear in text need to be italicMany 'PDF' Artifacts on first page""vendor specific"" is not what is intended, I think.Incorrect period placement and capitalization: ""above. (See 12.1)""extra space before period: ""transmitting or receiving .Additional""This puSome text in Bold is overwriting the existing text.Variables from equations that appear in text need to be italicMany 'PDF' Artifacts on first page""vendor specific"" is not what is intended, I think.Incorrect period placement and capitalization: ""above. (See 12.1)""extra space before period: ""transmitting or receiving .Additional""Should be ""symbol intervals,"" not ""symbols."" (We assume possibly multiple bits per symbol, but not multiple symbols per bit.)List of symbol definitions does not keep a single format throughout (extraneous semicolons and ""ands"" abound). Also, units should be included in all symbol definitions.To define A, mention that it is the peak amplitude.References should be cited by number [1] or author (Smith 2002), not both Smith [1].""The GFSK signal can be represented by Murota [B6], Aulin [B1], and Steele [B9] as"" is really awkward (I mean, the rest of us can also represent the GFSK signal the same way).""Bandwidth"" should be lower case.""differential"" QPSK, not ""differentiated.""15.1 is *not* orthogonal FSK. The modulation index h = 0.315, not 0.5.Where did these numbers come from? A sample calculation would be most welcome.""The intended transmission is attenuated by the path loss as defined in subclause 5.2 to the receiver. This is the signal power at the receiver."" This is not correct.""near-field"" is not an ""implementation effect.""LVALN  REJECT. These sections have been moved to appendices, so they are not normative. Also, the simulations at 1Mb/s were within 1dB, and at 11Mb/s were within 3dB over a 20dB range, so there was actually quite good agreement between the two models.$19 JIHaGGFIEVDKCGBTAPA!0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.33824T@@VXOnP 0Callaway, Eded.ca!0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.33824T@@VXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.33824EAmbiguous text.@VXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.2372429EStyle is informal.@PXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.13548Tx@H@PXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola66298ECitation error.B@PXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.1.2205E!Symbol list style inconsistent.@PXOnP `<@`E@y, E`E@callaway0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.4.1.1205E@ S`@PXOP860Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.1.11941EV@ S@PXOnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.1.11936Ef@Sf@PXOnP  /&`<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.4.1.11929Eb@S~@PAC ACCEPT. ###  X@>y%`<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.4.11851EF@SF@PAC ACCEPT. X@>I$`<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.3.6.3165T\@SChange to ""differential.""AC ACCEPT. ==='%##X@> #`<@H@y, EH@H@away @0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.3.6.11442TR@S$@ PAC@1#orthogonal&&   X@>9LVALT< v  2T@change text to ""theoretical coexistence models; and finalchange text to ""theoretical coexistence models; and finally the three coexistence mechanisms.Is there any regulatory issues with having an adaptive frequency hopping scheme. I know the FCC was considering allowing this but did they actually approve it? How about in other countries?Improve. Make a better introductory statement. Here you need to remove your engineering hat and use descriptions that non-telecom people (marketing, journalist) can understand and talk about.paragraph between lines 32-36 needs to be reworked.should be changed to read:............one can write these equations for the decoded phases as proposed by Van Nee [B15].should be changed to read: Since the complexity of the optimal decoder for CCK may to too high for practical implementation, the sub-optimal method can be used to decode the received phases with the following equations developed by Van Nee [B15].See above other standards. This is a very important goal for the future!Either add a very good justification of the scenarios picked to make them representative of "all of them" or change methodology. See aboveAdd more complete introductory material and improve structure of document. Try to make a good mapping of the document at the very beginning so the reader can have a smooth ride. Adding an "Introduction Clause" will help a lotProvide an overview (more than a paragraph)mprove. Share this document with Jennifer Longman - IEEE Standard Editor. She will provide good input -for free-. Do it before recirculationImprove. Share this document with someone that does not knows anything about WLANs/WPANs and you will get a lot of valuable input.suggest ""implementation specific.""Check spacing before and after periods throughout table.Compare and contrast the simulated results with the earlier theoretical predictions.Should say, ""Thus, the interference between the WLAN FH and TG1 systems is limited.""10 KK IF@MCBg0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation44.15T?`>@H@ez, H@H@gutiI@0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation044.15T@Z@VAC@2^@> `>@H@ez, H@H@guti0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation033.1E@$ @VAC8@QV860Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation11.22E@X@VXOjT&<@>@H@r, BH@H@eist@0Treister, Bijanb.treister@bandspeed.com.au+61396146299+61414854414Bandspeed044.064ENo comma before the 'and'Remove CommaRC@777+)'' ^@>i;@>@H@r, BH@H@H@@0Treister, Bijanb.treister@bandspeed.com.au+61396146299+61414854414Bandspeed033.1.4923T@4Up to the group.RC@2&&&^@> :@>@H@r, BH@H@eistI@0Treister, Bijanb.treister@bandspeed.com.au+61396146299+61414854414Bandspeed011.127Eh@XRemoveAC@Ced_note ^@> 9@>@H@r, BH@H@eistI@0Treister, Bijanb.treister@bandspeed.com.au+61396146299+61414854414Bandspeed0000141Ef@SMoveAC@B^@> /0Treister, Bijanb.treister@bandspeed.com.au+61396146299+61414854414Bandspeed1212.28023T@X@XOt\&7@>@H@ KaiH@H@ak@tI@0Siwiak, Kaikai.siwiak@timedomain.com954-755-6828256-990-9062Time Domain05E|@S Italicize variables in textAC ACCEPT. %%%   V@>!4`<@H@y, EH@H@H@@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1212.1.1.171217Ej@SH@VRU@B  X@>3`<@H@y, EH@H@away@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola11116138E@S""above (see 12.1).""RC@A%%%X@>2`<@H@y, EH@H@awayI@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1010.4.16038E ""t the""delete ""t.""AC ACCEPT. t_theCC<$"  X@>LVAL . 7#2)3BM1"0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola5Table 3, 4, 513T@SAdd a sample The clause is called Coexistence Model Overview, but there is no overview, there is just a description of the The clause is called Coexistence Model Overview, but there is no overview, there is just a description of the simulation setup.Check the document for compliance with IEEE style manual. Examples: 1) Clause 3.1: After a colon leave at least one space 2) Tables appear to have a problem (may be just a PDF setting), but observe the vertex of several of then, they look as they were draw by hand. 3) Frontmatter is in very bad shape (see cover page) 4) Copyright footer is not centered 5) Before the TOC there is an empty page called "Contents"??? 6) recommend leaving an empty page per section, to make an eThe clause is called Coexistence Model Overview, but there is no overview, there is just a description of the simulation setup.This clause contains several sentences stating the same (lot of redundant information). Make sure the document "looks" as written by one person as opposed to several authors. There are a lot of floating paragraphs all around the document. Example Page 6, Clause 4.1: "This recommended practice only addresses IEEE 802.11 WLANs and IEEE 802.15.1 WPANs." So what? I understand you need to clarify the scope of the work, but this should be complemented with the idea of "in the future with the new incoming standards in dot15 and dot 11 this document will be expanded". This text is in the document but is somewhere else!Editors note still included here. Should be removed.This section is in conflict with the Adaptive Frequency Hopping proposal in the Bluetooth SIG. This section has features which are not included in the Blutooth SIG proposal. This section could result in the production of a defacto standard of Adaptive Frequency Hopping which would not be Bluetooth compliant, nor interoperable with the Bluetooth Adaptive Hopping Standard. LVALN  MR2OrderByOnColumnWidthColumnOrderColumnHiddenRequiredAllowZeroLengthDisplayControl FilterOrderByValidationRuleValidationTextOrientationDescription FormatInputMaskCaptionDefaultValue$UnicodeCompressionN   0 (Main.[applied edits]l CommenterName      m n"CommenterEmail      m n"CommenterPhone      m jCommenterFax 6     m hCommenterCo      m dSubclause      m hCommentType      m l CommentStatus Y     m n"ResponseStatus      m VComment Y     f$SuggestedRemedy      ^ Clause      m ZPage X     m ZLine      m ?CommentID   XResponse      \ Topic      m JCreateDate    LLastModDate    NDispatchDate    LWrittenDate    X("Accept_RejectDate    \,&Closed_UnsatisfDate    hVoterStatus      m LVAL ɠ FFtdJdGGRange"Many variables are used without indicating their meanings, namely: NG, Nmin and p(k)."Range called out in text does not match figure, Figure says ""SNIR"" text says ""SINR""How is T1 decided? Why the 1-10ms range? Is T1 to be negotiated by the devices or should it be the sa"Many variables are used without indicating their meanings, namely: NG, Nmin and p(k)."Range called out in text does not match figure, Figure says ""SNIR"" text says ""SINR""How is T1 decided? Why the 1-10ms range? Is T1 to be negotiated by the devices or should it be the same within BSS?In Figure 4, there is no curve for the 802.15.1 receiver.For non-collaborative proposals ... suggesting a ""change to the sequence of hops"".IEEE 802.119 should be IEEE802.11BThere is an editor's note that 2 Mbps is not included.the word expire should be changed to expiration.Follow IEEE guidelines by capitalizing the first letter of primary words in Section Headings and Figures.question: It is not clear to me as to why the subintervals are not equal.The explanation of the spectrum factor is not adequate. Specifically, how this factor is determined.As is the sentence does not make sense.Improve wording use "issue" instead of "Problem" Clause 4 states "Coexistence problem and 4.1 start talking about interference!!!! There is no consistency. Text is assuming previous knowledge not previosly explained. Need to add a better background - more descriptive! What is the difference between the interference problem and the coexistence problem? I know this looks editorial, the problem is that 90% of the people will never read the entire document, they will read just the Overview clauses, if this clauses are not clear, there is no hope. The value of this document is exactly in this part (description of the issue) and in the conclusions (solutions to the issue). The "How" this conclusions were achieve is for consumption of a very reduced market.1MLK: KFFYERDIC>B;A8@4@!Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs66.43040E@XOpV"Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs66.43032Ef@VXOpV"Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs55.4.2.32440E@VXOpV"Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs55.4.2.2234E@ VXOpV"bDydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs55.3.21147E@ZXOpV"H0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation1TRL@@@ VXOjT&vDydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs44.3.2920EN@ZXOpV"F>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs044.1.4815Eremove the unnecessary "be".ACL@D@@@4200Z>> E>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs044.1.2738Eremove the unnecessary "in".RC REJECT. KKK4200Z>> D>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs044.1.1713Er@PAC ACCEPT. ---Z>> `>@H@ez, H@H@guti0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation10TR@~ See aboveAC^@   V860Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation4TR@4@ VXOjT&q0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation44.3TR(@Z@ VXOjT&@`>@H@ez, H@H@H@I@0Gutierrez, Josejosegutierrez@eaton.com414-4496525414-8706525Eaton Corporation044.2823-36T@XV@VACr@2   ^@>  LVALЊ  j |mI constantly found myself turning back and forth between page 33 and the Figure I happend to be looking at.Table 10 calls the four simulated topologies ""experiments"" subsequent text and figures use scenarioText describing figures repeatedly uses ""gives the .....""The structure of the document is not clear. Need to improve in order to make a good document. Examples: 1) Clause 10, 11 and 12 can all be under a heading "Coexistence Mechanisms" 2) Bookmarks in PDF files do not reflect an actual layout of the document. 3) There is no "Introduction", the "General Description" does not do a good job in this and furthermore is focused in the "problem" statement and does not mentions anything about why this document is organized in the way it is. The focus of the document is more in the modeling rather than in the problem stated in the title.It looks to me that this is based in a particular scenario and does not cover more general cases. There were closed form analyzes not based on simulations (See Howitt et al) in the IEEE proposals. Why these were not mentioned in this work? I do not see an clear explanationI constantly found myself turning back and forth between page 33 and the Figure I happend to be looking at.Table 10 calls the four simulated topologies ""experiments"" subsequent text and figures use scenarioText describing figures repeatedly uses ""gives the .....""The structure of the document is not clear. Need to improve in order to make a good document. Examples: 1) Clause 10, 11 and 12 can all be under a heading "Coexistence Mechanisms" 2) Bookmarks in PDF files do not reflect an actual layout of the document. 3) There is no "Introduction", the "General Description" does not I constantly found myself turning back and forth between page 33 and the Figure I happend to be looking at.Table 10 calls the four simulated topologies ""experiments"" subsequent text and figures use scenarioText describing figures repeatedly uses ""gives the ....."" LVALФ j @ @I don't understand the headings on this table 1 2 3 other Also, the entries in the table need to be clarified.Clauses 5, 6, 7, 8 and 9 offer interesting technical analysis but should be located to the end of the draft as a series of appendices. An implementer does not need to know all the background analysis when implementing the standard.The opening comments indicates that this standard is for a very specific case of DCF 802.11b with 802.15.1, and it appears this standard is being called Part 15.2. But what are we going to call coexistence standards that follow?12.2 Adaptive frequency hopping mechanism - I may be out of date on this issue, but I thought the FCC did not allow AFH in the 2.4 GHz ISM band. This is not a criticism, just a comment. The method shown seems to be well thought out. Has anyone actually built a device that implements this procedure?The structure can not be generalized easily to allow other incoming standards to be in a future version of this document. The actual strcutture is not only unclear (as stated I don't understand the headings on this table 1 2 3 other Also, the entries in the table need to be clarified.Clauses 5, 6, 7, 8 and 9 offer interesting technical analysis but should be located to the end of the draft as a series of appendices. An implementer does not need to know all the background analysis when implementing the standard.The opening comments indicates that this standard is for a very specific case of DCF 802.11b with 802.15.1, and it appears this standard is being called Part 15.2. But what are we going to call coexistence standards that follow?12.2 Adaptive frequency hopping mechanism - I may be out of date on this issue, but I thought the FCC did not allow AFH in the 2.4 GHz ISM band. This is not a criticism, just a comment. The method shown seems to be well thought out. Has anyone actually built a device that implements this procedure?z1N   @@I@pol,I@I@chinJ@"0Chindapol, Aikaik.chindapol@icm.siemens.com858-521-3546Siemens11Figure 43, 45, 46E These Figures are hard to readreplace them.AC@$2fig434546HH=1/--^B>߹1|qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,!                   ~| y wuspol k ihgecba`_^ ] \ [ Z WUTSRQPM L K HGFEDB@?> = < 9874210/. , + )(&%             }}}} } } } }}}}}}yy y y y yyyyyyyo o o o ooooom m m m mmmmmm~m}mziyix iw iv iu isiriqipioinilii hh hdhchbhah_h^h\ gZ gY gX gWgVgUgTgSgRgQgPgOgN[M [L [K [J [G[F[E[D[> W< W:W9W7W5W4W@?@H@, PaH@H@H@@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.4.42826EB@x@kRCREJECT. Remove the sentenceZB>߿  LVAL REJECT. 1) There is no suitable single picture form to include in the draft that could directly be used in the tool. OPNET has many different hierarchies including node, process, and network levels. A picture representation would not be very straightforward and therefore defeats the purpose of added clarity in the Recommended Practice document. 2) The OPNET models are currently available on the NIST web site at http://w3.antd.nist.gov/wlan_wpan.shtml. The reviewer s comment is well taken. A sentence can be added in the draft to point to the models. However, since this is a web site that can be redesigned or changed in the future, I would not put the link in the draft Recommended Practice yet. Therefore, TG2 should decide what and how to distribute the models as appropriate. LVAL |qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,!                      ~| y wuspol k ihgecba`_^ ] \ [ Z WUTSRQPM L K HGFEDB@?> = < 9874210/. , + )(&%             }}}} } } } }}}}}}yy y y y yyyyyyyo o o o ooACCEPT IN PRINCIPLE. The following is added to subclause 9, page line Replace lines 17-19 on page 32 subclause 9 by the following ( starting from ""All simulations are run "" until ""is present""): ""A simple 4-node topology is chosen in order to better identify the interference problem and the parameters affecting it. This is the simplest topology required that could lead to interference. A mix of data and voice traffic is chosen as a representative set of applications running on IEEE 802.11 and 802.15.1."" LVAL N  ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~                      ~} | { z y xwvutsrqpon m l k j ihgfedcba`_^ ] \ [ Z YXWVUTSRQPON M L K J IHGFEREJECT. This is contained in the equations (especially Nmin) Bad channels are needed because 1) the good channels to be used can be less than the minimum number of channels required by regulation; or 2) the channels in ISM band are too occupied by other devices, e.g., 802.11b, to provide enough good channels for AFH. (This is contained in the equations (especially Nmin))1$ @@H@ammeH@H@H@K@"0Shellhammer, Stephenshell@symbol.com(631) 738-4302Symbol Technologies, Inc.055.4.42823T(@~@ACF@?  jB>߿ LVAL|qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,! ihgecba`_^ ] \ [ Z YWUTSRQPM L K HGFEDB@?> = < : 987654210/. , + )(&%               }}}} } } } }}}}}}yyyy y y y y yyyyyyyyoo o o o o oooooooooomm m m m m mmmmmmm~m}mziyix iw iv iu iriqipioinilii hh hehdhchbhah`h_h^h]h\ g[ gZ gY gX gWgVgUgTgSgRgQgPgOgN[M [L [K [J [I [G[F[E[D[> W= W< W:W9W7W6W5W4W3W2W1U/ U. U, U+U*U)U(U'U&U%U RFigure title says 802.15.1 is included, but there are only 4 lines in the graph, and the legend suggests that the 4 lines represent 802.11.l LVAL| |qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,!                    ~| y wuspol k ihgecba`_^ ] \ [ Z WUTSRQPM L K HGFEDB@?> = < 9874210/. , + )(&%             ACCEPT IN PRINCIPLE. The paragraph will be changed to "Channel estimation can be inferred from the built-in ACK mechanism implemented in 802.11 and 802.15 so that no explicit communication about the channel state is needed between the transmitter and the receiver. In the case of 802.15.1, the receipt of a packet with the NACK bit set in the header can indicate that the previous packet sent is lost. Similarly, a receiver expecting an acknowledgement, infers that packet it has sent is lost if it cannot correclty decode the packet containing the acknowledgment bit. In the case of 802.11, if no ACK is received for a frame that requires it, the transmitter infers that the packet it sent is lost. ".LVAL#аJJH `    ^ ^^ʲ X FFFRemove formula or unify with previous formula (once once is added) for SIR.What is frequency nulling ... provide explanation.Define ""B"" and change ""Nc/B "" to a correct formula or simply delete ""Nc/B"".Change the sentence on lines 53-54 to read: ""IEEE 802.15.1 specifies a maximum hopping rate of 1600 hops/s for data transfer.""Change ""BER for SINR values in the range -15 to 20dB"" to ""BER for SINR values in the range -10 to 10dB"" Change X axis label on Figure 4 to read ""SINR (dB)""the sentence should start with: The clause defines themodify the sentence on lines 4-5 to read: the model available in the OPNET library was extended to interface to the channel and physical layer models described in the previous clause.Change ""since that effects the interference power level"" to ""since the physical spacing affects the interference power level""Change ""dwells on a given frequency for say 100 ms"" to ""dwells on a given frequency for approximately 100 ms""Make ""three channels in the ISM band"" read ""three non-overlapping channels in the ISM band""Should be ""IEEE 802.11"" or ""IEEE 802.11b""Please provide the rationale for T1's range, and how it will be decided or negotiated.Remove reference to Bluetooth and replace with 802.15.1Offer explaination of why 2 Mbps is not included. Having just the note is not sufficient.Make clauses 5, 6, 7, 8 and 9 as series of informative appendices.Name this Part 15.2A and use 15.2B, etc. for whatever follows.introduce "the " before procedure.introduce the word Section before 12.1.Introduce the word Section before 12.1.do not carry the question mark to the next line.place a period at end of sentence.separate the words "have greater".the period should not be carried to the next line.the word to be used is additional.introduce "of" between activity and a number.Table 17: the table should be combined on one page.remove "on" before the word dynamically.F1< 8M S soG^BtpA!E>@`E@ichaelMichael.DyDydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.4.16038E@XO Delete t(((![>@H@ichaH@H@H@I@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.4.16038E@ACACCEPT. Delete tt_theAA: Z>>.Y>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.6 Table 26575ED@fAC ACCEPT. AAA*(&&Z>>9X>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.5 Table 255535Eseparate "current 802.15.1 ".AC ACCEPT. bbbKIGGZ>> W>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.5 Table 255528ED@fAC ACCEPT. CCC,*((Z>>!U>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.3 Table 215242Ed@fAC ACCEPT. CCC,*((Z>> T>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.3.15138ED@fAC ACCEPT. 111  Z>> S>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.35037EZ@fACACCEPT IN PRINCIPLE. :::Z>> R>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.2.45022E@kACACCEPT IN PRINCIPLE. ???  Z>> +P>@H@ichaH@H@l.DyN@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.2.2.6.247Ef@fACACCEPT IN PRINCIPLE. BBB  Z>> O>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1010.242E@ZRC4@Z>>|1N ` !DDq@j ?@H@s, RH@H@ober"0Roberts, Richardrroberts@xtrem ?@H@s, RH@H@ober"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum044.3.1854T@ Z~@VAC~@ FCC   Z:6i ?@H@s, RH@H@oberI@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum033.3548EReference to Bluetoothn@fAC ACCEPT. bt_11HHA*(&&bB> h ?@H@s, RH@H@oberI@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum011.2221ED@ ZAC ACCEPT. bB> .e ?@H@s, RH@H@ober@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum0000E@]|@fRCh@ 2 bB> d>@H@reggH@H@sor@P@Rasor, GreggGregg.Rasor@motorola.com561-739-2952Motorola1212.274E\@]AC~@fccV>>ݛ c>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1212.3.38443ED@fRC@G&&&  Z>> b>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1212.3.38441E`@ZAC ACCEPT. 222 Z>> a>@H@ichaH@H@l.DyI@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1212.2.1776EFigure # is missing.AC|@FfigxxxBB:.,***Z>> `>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs0000E@ZRCn@nn Z>> _>@H@ichaH@H@l.Dy@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1212.1.2.37225EN@ fRC@* Z>> !]>@`E@ichaD@D@D@I@Dydyk. MichaelMichael.Dydyk@motorola.com(480)775-7020(480)570-2841Motorola Corporate Labs1111.3671E@AC@   Z>>  1NU nLKJI0IaHGFEDCBBSA;@c"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum55.3.21318T@4Clarify Table 3XOx`* "0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec99.13549E@kXO~nnV$ ߯"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec9Figure 18 - 24E@\@kXO~nnV$ ߹"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec99.1 and 9.2E@\r@kXO~nnV$ ߹"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec99.1 and 9.23440Ev@\@kXO~nnV$ ߻"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec55.4.2.22345out of place reference Delete Van Nee [B15] lines 4-5XO~nnV$ ߷6"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec55.3.6.8183E@ ZF@fXW~nnV$ ߿"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec5Table 11040T@kXO~nnV$ ߯"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec44.1.274445Same as commment 5XO~nnV$ ߧ"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec44.1.171415E.@kXO~nnV$ ߯"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec44.1.1710E@fXO~nnV$ ߯"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec44.1.1654E@fXO~nnV$ ߯"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec44.1633E@fXO~nnV$ ߯J"0Schuster, Tomtom.schuster@intermec.com319-369-6866Intermec11.2221EIEEE 802.119Z@fXO~nnV$ ߿Shawn Liushawnliu@inprocomm.com+886-3-5165106 ext 865 InProComm, Inc.1010.242T@ Z@fXOppDݻl`?@H@ushaH@H@procI@Shawn Liushawnliu@inprocomm.com+886-3-5165106 ext 865 InProComm, Inc.055.3.6.818Er@ ZAdd the curve for 802.15.1.AC@Hfigure4..%|P>>ݻ9 ?@`E@s, R`E@rdrrober"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum044.3.2922TFrequency nullingd@!fXO!!!!Z:61 @@H@ StuH@H@H@K@0Kerry, Stuart J.stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips055.4.42828E@ @ACL@ 2"""`@>kLVALLL΄  & v " 6 $ŰdzxN?0Gutierrez, JosejosegutierMake comparis ....in AWMA is that the IEEE802.11 ..........addressed to its own..& say, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?)Be more specific as to why the bit rate doesn't matter. For example, did additional simulation results (not shown) support this?Make comparisons between the models to ensure consistency.Improve the description of modeling effort and its results.Qualify choice of experiment topology.Clearly say how these results will be used (if at all).Add sentence saying why BER=0.01 is a valid comparison point?Why describe 5.5 Mbps if it is not used in your results? Possibly omit it unless you see other value in keeping it.Both should be in line with the text.Check the value (23), or state what it means.Add 802.15.1, or adjust title, or indicate which curve is 802.15.1.Clarify the modulation description.Remove derivations of BER and use a table to show the information more concisely.Use SIR instead of SINR if noise is not used.Should be ""Master polls the Slaves""Make informative or move to an appendixMake informative or move to an appendixReplace reference citation with 802.15.1Provide a supplementary figure for table 6Change ""Basically very few packets are going through between 0.5 and 1.0 meters"" to something like ""Since very few packets are properly decoded, the access delay results are erratic due to the small sample size""If possible change legend of each figure to be more descriptive, add if it is voice or data instead of Scenario1/2/3/4Constant use of experiment, scenario or some similar wordChange ""gives"" to shows, depicts, illustrates, graphs, represents ..., something other than gives.Change table title to reflect path loss equations are for 2450 MHz.Change ""Depending on the application this may or not be tolerable"" to ""The application requirements determine if these degradations are tolerable""LVAL,B R f  d 0      \j"0Roberts, Richardrroberts@xThe expression for the random delay is in line with the text, but the random phase is set apart.Figure title says 802.15.1 is includThe expression for the random delay is in line with the text, but the random phase is set apart.Figure title says 802.15.1 is iThe expression for the random delay is in line with the text, but the random phase is set apart.Figure title says 802.15.1 is included, but The expression for the random delay is in line with the text, but the random phase is set apart.SINR range is shown to be -10 to +10, but text says -15 to +20.Spelling - should be ""differential"" and not ""differentiated""802.15.1 does not use orthogonal FSK; it uses GFSK. If this BER equation is used as an approximation, then clearly indicate that.This whole section (5.3.6) would read better if it just contained a table showing the BER formula for each modulation type. All of the derivations are not necessary. You could simply provide references to textbooks or papers where the derivation is provided.SINR should be SIR if no noise is included. Otherwise it's hard to tell by looking at a plot or result if noise is present or not.The comment on CCK coding gain probably belongs in section 5.3.3 (1st paragraph).Why not just say SIR (instead of SINR) since you don't actually include noise?Repeated paragraph. This paragraph appears identical to the last paragraph of section 4.1.1.Spelling - ""insure"" should be ""ensure"".Last sentence in this paragraph is awkward.First sentence sounds better with ""about"" removed.Typographical error - unnecessary comma after the word ""packet"".Spelling error - ""Master polling the Slaves""Typographical error - double period.Typographical error - ""IEEE 802.119""None of the sentences are complete - they are all fragmentsClause 11.3.1 should be infomative or moved to an appendixClause 11.2.2 should be informative or in an appendixWouldn't table 6 be better illustrated with a figure?1 LKK? pD@EyDD@@@?@H@, PaH@H@orda"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola0.@?@`E@, Pa`E@ul.gorda"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.1.2742E@ lRemove redundant paragraph.XOrepeatR:6߿0@?@H@, PaH@H@orda@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.1.1712EV@ lCheck word usage.RC@GZB>߿ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.1.2727EV@ lRe-word the sentence.AC|@ZB>߿"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola44.1.2725Eh@ lXO|zjjR" ߟ+@?@H@, PaH@H@orda@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.1643E\@lJ@ kRC REJECT. ZB>߿ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola044.064EH@lRemove extra period.AC ACCEPT.   ZB>߿ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola011.2221EL@lShould be 802.11 or 802.11b?AC ACCEPT. ZB>߿@?@H@, PaH@H@orda@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola011.1149-52Ev@lUse complete sentencesRC"@par_scope ZB>߿ ?@H@eng H@H@inpr@M@Kwang-Cheng Chen kc@inprocomm.com+886-3-5165106 ext 668 InProComm, Inc.1010.4.26053E@Make them consistent.AC@F%%%^>>ݿ !  ?@`E@s, RD@D@D@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum1111.3.167Et@lN@ kAC@#   Z:63} ?@H@s, RH@H@oberI@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum066.0298ECitation of Bluet99P@kAC ACCEPT. citeEE?'%##bB> | ?@H@s, RH@H@ober@"0Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016Xtremespectrum055.3.514Tj@lT@kRCREJECT. Table sufficient===bB>1N   #  @@H@ammeH@H@enshL@"0Shellhammer, Stephenshell@symbol.com(631) 738-4302Symbol Technologies, Inc.055.3.6.21548T@@"fAC ACCEPT. &&&  jB>߿1NMM=LdK GvCBAAC@."0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola99.032E*@xL@kXO|zjjR" ߻p"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.31128E^@xn@kXO|zjjR" ߿+"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola99.032E@x"Specify which PHY model is used.XO|zjjR" ߻_"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.4.42826EB@x@kXO|zjjR" ߿"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.4.325E.@xz@kXO|zjjR" ߻@?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.4.2216E@x@kAC ACCEPT. ZB>߿ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.4.1.22028E@lJ@kACv@;#ZB>߿ @?@H@, PaH@H@orda@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.4.1191Eb@xZ@kRC@79/23ZB>߿ "0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola5Figure 418E@d@kXO|zjjR" ߻@?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.3.6.8183E~@l Adjust text to match figure 4.AC ACCEPT. ZB>߿ @?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.3.6.3165E@lChange to ""differential""AC ACCEPT. ZB>߿y"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.3.6.11442E@lF@kXO|zjjR" ߿"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.3.61433E@l@ kXO|zjjR" ߿e"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.3.41350E@lZ@ kXO|zjjR" ߿0"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola55.3.51430E@lMove comment to section 5.3.3XO|zjjR" ߿T@?@rday, Paulpaul.gorda"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola055.3.21149E@lUse SIR instead of SINRXOR:6߿0K[                     .CommentStatus = "X" 'H Here is where we do all the work    H ,Ak6 B@>5 B@B B@B'All general (readable) reports completeA@@o5`]] $ $ '802.3z confirmation of comments'Message header for each email Subject:  1The 802.3z chief editor has received your inputs. 8Please contact howiej@sigcon.com if you find any errors 'WHERE Main.CommentStatus = "X" 'H Here is where we do all the work   HAo3   /This operation will modify your Main database. +It will change all status codes from X-->D. nsnSetStatus_Click()$@ |3k3 Nothing to itAo2X;Create summary email containing NEW records for each editor]]]]8]PEmail'$Summary of NEW comments, by editor ( Z)'',$$. SELECT * FROM ClauseList %&. !*a ">$ "B' WHERE Main.Clause In( ", ) AND Main.CommentStatus = "X" 'H Here is where we do all the work    H ,Ak0 B@>0 B@B B@BAll summary reports completeA@@ox0p0Attribute VB_Name = "Form_fHoundDogging"D Bas0{A0771CA8-001C-11D1-8168-444553540} |GlobalSpacAIFalse dCreatablTru PredeclaId"Expose_Templat@eDerivCustomizD$Option Comp@ DT  !Afithe or?@Z fields  Setr= CurrentDbAxAAs=.At("SELECT * FROM@WHERE Rm m]@i""" & W@;JAX1 ![n] EH#Hcb @/Her /s whwe do +#worke-Send Bs(DV2XO@.Clx db%?AkU:Elxrst_i o[8tπ&L8H",;aDyn [tac@.EOF`c T is @ty9?D!;!/c MoveLas'!n(" contains =Tt.#$CtK $a. Do yo u wisio dȁ>D in5n?"_vvbOKCancel, "6M p")-vb&7C "fNRCtaken%*&'OAz=e8N+Fio Until (!<DBNex1LoopWa.\&J#aB!`AllTo Chief'UbsaALLe9'&Mad"nASCII summaryLw(_X.tx,$RgyQmQisA  = [ ZscS Rep0ortsXZ TILDE-(imi6t|S ddyc (_0de_ "[ R2? J? *? eTildeFileV lLiRE}\oraLaxt of e7forh eaPneb8urn (ne0qhaddn"rCla0samRJ'tttdOW&&&&t)Tob#&e/&ck0n2IPORl(_de%%cB 2RcP%eGenperal222f( 2(cH(l 2KH>?![o>4O/2qJH2 ?arc~~#EWARNINGf!@yopRwi_pUpm0m[p)pck ,=d3 гmmft(" db}~mQkmvem9 nm   Bm oQaQxNew2oQ oQ toQ0oQÛoQ!ocŲxw w8wS 9wS%iQ} = vbCancel) Then Exit Sub Call snSummaryReports_Click 'Make readable ASCII detail $fi"(_.txt) If (MsgBox("Rjy to mC4s?",OK, "cmdNewToEditory") _ GeneralTILDE-delimitedbatabasec (_tildecEbCteTCFconfirmations for comm$en (emŠa̐endC(.Set s tatus+des: X --> Ds fD++tS%GEndC PriPvate S-6EW (@YDim rst As Record- AdbD A@= CurrkDbA= db.OpenF("dispatchdb8DynA؀o UnA.EOFCDoCmd.)Object acNo, , FoGTXT,i![B]aMessage@a  !["zdy`False .MoveNext Loop8Clo$ c ("M!s "@(See if user wantsK[                     clear the ! ul•1C!D$Ta8Prepare!(arfgb"rgH erB!Bod>yd= 8@=:?strCRsciiCRaAString "Chr(13) + "&0b!D' D$anX av'r"N exists#L / oISELECT * FROM e& "E& "W`HERE "@""h%AND KE*Full= "J,`a]'No; we wihaveF" on E!сQdޡVAd!fX߅`eh]_iݠccH *-" %< mj >f- 0&@E@D !N %oAUpd` EqaLen(`uKK ) < 20G`v'We c&safely add&+ !N Gdi`?$zDc$@ gew1.$   muY`kD$3as (9^pirR nevwS#. Tru% b%4&l[WW&vuX&-&&=[B @Ifא'tp.^ t`  h$WTypergDest%, j@ceXtoDQ'aA Output◰c"c1]n@xth /tTransff-~o{P QZo|_hQb1, 234R h=`c bSbb'Che,ck9e o~fQS Q""q'BpalqA`A> "X0'w6{¾"J"s."!* C("Do youshverwrUQ!ɾ7L'Ohrwi kA`o ffJmembert6K !)Y,$% _'Q*u)"1Rӟ))nt{pa7|r| "k}/Vu@&1!50jORDER BY  "J  \ " {s.A>aOIr (("@oy$ou1sh"rverwrite?", vbOKCal, "bCK=c) _#f` Exit I'Oth iW\kih f Ming memberDKiMA%feIK( O AR`H i ?S SVL= CurrentDb(@<q/? qa S(f""SELECT * FROMc_"(&&si"ORDE0R BY ~ause,,clPDLineAg3" ";@!K DfbjeXct:I j2@>R 6ricted+r=!TYer&;Sߵ,Sߵgx:Q߲ղ3 opp4f8rO`eXDQ'sgflags X-->Dӣ 0 Mψce ;m= X)}.))/& "WHERE%""X" ,*DdbQDyntP&'Upda`ߕ05&D/ 'Q8Edi ![5]~DPyDispatchцq%O]Q"gVշ_"e:"ub#Tilde%?;-7@}kZ'Grab0cacq3+Gransfer records to the table MainOutput, applying cUnScruball memo fiel@ds 'TTextln onle Dim rstn,Aw As Ret(dbDa as<tCheck for existence of argDes6If (p1 File() <> "") T@hen MsgBox ("f " &#"/s."),o you wishroverwrite?", vbOKCaKl, "cSendSumma4ry?= ) _+ J Exit Sub End If vGrabacˀ܀lconditionSet = Curr@entDb(['Select ~Pg =.Opend(,"SELECT * FROMŽ@O4WRCF(H;"ORD ER BY.Clause,A"cPagLi$neO";i CAh/.EOF{' NoF@@NprocesL"E odbIe[?,KC B-A{cl0ear pries inBD o Until ^(J: DtWM`VNw Loopz)&!Enew#߃ÃDKAddNewD@![Comm"ID]`RderName$Email3C_PhonǔC_FaxsCopCVwy|jAHTyp0 EEp&Q]/XSuggedRemedy Resp!R(ForceXtoD5True) A g Status "X")s0!::xD"ElV>(r E[/ҋ![TopicV CreateЅ ''gLaodyDispatch~Wp`yK[                     Accept_Re>j`.Clxd_Unsatisfe]AVoter[yj#.UpdۓS'asn1Uzs).vv b s~ՇxVx1aoCm d.|2acExportimW th Tildes"СA, AB񨧑?ֳ@b-delimintedmat complete(̶)bPriv! cmdUnlockDangerousButt0P_ClickpMms![fHoundDoDgg]![C /T].En qd0PNot ongohk!QOJqG / _(}QI`Pb&pChief getQseeb; eors don'tcGetOwnc();r!(:cAllToEiS'IseRe,s'Ge al.]b.ROEOO,New5>n:>X >n;>|snը? D End If 'Alwa ys be with these dangerouutton s dis T`!?Make re;us` didn' t hitC>ancel key If (2"@.The7 Msg ("A valid is@quired. U`OK+accept default"dExG`6p$ChePs ee if existsp4aAGE) <> ("WarnR: a _=e`=D . Ove@rwrite"?g)avbOKC$, ,E1))vbC) 7qoKip9D 3UJJHe0wh5w`Jo<0K w@ork C=c?1?$<3<, ;A {F` F Ҍ-del im" contpQ@ H2 G GGngG GF"!> MG>MGt'/G/G!Gde@lseV/G/G/GQ[ /GU/G/Gt(/Gnt-GD2 `<Gc4$G*GG cGGxGAGGGE46 GleGGJ GgGtkGG GsPGB~ =`GGGEuGGKG?7Z;oFsoFoF seoFoFit!woFsaFeach eorC06Q sStWrst%!R3etdbsAqjbaQPPrefix9<')hat a t@lect haeen0 madp'Is@Null([m.sLpt])h|se!XQ aq4'$e!#SubjPF"#DoOC, by K`OMȑpb`y'= MMt?&4~"c:\CT\r`s\`1mure the user didn't hitcancel key If (FilePrefix = "") Then MsgBox ("A fJname pTis required. It should includdctory path<. Use OK to accept default")qExSub End If S e&bCurrentDb(-rstdb.OpenRecordset("SELECT * FROM ClaLis2 Do Until (a.EOF=Not cIsBlank!Edi a)argDe>& "to_" & cReplaceAllA", " "_ _Ade.txt"~,'Checksee Dif ex^sUpData>(F) <> A s("War@ning:  +E3%. OverwriteB :?-_vbHOKC, S"seCreate TildeAs_ ClickA= vbCMXElse#Kill D2 E @Con@{ions@"WHERE@ Main.C In(w@!ǔ=#7AND|& [Forms]![fHoundDogg`TypjeA] $'LHewhw8e d̀8wo$rkF Ca@cSendX,!@i&jg, cepXtoD_ "AbMoveNext# Loop !Clo!/ n$'!;ports completeA{yz PrivA  seGeneralf7C{'cFtaa`d em n+X r~ for each e 8or|im?+u-" As Str 2 gAdbnba D Ydlf,Boolea {hat a t?` lectN has been mad\vIsNuHJ2&P@seA fromb" %o!e!'AskB+ =bput(" $A3NEWBC:!@G"c:\mydocs\I'Make s`Xb`.2+` U De`s of^`km,sd`i, byD_ b`*e"H`(= FaSOuOuOuOu%$2Ou"1,OuB:OuOux@ t!ytfdablttetptt11Q S#t ҁtt%ut"sc2tVtt@t@!b fiWuuWu:) uuuruuu1u9duup.uuul gsr@ea.)Tvd `C[vSummaryvvsvvvKpStv`D@uvmv"xorÌ'vvonv (vN]vҏvvvA!C^Ea__o _4_(___J5S= @RDQϹϹϹ 0ϹϹ!"1N OEOEcGEOE!So3s rst.Clos e dbMsgBox ("All summary reports complete") End SubPrivate snCreTildeFiles_Click*(h'4 6-delimited f&]ntaining NEWtcords for each editor Dim argType,DestjCon+ions As StrS7$Re[et db Databa0K[                     \Prefix !ForceXtoD BooleanISubj = "Ded`ls ofements, byc (" & 9e")" + = Tru 0'Askname pIO= Inputۈ("PFse 6eMB: isquired. It should inclTuddc@y path. UAOK to accept defaultA/AEx@)@kCIfoSe boCurrr@PDbAA=B OpenƎ("SELECT * FROM ClaALisB@o Until (.EOFCNot cIs Blank!E)IE %O@& "to_caklaceH,d "w"_Y _ de.txt@'Check$see ifCptexsBAp b() <>| "` 8a9("Waray: a.  C . Overwr"?gNe vbOKCBJV,"sc3@= vb-,sB ElAKi $'% !IaWHERE M@Hy{bF!GJEu HAND$omS tatusE""X"`@Z'He`uiwhwe d`c wwork FCacSend>5, [ !_MoveNex`a Loop ! G?a w kGeneralkx'$d"@ema@scofta>E|L#MѿhhQQQQQ QeQrQrgQ0!66 bIn6t6D66t0.660 6t+6o7o7e77g3jeadable)70>QCMfirmXV 2Her ]strCR0sciiCR.Chr(13) + 0 /802.3zaaa Ř`2'Message< h q4  5 ectpsP2e& S a4q hief uhaceiva@HyourЛs~.|rdJct howiej@sig . O|0t@anPrrors6`0 ggdd,,g,s,OrgW$yğGmģ%Thm,op_wymo`dify Qu zdd.Po bcXhan A`s=coderom X-->D.? !et ߨ h0is54XD!op  ؕ^ppJV<Z!ן'@1 Q:p"0pppppo?p0=pE(?use In(" & rst!ClaList _ & ") AND Main.CommentStatus = ""X" " " j'Here is whwe do all the PworkRCcSendSummary(argT ype, DestSubjConditions, Forc@eXtoD)NE`nd If.MoveNext LoopClose db. MsgBox ("ATsF reports complete"52H% the Type ListA@@|>k>Email',Summary of all comments to date, by editor ( Z)'',$$. SELECT * FROM ( DxME PSLS S converted to \13 \10,  converted to ~, and -Status and Clause fields forced to upper caseA@@o@0The Chief gets to see all buttons; editors don't$<$D d"L"V(X d"L"Z(Xd d"L"V(X d"L"Z(XkPoH]]$$.^#Select all records with CommentID=0.this query isolates new comments (CommentID=0)  *SELECT Rough.CommentID, Rough.CreateDate, Rough.LastModDate FROM Rough WHERE (((Rough.CommentID)=0)); ^%&.:The index table holds a single record, with a single field5this field holds the next assignable CommentID numberIndex ^%&.`SSave existing value of NextCommentID in case we have to back out these transactions `B@. `"d `)b `B@< !*aAdd coment ID to curent record B@. Z ) Z ) `"d )~ B@<Advance to next record B@>Advance the CommentID index `B@. `"d `)d `B@< B@B `B@B ^B@B'All ID's assigned in Rough import tableA@@oX8hH]x]]]]]]](fRough'NIsNull(ResponseStatus) OR ResponseStatus Not In ("O", "W", "S", "C", "U", "Z")'jBIsNull(CommentStatus) OR CommentStatus Not In ("X",K[                      "D", "A", "R")'l:IsNull(CommentType) OR CommentType Not In ("T", "E", "TR")'n   j OR  l OR  n OR  p'r$$.  r$SELECT * FROM Main ; %&. !*  r BB@HThese records contain bad status codes, comment types, or clause numbersA@@d@No Bad RecordsA@@kdSELECT * FROM Rough WHERE r; %&. !*  r BB@HThese records contain bad status codes, comment types, or clause numbersA@@dHNo Bad RecordsA@@k k B@B B@Bt|h !A@@toH]]]z$$. Index ( %&. !* B@|k@ B@. "d'x&Last saved value of NextCommentID was "b.. Please enter a new value for NextCommentID: Modify Index Table x$j )d x )b B@< B@B B@B|@|8z0 B@B B@BNo change to NextCommentIDA@@|o!Check for existence of input file d"L"N$lNew input datafile not found.A@@|PkH$Proceed to read from input datafile?$@G|jelseA@Proceed to assign ID numbers?$@G|jelseA@\Proceed to set date stamps?$@G|jelseA@!Proceed to check for bad records?$@G|jelseA@fRough import process completeA@@o ]`]$$.^Rough ^%&..this query opens the entire Rough import table  !*aC@.LFirst preserve dates and voter status codes from main table where they exist A@C@<C@..Now fix up dates according to new status codes A@C@<Advance to next recordC@>q B@B ^B@B)All date stamps set in Rough import tableA@@o]]]]83Proceed to transfer records to main database table?$@G|j$$. .this query opens the entire Rough import tableRough ( %&. !*bGFind record in Main with CommentID that matches current record in Rough  -SELECT * FROM Main WHERE (Main![CommentID] = "~ );'  ( %&. !*1If matching record was found, delete it from Main B@. B@zk "Transfer record from Rough to Main B@| "~ )~ " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) " ) B@< B@BMove to next record in Rough B@z B@>X B@B B@B"All records merged into Main tableA@@o X]]]$$. oPartial query used to find record in Main with correct CommentID (we'll fill in the ID part of the query later) :SELECT Main.CommentID, Main.CreateDate, Main.LastModDate, ?Main.DispatchDate, Main.WrittenDate, Main.[Accept_RejectDate], MMain.[Closed_UnsatisfDate], Main.VoterStatus FROM Main WHERE Main.CommentID = "~;'  %&.*If there is a corK[                     responding record in Main !*-AND if the dates are not filled out in Rough,.then transcribe over the dates from main table5NOTE -- EDMAIL sends us NULL dates, but the automaticEdatabase import I am planning for the next version will preserve them "$G " )j "$G " )j "$G " )j "$G " )j "$G " )j "$G " )jNow fix up voter status codes "$b "$b -Both fields are blank; try the voter database  Ad` $Preserve the value in the Main table " )kk B@Bki0]p]$$. Rough ( %&. !*a B@z B@>p B@B B@BRough Import Table is ClearedA@@o!Check for existence of input file d"L"N$lNew input datafile not found.A@@|k PRough import with tildes1Rough d"L"N BB@!A function in the module "common"A@ 'Leading white space has been stripped,  converted to \13 \10,  converted to ~, and -Status and Clause fields forced to upper caseA@@o@]0]P$$.  d"L"ZUpdate Records with no status3SELECT * FROM Main WHERE IsNull(Main.VoterStatus) ; ( %&. d"L"ZUpdate all recordseSELECT * FROM Main ; ( %&.d0%Please select which records to updateA@@ B@B|k !* B@.  A B@< B@> B@B B@BVoter status update completeA@@o0p] ;SELECT * FROM VoterNames WHERE VoterNames.CommenterName = " ""; ( %&. !*:commenter name not found in VoterNames table; add the name B@| " )Echeck to see if the same name already exists in the VoterStatus table    9SELECT * FROM VoterStatus WHERE VoterStatus.VoterName = " ""; ( %&. !* Bfound the name in the VoterStatus table; fill out the voterstatus " ) " " )k B@< B@Bd0found the commenter name in the VoterNames table !$b Uassuming the votername field is non-blank, look up the voter in the VoterStatus table 9SELECT * FROM VoterStatus WHERE VoterStatus.VoterName = " ""; ( %&. !*gcmdUpdateVoterStatus() name in VoterName column of VoterNames table does not exist in VoterStatus tableA@@ B@B B@B B@B B@B|k Bfound the name in the VoterStatus table; fill out the voterstatus " " ) B@Bk0k( B@Bo(!Check for existence of input file d"L"N$lNew input datafile not found.A@@|koxp 3IsNull(Clause) OR Clause Not In ("00", "01", "02", "03", "04", "05", *"06", "07", "08", "09", "10", "11", "12",  "A", "B")'p%Attribute VB_Name = "Form_fInput" Bas0{033FE3A9-FEEC-11D0-8168-444553(540} |GlobalSpacFalse dCreatablTru Pre declaId"Expose_TemplateDerivCustomizD$Option Comp@ D3T  >ݿ @?@g-Chang Maa ycmaa@inYeong-Chang Maa ycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.05TR@ xt@kXW*@ #|T66ݸ9"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola1212.069E@xXO~zjjR" ߛ@?@H@, PaH@H@ordaI@"0Gorday, Paulpaul.gorday@motorola.com954-723-4047Motorola099.032E@xv@kAC @aZB>߻ LVALllD H * @            Not sure if this method can be used within the current Bluetooth specifications since it requires the definition of a new packet format.Simulation results are given in clause 10.4.2 for the notch filtering technique, but none are given for AWMA and PTA.Both AWMA and PTA consist of a TDMA technique that alternates the transmission between 802.15.1 and 802.11. AWMA uses a fixed partition while PTA is a finer grain possibly more dynamic partition. IT is Not sure if this method can be used within the current Bluetooth specifications sinceNot sure if this method can be used within the current Bluetooth specifications sinceNot sure if this method can be used within the current Bluetooth specifications since it requires the definition of a new packet format.Simulation results are given in clause 10.4.2 for the notch filtering technique, but none are given for AWMA and PTA.the WLAN model available from the OPNET library was extended to include the PHY and channel models.refers to Bluetooth as opposed to 802.15.1It is stated that the results from the analysis and simulation are not compared due to different definition of SIRLines 12-15 and 42-46 are redundant. In addition, the statement is inacurate since the ARQ mechanism does not cause the throughput decrease as implied.The statement is inaccurate since IEEE 802.15.1 does not always operate at 1600 hops/s.This comment is redundant. It has been already stated on page 2 Clause 1.1 Scope.Two periods at the end of the sentenceThe definition of coexistence seems to (partly) overlap with interoperability. Do we want to strictly divide between the two?What if ACK or NACK is not receivedGrayscales chosen for EV3, HV3 and HV1 do not read well.There is no clear specification on the used bits of CLK. The use of CLK should have a clear specification on the used bits. For example, CLK[27:1]Table 5 is not needed since we did not simulate the 11b self interference. LVALj$$$$ ͎   :RjIt should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types of transmitters should be splitted, and the table of content should be modified according to the above frequency offset definition.In my opinion, the discussion for the two schemes can be made more seamless with examples aIt should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types oIt should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types of transmitters should be splitted, and the table of content should be modified according to the above frequency offset definition.In my opinion, the discussion for the two schemes can be made more seamless with examples and usage scenarios where one solution is preferable over the other.consistent spelling of ""colocation"", ""colocated"", etc.refer to the 802.15.It should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types of transmitters should be splitted, and the table of content should be modified according to the above frequency offset deIt should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types of transmitters should be splitted, and the table of content should be modified according to the above frequency offset definition.In my opinion, the discussion for the two schemes can be made more seamless with examples and usage scenarios where one solution is preferable over the other.consistent spelling of ""colocation"", ""colocated"", etc.refer to the 802.15.1 specificationsneeds to be replaced with ""increased""State clearly whether interoperability is included in coexistence or not.Add ""If an ACK or NACK is not received the channel is deemed bad"" or something like thatChange graph lines to black with markersSpecify the bits of CLK to be used.v1|qf[PE:/$ti^SH=2' w l a V K @ 5 *   z o d Y N C 8 - "   } r g \ Q F ; 0 %    u j _ T I > 3 (    x m b W L A 6 +  {peZOD9.# ~sh]RG<1&vk`UJ?4)yncXMB7,!                     }}}} } } } } }}}}}}}}}}yyyy y y y y yyyyyyyyyyoo o o o o oooooooooomm m m m m mmmmmmm~m}m|m{iziyix iw iv iu it isiriqipioinimilikij hi hh hg hf hehdhchbhah`h_h^h]h\ g[ gZ gY gX gWgVgUgTgSgRgQgPgOgN[M [L [K [J [I [H[G[F[E[D[C[B[A[@[? W> W= W< W; W:W9W8W7W6W5W4W3W2W1U0 U/ U. U- U, U+U*U)U(U'U&U%U$U# @@I@ StuI@I@tuarI@0Kerry, Stuart J.stuart.kerry@philips.com+1 (408) 474-7356+1 (408) 348-3171Philips09Table 103311Ed@R@ACACCEPT IN PRINCIPLE. scen_expJJ@ `@> 1N MKLKJIHH!GHFkEDCBAA7@"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self33.2435E"@@ XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self33.1.6329E@ z@ XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self33.1.4323E@ @ XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self33.035E@ @ XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self11.2221E@@XObD" I"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self11.1247E|@@XObD" O"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self11.1245TJ@@XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self00031E@@XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self11.014354E@F@XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self11.014041E>@@XObD" ;"0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000154Er@Please delete page iv.XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000154E`@p@XObD" "0Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self00010E @@XObD" "0Golmie, Nadanada.golmie@nist.gov(301) 975-4190NIST1111.2T@z@XO|zzzrnffJ" ߹"0Golmie, Nadanada.golmie@nist.gov(301) 975-4190NIST1010.3, 10.2T@z@XOrnffJ" ߹"0Golmie, Nadanada.golmie@nist.gov(301) 975-4190NIST100040T@<@ {XO|zzvrnffJ" ߻?@H@, NaH@H@olmiI@"0Golmie, Nadanada.golmie@nist.gov(301) 975-4190NIST1010.04042E@$t@ {ACP@>#1l2lsZB>߿ ?@D@, NaD@da.golmi"0Golmie, Nadanada.golmie@nist.gov(301) 975-4190NIST066.0295T@ zn@fXWzR:6߿01@@@I@ LeeI@I@adcoK@Hans van Leeuwenhvl@adcon.com+31 20 420420031 628 960 146Adcon055.4.42830,31E@ Z@ ACACCEPT IN PRINCIPLE. x^>>9LVAL~ N2p Jln""can lead to increase in packet collisions""""interference of an IEEE 802.11 WLAN""Replace the subclause by parameters needed for the current partition sequence sturcture.Take the alternative to take the least-numbered channels. Or at least make LMP command field properly defined.Please adjust column 1 based on the entry ""CSMA/CAcarrier sense multiple access with collision avoidance""Please add to Bibliography. Please make the change globally.Please correct the spelling of ""colocation"" to ""collocation"".Please correct the spelling of ""sub clause"" to ""subclause"". Please make the change globally.Change sentence to read ""...of an IEEE 802.11 WLAN and IEEE..."". Do youPlease make the Mb/s change globally. Also, the symbol for kilobit per second is kb/s, not kbps.Delete the period in the title sentence from ""...Unlicensed Frequency Bands."" to ""...Unlicensed Frequency Bands"" on page i and page 1 too.Change reference from ""IEEE Std P802.15.1-2001"" to ""IEEE Std P802.15.1-2002"" and be careful when you use ""802.15"" and you really meant to use ""802.15.1"". The point is try to avoid referencing the WG when you mean to refer to the IEEE 802.15.1-2002. Please make the change globally.Replace with ""...Wireless Personal Area Networks (WPAN(TM))"" or drop the TM usage when it is spelled out. Please make the change globally.Add introductory material to Front Matter before recirc.Change ""standard"" to ""recommended practice"" on line 10 and throughout D5. Remember that there are three (3) types of IEEE Standards Documents: Standard mandatory (shall) Recommended Practice suggested procedures (should) Guide guidelines (may) The point is you need to liberally use the verb ""should"" in a Recommended Practice.Harmonize with the method adopted by