Standard Jet DBnb` Ugr@?~1y0̝cßFNj7՜]('`{6n߱eCT>3y[ $|*J|C1 f_Љ$g'DeFx -bT4.0R@'RN%%`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 Co@@K @-=$3\2HwG7@ Y\0S xx 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    daOY& Settings\alSwY 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 CdX1bN   : k & W  C `  L}# $ % & ' ( ) , - . / 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@ '!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-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`JYby+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+iqdmQikmJmokJf^^YQO+QOYmkyM+kM+fU+^byM^JokQ^YkmM^dkQQJbOmMd``QbmkMd``QbmQiSo^^++OYkfJmMWYbOQu`JYby`JYbdomfom `JmMW:y`kvkJMMQkkdL[QMmk!`kvkJMQk`kvkY`QuMd^o`bk"`kvkY`QukfQMk#`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkidoUW$miMd``QbmQi%mvfQ^Ykm&qdmQibJ`Qk'qdmQikmJmok(JMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQOokQiOQSYbQO_`Dabch(box_suggested_remedye5_` abchbox_responsee25]a$'bH!c ̙ Box173e25_a@b !c Box172e25_ab !c Box66f3_5`<a$b Line105f3_5`<ab Line106f3_5`<ab Line107m7W`a<btefk&CommentIDCommentIDd25]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%FyGyHyIy!yD" !_#c$h&l'p(KLMNPQRSTUVWXYZ[\]^_`cdefghijmnruvwxyz{|}~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@FAFBGCGDGEH|AH|BH|CHFIMINIO|/|0|1|2|&|'|(|3|4|5|6|7|8| ||||||||!4!5!6D|)D|*D|+|| |!|"|#|$|%_|,_|-_|.c|9c|:c|;h|?h|@hlllppptttt tt tttt!t"t#t#t#t#Y0š]                        \    ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D E F G H I J K L  @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ 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 DDDDD D DD DFpFFFF F F F F FqGG8G9G:G ;G <G =G >GH?HAHBH@IWIIIIIIIIIIII I I I I I I I I I IXp<''' , pp ,>,F p6  O, tx$,p  DirData                          ! " # $ % & ' ( ) * + 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 { | } ~  ]  _ Page " & [Page] & " 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^ ion196d |Label197kwoption_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\@MSysRelationshipslI@:::......., @ g\@ g\@Relationshipsl<<<<<<<<<<<:  g\@ g\@Databasesl<44444444442  g\@ g\@Tablesl<.........., 8LU L A h dJ I ImiHGlhFjD;;{pA=EE @s\@: 3T@AccessLayoutm>4MR2KeepLocal Tjqzz:::::::8 @p~Nh@zDJT|@VoterStatusm>@DDD88888886 @l@Eh@'0Np@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@ 8@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>t @94MR2KeepLocal Tl``````^ `1ݨ @ݨ @~sq_cfFinalReports~sq_cClauseListm>k@+4MR2KeepLocal Tpddddddb `0 ۏe@Ҋ#f@_GetAllCommentsm>@w@zXLL@@@@@@@> @/ oc`@ Je@Adminm>R@z8,,,,,,,,,* .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@ C@mPmi@t eEr BAVTZP_THMGYWDNAOWKEINOKJKHI28A@VTZP_HMGYW_NO@KbINOhKJHgADH@1^B,<"B(B+BxForm_fMainGEA6r3_f@ a 5n0GRVBZIDXNOFUZDSYCZPKJWZAFNYB(((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 mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmO 1 e 0 ɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼɼctDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeIiimmmiCmEmYYIdParentIdName         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 G G Main.CoG Main.Comment+ 'GG Main.Comment+ G Main.Comment+ 'GG G GGSt GSt GSt GGSt GSt GSt 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 claLVALC` > T 0   HR ACCEPT IN PRINCACCEPT IN PRINCIPLE. REJECT. SiACCEPT IN PRINCIPLE. If copyright permiACCEPT. In annex If model FH ACCEPT IN PRINCIPLE. In an Annex, just find itACCEPT IN PRINCIPLE. If copyright permission is not obtained, all of these definitions will be deleted.ACCEPT. Will remove editor's note.REJECT. A change in the title is not editorial. It requires a change to the PAR.ACCEPT IN PRINCIPLE. Will either add curve or correct title be removing 802.15.1REJECT. Since these two discussions are in two separate clauses, there is an advantage of having them be self-contained.ACCEPT IN PRINCIPLE. ... due to timer expires ... ==> " ... due to timer expiration ..."ACCEPT IN PRINCIPLE. They are defined in P78L15. Will confer with technical editor to add definition in clause 3.3. Td TsREJECT. Cannot understand your comments. It does make sense using RSSI to judge whether the error is due to interference.ACCEPT IN PRINCIPLE. First word will be capitalized as per IEEE 802 style manual guidelines (9/2001)REJECT. Do not see any problemACCEPT. Figure 43 will be redrawn in black and white only and using the same package as the other figures for consistency.ACCEPT IN PRINCIPLE. Figures will be enlarged to fit the width of the figure box, which is fixed with the margins.ACCEPT. Figure will be redrawn.ACCEPT IN PRINCIPLE. Will correct title by removing 802.15.1ACCEPT IN PRINCIPLE. Change to 802.11bREJECT. 802.15.1 could be in park or holdACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eACCEPT. Will align TBTT to lineREJECT. 802.11g is not covered by this recommended practice.REJECT. 0.5 m was chosen based on transission between near and far field.REJECT. A value of 1/n is not valid for all applications.ACCEPT. Will remove the editor's note.REJECT. Note that the PAR for TG2 states that we can modify 802.15 standards.[!                                                                                                                                                   ,,,,,,,, , , , , , , ,/////:::::::: : : < <!<"<#<$<%<&<'<(< )< *< +< ,< -@.@/@0@1@2@3@4@5@6@ 7@ 8@ 9@ :@ ;@<@=H>H?H@HAHBHCHDHEHFH GH HH IH JH KHLHMLNLOLPLQLRLSLTLULVL WL XL YL ZL [L\L]R^R_R`RaRbRcRdReRfR gR hR iR jR kRlRmUnUoUpUqUrUsUtUuUvU wU xU yU zU {U|W}W~WWWWWWWW W W W W [[[[[[[[[[ [ [ [ [ [[]]]]]]]]]] ] ] ] ]]bbbbbbbbbb b b b b bbffffffffff f f f f fffllllllllll l l l l llllxxxxxxxx x x x x xzzzzzzzzzz z z z z zzzz                !"#$% & ' ( ) *+,-./012345 6 7 8 9 :;<=>?@ABC D E F G HIJKLMNOPQRST U V W X YZ[\]^_`abcd e f g hijklmnopq r s t u vwxyz{|}~                                                           !"#$%& ' ( ) *+,-./012 3 4 5 6789:;<=> ? @ A BCDEFGHIJ K     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  _YKderByON##KKY 4 Y q Y Z Y s Y   Y B Y nd Y i Y  nd Y id Y t Y u Y l Y d Y n Y  Y [dY Y  Y Y Y $Y , Y ldCommentIDCommenterNameCommenterEmailCommenterPhoneCommenterFaxCommenterCo ClauseSubclausePageLineCommentTypeCommentSuggestedRemedyResponseCommentStatusResponseStatus TopicCreateDateLastModDateDispatchDateWrittenDate"Accept_RejectDate&Closed_UnsatisfDateVoterStatus #meYCommentID ## ### #mentID ## ### #u%e70-8341+1-954-557-7187Motorola9.1TI don't understand the explanation for the delay spike. Does this imply that the simulated time period was too short (i.e., too few packets being received for good statistical inference)? Improve the explanation in the text.TE-??XO@ 1$@C93548b`^]QEDC>\[XPA2 ,0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola6.0ECitation error.Fix the Bluet{99} citation error.TE-Agree Will remove the end of the sentenceXOCitation error.!@C6298ֻk\[XPA2  84F0F; `O0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation2TSection 10.2 needs some work. ; *`O0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation10.2TSection 10.2 needs some work. The T1 and one of the TWLAN/TWPAN need to be communicated. The other duraction can be calculated from TB. This document should include changes to 802.11 in the form of editing instructions to a particular revision of 802.1Signal T1 and TWLAN. Add ""editing instructions"" to this document for any required changes to 802.11.TE-??XO+@Gf@ C1042qrqmYI: : )`O0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation10.1TLast para of 10.1 doesn't mention that PTA should also be used when SCO needs to be supported.Add "" or when SCO links need to be supported."" to the end of this para.TE-??XO^@DI@ C1041<<:8, rqmYI: 9`O0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian CorporationFigures 9-15EThese figures are too small.Make them bigger.TE-??XOThese figures are too small.Make them bigger.525֮zymYI: 8 `O0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation5.3.2EFigure 3 looks really naf.I'll give you a wmf from my original drawing.TE-??XOFigure 3 looks really naf.-@C51223-49srmYI: c"5 I0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola12.1.2.4Eextra comma.Delete comma.TE-AgreeXO extra comma. Delete comma.127322zma`XPA2 4 G0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola12.1.1.1E""vendor specific"" is not what is intended, I think.suggest ""implementation specific.""TE-??XO5@1$@C127117a`XPA2 T 'N , * **̕ ˻ ~1y0̝cǟFN7]D^(`T{6߱wCϯ34ay[|*|OJl>`&_Љ$g'DeFx -{N            FlagsFormModuleNameReplicationVersionTypeTypeInfoVersion06Index1000TypeSpecIDSpecNameSpecTypeStartRow TextDelim TimeDelim@@ 6*D4"@ @@ 6*D4" @ !!@ !!"@I:n)L  &HJIԺn)RN F  !` bHNP  U??1(DRfb!b bHNP  U??1LVALMR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:     MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:     MR2OrderByOnColumnWidthColumnOrderColumnHiddenRequiredAllowZeroLengthDisplayControl FilterOrderByValidationRuleValidationTextOrientationDescription FormatCaptionInputMaskDefaultValue$UnicodeCompression   l CommenterName      m n"CommenterEmail      m n"CommenterPhone      m jCommenterFax      m hCommenterCo      m dSubclause      m hCommentType      m l CommentStatus      m n"ResponseStatus      m VComment D4     f$SuggestedRemedy      ^ Clause      m ZPage      m ZLine      m XResponse      \ Topic    MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:  MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:     MR2RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnOrientation:     @ "08","09","10","11","12"David Cypherdavid.cypher@nist.govU>0  LVALdF P l x  ˈ " 6.ULwܐdHULwܐH"frequency nulling" has not yet been defi"frequency nulling" has not yet been defined; since t"frequency nulling" has not yet been defined; since this term usually refe"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 b"frequency nulling" has not yet been defined; since this term usuall"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 withouNone and Receive seems to have been switched in the last two columns of the last row.QPSK: Change "phase shift" to be "phase-shift"Typo: c7 should be -e^(j phi1+phi2). (c = [c1 c2 ... c8])typo: ""... IEEE 802.119 WLAN and ...""It is said that some bad channels should be kept in the hopping sequence. Why should the device do it?Why does the CCK system model have a GFSK mode?Why does the 802.11b system model have a GFSK mode?...average the schedualing policy yields to a delay increase.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. "00","01","02","03","04","05","06","07"David Cypherdavid.cypher@nist.govdM?LVALϢPp>`D'( k(  ?` ( P  g   & N v     N    8 `     8            ! & N v     N  d  d  d         )ClauseList.ClauseListClauseList!ClauseList.EditorClauseList.EmailClauseList.OwnerClauseList.Chief'ClauseList.NoWritten%ClauseList.NoActionClauseList.NoSig'ClauseList.TRproblemClauseList.Done    (   X ݨ @   X + @& @JN @ v @  @  @  @  @ N @    @  H X y8@A~sq_cfFinalReports~sq_cClauseList          8   `         (   0   8 8    8 `     8  @  @ & @,N @@v @*   @  @, @D @N @ ClauseList      &   N   v   (   0   8   @  N H    8 `     8     X 8 `    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  P  P  P  P  x 8  0L H  0L H  0L H  K H  K H  K H  K H  K H  K H  K H   z H  `   P X  h  x   0  h         d  dP  d   0 h    P(       ( 0 8  P    0 h    H ClauseListh  v h P   q                               P     ClauseListK  h  h K      H !ONMLGK6J2JHGFEDC*A3@a0Seals, Michaelmseals@intersil.com321-724-7172Intersil55.4.2.12152EB@ )@.TE-AgreeXO TE-AgreetrbbJ$0Seals, Michaelmseals@intersil.com321-724-7172Intersil55.4.1191EWhy is there (23)?!Remove this or add explanation.TE-Do Not Accept, This is from Bluetooth to reflect that there are two differenct frequency hopping sets due to regulations 79 or 23. See 802.15.1 for further detailsXON@1%#!~trbbJ$0Seals, Michaelmseals@intersil.com321-724-7172Intersil5Figure 41828EF@ )Add the 802.15.1 curve.TE-??XOTE-??trbbJ$0Seals, Michaelmseals@intersil.com321-724-7172Intersil53.6.31620E\@)Remove the word ""required"".TE-??XOTE-??~trbbJ$0Seals, Michaelmseals@intersil.com321-724-7172Intersil55.3.6.21544E"Missing parentheses in equation.Add parentheses.TE-??XOTE-??trbbJ$0Seals, Michaelmseals@intersil.com321-724-7172Intersil55.3.6.21539EJ@) Replace.TE-??XOTE-??trbbJ$;@D@MichD@D@D@ 0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.5143EN@)Remove the em-dash.TE-AgreeAC ACCEPT.~X<:M;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.3.3139E^@)Remove the em-dashes.TE-AgreeAC ACCEPT.~X<:=#0Seals, Michaelmseals@intersil.com321-724-7172Intersil44.1623E!Remove this one line paragraph. Remove it.TE-??XOTE-??|ztrbbJ$;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil044.064ED@)Remove one of themTE-AgreeAC ACCEPT.   ~X<: 0Seals, Michaelmseals@intersil.com321-724-7172Intersil33.3549ED@)"Replace with 802.15.1 hop kernelTE-??XOTE-??|ztrbbJ$;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil033.1.3321ET@) Add it.TE-AgreeAC ACCEPT.~X<:-;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil011.2221E802.119 WLAN 802.11 WLANTE-AgreeAC ACCEPT.~X<:m 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 bLVAL'Z~  ̈́ " r   F J`        say, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standardsay, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?say, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?)Improve the explanation in the text.Fix say, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?)Improve the explanation in say, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?)Improve the explanation in the text.Fix the Bluet{99} citation erroLine 3 - should read 'case, increasing' Line 8 - should read 'to less than 1...'replace with differential Replace with 'much more likely than'possible correction:""but also the adjecent channels, the 22 channels that are susceptible could be increased to 24 channels"".There is a potential packet collision between a WLAN packet and an 802.15.1 packet when the WPAN hops into the WLAN passband.Correct introductory text, or remove PCF behaviour in PTA.Include a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.Analysis and simulation material addressing 802.15 and 802.11G coexistance needs to be included.e.g. change to ""can support up to three non-overlapping channels in the 2.4 GHz IMS band.""Change to "" Wireless Personal Communication""Change to "" discusses the physical layer""Change to "following subclauses "Insert a space character and question mark: "" 802.15.1 activity have greater priority than the requested 802.11b packet?""Add space character "" transmit activity. The decision ... "xxx -> 53(?) move formulas down or enlarge tableChange to ""... IEEE 802.11b WLAN and ...""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.! & KUJH4{B4 0Cap0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.1.7331E@)Delete ""it is.""TE-Do not accept This is copied from the given reference. If permission is not obtained, entire definition will be removed.XO@nP t0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.1.3321Eperiod missing. add period.TE-AgreeXO TE-AgreenP v0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.1.2316TR@)@.TE-Do not accept. A term shall be general enough to be applied else where within the IEEE.XO@nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola33.138TR@)Define ""set of rules.""TE-Do not accept. A term shall be general enough to be applied else where within the IEEE.XO@nP `<@laway, Eded.callaway0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola011.1147ER@ )z@.TE-?? Scope must match scope in PAR, cannot change unless text in PAR is changedXO@T<: ;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil1212.2.1775EReference to Figure xxxF@.TE-?? Is the correct figure 53?AC ACCEPT.HHH31/~X<: ;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil09Table 103310-20E BT is used instead of 802.15.1Replace BT with 802.15.1.TE-AgreeAC ACCEPT.FFF1/-~X<: ;@D@MichD@D@D@0Seals, Michaelmseals@intersil.com321-724-7172Intersil09Figure 173321-51Ev@ )"Replace Bluetooth with 802.15.1.TE-AgreeAC ACCEPT.///~X<:];@I@MichI@I@D@I@0Seals, Michaelmseals@intersil.com321-724-7172Intersil066.0298E!Bad citation of Bluetooth spec.^@.TE-Agree Will remove the end of the sentenceAC ACCEPT. citessmWUS`DB;@I@MichI@I@I@I@0Seals, Michaelmseals@intersil.com321-724-7172Intersil055.4.2.1226TR@ )R@.TE-??ACT@`DBLVAL;2 0 ( f R 2  \DJ,zBluetooth should be spelleREJECT. SME is standard IEEE 802.11 terminologyREJECT. REJECT. No requirement for IEEE 80ACCEPT. It appears to be an PDF artifact.REJECT. No requirement for IEEE 802 style.REJECT. No need to redefine master slave when 802.15.1 is a normative reference listed in clause 2.ACCEPT. This was due to a formatting error caused by an excessively long title.REJECT. Not a requirement for IEEE style.REJECT. No requirement for IEEE 802 styleACCEPT IN PRINCIPLE. Will change must to shouldACCEPT IN PRINCIPLE. Formatting will be done by IEEE editing staff later.ACCEPT. Since this was the resolution for TG1's draftREJECT. SME is standard IEEE 802.11 terminology, no need to repeat here, which is listed as a normative reference in clause 2.ACCEPT IN PRINCIPLE. Figures will be redrawn.ACCEPT. Will remove editor's note.ACCEPT IN PRINCIPLE. Either PER or BER can be used. The text is rewritten to address this point.ACCEPT IN PRINCIPLE. Figure XXX change to figure 53ACCEPT IN PRINCIPLE. Cross referenceREJECT. LMP is in acronym list clause 3.2REJECT. Because TGg is not finalized.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eREJECT. Non collaborative solutions will not solve the collocated issue.REJECT. Lack of resources, **Jim's response on 3dB difference.ACCEPT IN PRINCIPLE. Will correct the title by removing the 802.15.1reference from the caption.REJECT. For table 24, PCF is used for completeness. PCF is not used for coexistence studies.REJECT. Copied directly from the PARREJECT. No need to redefine master slave when 802.15.1 is a normative reference listed in clause 2.ACCEPT IN PRINCIPLE. Editor's note about 2 Mbit/s will be removed, since 2 Mbit/s is now included.ACCEPT IN PRINCIPLE. Will delete the editor's note.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eLVAL ^j  &This document only applies to WPANs and 802.11-1999, not to aThis document only applies to WPANs and 802.11-1999, not to any other wireless technologies.It is said to be a complex baseband model. But the equations in the subclauses sometimes are presented in a passband form.Typo IEEE802.119 should be IEEE802.11bdelete ""The resulting performance curves are quite accurate, but they are obtained at the expense of significant computation.""In Table 10: Should the references to ""BT"" be changed to 802.15.1?Figure text smaller than that allowed in IEEE Style Guide (applies throughout) Figures 9, 10, 11, 12, 13, 14, 15Do you need this Clause? Although Spectrum factor is shown in Figure 3, it doesn't seem to be used anywhere else.Control of legacy systems will not work when a legacy device is not in power save mode and wakes up to transmit a packet.figure 42 has a legend of 8 items, but only 7 curvesWhile there is an extensive treatment of the calculation of bit error rate from SINR, the performance results shown in clause 9 show packet error rate. There is a dubious statement that 'the packet error rate for the WLAN corresponds to the loss of ACK messages'. In reality the packet error rate will be dominated by the loss of data packets, since they tend to be longer than ACK packets and hence more vulnerable to bit errors. This would yield more pessimistic results then those shown. On the other hand there is no discussion of the correlation of the bit errors. If there is structure in the interference (and in this case there is) then bit errors tend to be correlated. This would yield a packet error rate which is less than that for i.i.d. distributed bit errors, i.e. it would make the results more favorable. A third effect which aggravates the packet error rate is the effect of interference on packet detection, which is not modeled and which tends to dominate the probability of packet loss by decoding errors, especially at low SINRs.LVAL r $ `H44|                                           The bibliographic cross reference using the author's last name detracts from the sentence flow.The cross-reference to the Bluetooth specification is brokenBluetooth spelled wrong. Also the sentence is a little strange. The last sentence really should end in a colon.The model uses only 32 of the 79 hopping frequencies at a time with no justification.Gratuitous use of capitalization.The actual OPNET model used is not provided in the draft.The text lists multiple devices and uses improper language.Gratuitous use of capitalization. "Medium Free", "True" and "Medium"The term TU is not in the acronyms list nor is it defined in this document.The formatting for the MLME primitives could be improved (IMHO)Change "of these parameters are shown" to be "of this parameter is shown"The font for "FALSE" in the valid range column appears to be wrong.SME has not been defined. (This is true for 10.2.2.1.2 as well.)The WPAN interval field explanation precedes the figure rather than following the figure.Missing spaces, "activity.The decision" and "receiving .Additional state"ACL has already been introduced, no need to spell it out here.The word "must" needs to be "shall" here.SCO has been introduced already, just use the acronym. Change "can not" to be "is not able to".Change "in AWMA the IEEE 802.11 Access Point can transmit" to be "in AWMA is that the IEEE 802.11 AP may transmit"Extra space in "pattern. At any time"?Cut and paste error, in the Note column change "Beacon frames" to be "Probe Response frames"WLANs operate over larger ranges than the AP distance of 15 m used in Clause 9 and 11 PER and delay plots.Not all 802.11 frame exchanges have an ACK.How was the receive mask for 802.11b derived? 802.11b has no receive mask. The 802.11b adjacent channel specification only addresses another 802.11b signal in the adjacent channel. Converting this specification to a mask for narrowband interferers is a very uncertain extrapolationLVALw6`D+Q +  ?(Q +Q PQ (Q T Q Q Q "Q JQ rQ Q Q Q Q Q *Q JQ zQ Q Q Q Q "Q JQ rQ Q Q Q Q Q Q Q @Q hQ Q Q Q Q Q Q @Q pQ Q Q Q Q Q @Q hQ Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q Q "Q JQ rQ Q Q Q Q Q *Q JQ zQ Q Q Q Q "Q JQ rQ Q Q Q             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 Q x Q Q ` Q   Q fhC@ Q Q Q @A Q @A Q @A "Q @A JQ @A rQ @A Q @A Q @AQ @A Q @A Q @A *Q @A JQ @A zQ @A Q @A Q @A Q @A Q @A "Q @A JQ @A rQ @A Q @A Q @A Q @A MainQ  Q Q X"Q Q )X:C@~sq_ffMain Q  Q `Q  Q hQ  Q pQ  Q xQ  @Q Q  hQ Q  Q Q  Q Q  Q Q   Q Q   Q Q   Q Q   @Q Q   pQ Q  Q Q  Q Q  Q Q  Q Q  Q Q  @Q Q  hQ Q  Q Q  Q Q  Q Q Q Q Q Q @Q hQ Q Q Q Q Q  Q @Q pQ Q Q Q Q Q @Q hQ Q Q Q Q @A Q @A Q @A "Q @A JQ @A rQ @A Q @A Q @A Q @A Q @A Q @A *Q @A JQ @A zQ @A Q @A Q @A Q @A Q @A "Q @A JQ @A rQ @A Q @A Q @A Q @A Main Q Q  Q Q  Q Q  "Q Q  JQ Q  rQ Q  Q Q  Q Q  Q Q  Q Q  Q Q  *Q Q  JQ Q  zQ Q  Q Q  Q Q  Q Q  Q Q  "Q Q  JQ (Q  rQ 0Q  Q 8Q  Q @Q  Q HQ Q Q Q Q @Q hQ Q Q Q Q Q  Q @Q pQ Q Q Q Q Q @Q hQ Q Q Q  Q )Q $Q  Q 8Q Q Q XQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q PQ Q ! PXF6"?@0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.1.11929Eb@5~@.TE-Do not accept IEEE Standards Style Manual (9/20/02) clause 19 states as currently used.XO@ nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.11851EF@5F@.TE-AgreeXO TE-AgreenP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.3.6.3165T\@5Change to ""differential.""TE-?? Not the only place where this term is used, which is correct?XO@usqnP 80Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.3.6.11442TR@5$@ .TE-??XOTE-??nP 90Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola5Table 3, 4, 51311-46T@5Add a sample calculation.TE-??XOTE-?? nP A0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.3.21145TR@5@ .TE-??XOTE-??nP F0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.21035Tf@5x@ .TE-??XOTE-??nP G0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.3.2922E@)@ .TE-??XOTE-??nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.2826E@)@ .TE-?? English reading indicates only two, but it is confusing for detemining the pairingXO@xvtnP i0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola44.1.3749E""exact same"" is redundant.delete ""exact""TE-AgreeXO TE-Agree"  nP `<@laway, Eded.callaway0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola044.1.1654EL@) Add commas.TE-AgreeXO TE-Agree555 T<: $`<@laway, Eded.callaway0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola033.1.8336T@)@.TE-??XOTE-??  T<: $LVALЂ008bcǟFDon't select an element ID, but instruct the editorDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There's lots of ""M Weik"" in section 3.1Who Don't select an element ID, but instruct the editor to find an unused one. YouDon't select an element ID, but instruct the editor to find an unused oDon't select an element ID, but instruct the eDon't select an element ID, but insDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There's lots of ""M Weik"" in section 3.1Who owns theDon't select an element ID, but instruct the editor to find an unused one. You cannDon't select an element ID, but instruct the editorDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There's lots of ""M Weik"" in section 3.1Who owDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There'Don't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There's lots of ""M Weik"" in section 3.1Who owns the trademark onDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There's lots of ""M Weik"" in section 3.1Who owns the trademark on ""Wireless Personal Area Networks""??""vendor specific"" is not what is intended, I think.Incorrect period placement and capitalization: ""above. (See 1Don't select an element ID, but instruct the editor to find an unuseDon't select an element ID, but instruct the editor to find an unusedDon't select an element ID, but instruct the editor tDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.There's lots of ""M Weik"" in section 3.1Who owns the trademark on ""Wireless Personal Area Networks""??LVALVPQ Q PQ Q PQ Q PQ Q 8Q +Q p&Q "KQ X"Q `0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  0LQ X"Q  LQ X"Q  $LQ X"Q  $LQ X"Q  $0LQ X"Q  0LQ X"Q  0LQ X"Q  KQ X"Q  KQ X"Q  KQ X"Q  KQ X"Q  KQ X"Q  KQ X"Q  0LQ X"Q  Q z 'Q +Q 'Q `C Q Q PQ h#Q Q x#Q Q #Q Q #Q 0Q #Q hQ #Q Q #Q Q #Q Q #Q HQ #Q  Q $Q  Q $Q  Q ($Q ( Q 8$Q ` Q H$Q  Q X$Q  Q h$Q !Q x$Q @!Q $Q x!Q $Q !Q $Q !Q $Q  "Q $Q Q  PQ  Q  Q  Q  0Q  dhQ  Q  dQ  dQ  HQ  Q  Q  Q  ( Q  ` Q  d Q  Q !Q @!Q x!Q !Q !Q  d "Q `&Q 'Q 'Q 'Q 'Q 'Q ('Q 0'Q 8'Q @'Q H'Q P'Q X'Q `'Q h'Q p'Q x'Q 'Q 'Q 'Q 'Q 'Q 'Q 'Q Q PQ Q Q Q 0Q hQ Q Q Q HQ Q Q Q ( Q ` Q  Q  Q !Q @!Q x!Q !Q !Q  "Q X"Q Main'Q CommentID(Q Q v +Q *Q +Q Q )Q )Qq )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q )Q p+Q  PQ +Q `+Q +Q (Q MainCommentIDKQ (Q +Q $Q +Q KQ )Q +Q P+Q +Q +Q X"Q ! t^'ɿǯƇŃsNE30Ca0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1111.06138E@5""above (see 12.1).""TE-Do not accept As per The Gregg Reference ManualXOf@ WKIGnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1010.4.16038E ""t the""delete ""t.""TE-?? Might be a variable and not an extraneous "t"XOh@ `TRPnP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola10Table 215242E@ 5p@8TE-AgreeXO TE-AgreenP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.33824T@ 5@8TE-??XOTE-??nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.2372429EStyle is informal.@.TE-??XOTE-??nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola99.13548T|@ 5H@.TE-??XOTE-??nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola66.0298ECitation error.B@.TE-Agree Will remove the end of the sentenceXOZ@ ?31/nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.1.2205E!Symbol list style inconsistent.@.TE-??XOTE-??nP 0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola55.4.1.1205E@ 5`@.TE-??XOTE-??nP )`<@laway, Eded.callaway)0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.4.1.11941EV@ 5@.TE-??XOTE-??%%%T<: L(`<@laway, Eded.callaway(0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola055.4.1.11936Ef@5f@.TE-??XOTE-??%%%T<: L'`<@laway, Eded.callaway'0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola0000E@5P@.TE-Do not accept IEEE Standards Style Manual (9/20/02) clause 19 states as currently used.XO@ T<: dLVALv` ` x ^ pT         Improve 5.2/5.3 with multipath model taking into account BT/11b differences in frequenImprove 5.2/5.3 with multipath model taking into account BT/11b differences in frequImprove 5.2/5.3 with multipath model taking into accountImprove 5.2/5.3 with multipath modelImprove 5.2/5.3 with multipath model taking into account BT/11b differences in frequency selectivity and antenna diversity.Add editing instruction: ""Add the following element to table 20 of ... and assign an available element ID"".Re-word sentence:These two parameters are programmable over the WLAN and can be allowed to change dynamically according to the load of the two wireless systems. Delete all references to it in the Recommended PracticeChange ""(and hence link loss) is constant."" to ""(and hence link loss) is assumed constant.""Add ""Frequency nulling"" to clause 3.1 as a definition or term.Replace ""IEEE 802.15.2 has decided to select"" to ""This recommended practice selects"".Remove all references to collaborative coexistence techniques in the document. Modify Section 4.3 to delete references to Collaborative models. Delete Section 4.3.2 Delete Section 10In the absence of any such coordination, remove section 12.3.Add a statement of compatibility to the BT SIG AFH mechanism.Remove all mention of communication between slave and master in this section. Make appropriate adjustments so that master operates only on the basis of local knowledge.Remove this comment or add normative editing instructions to change 802.11.Remove the MLME interface and add section saying that the MIB values are updated whenever a beacon is received. Beacon transmitted contains latest MIB values of these variables. Support T1 and TWLAN MIB variables (TWPAN is redundant and problemmatical if TWLAN+TWPAN != TB).Add "" or when SCO links need to be supported."" to the end of this para.I'll give you a wmf from my original drawing.Add to reference section and make references by [1] rather than name.|LVALN`D0 X2 t X  ?2 X2 2 2  @2 2 B2 j2 2 2 02 X2 2 2 2 2 2 2 B2 j2    ȅ  d   !TypeList.TypeListTypeListTypeList.CommentTypeList.SubjectTypeList.Header2 2 H2 X2  x2 ݨ @ 2 2 x2 +2  B2  j2 2 2 2  2 x2 G1@=~sq_cfFinalReports~sq_cTypeList2  2 p2  2 x2  02 2  X2 2 2 2 02 X2 2  2  B2  j2 TypeList 2 2  2 2  B2 2  j2 2 2 2 02 X2  2 (2  2  x2 82 H2 X2 h2 x2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 h2 2 0L2 2  0L2 2  0L2 2  L2 2  $2 z x2 2 2 2  2  2 2  2 2  H 2 2   2  ȃ 2  d 2  H 2 8P2 X2 `2 h2  2  2  2 H 2  2 TypeList2 2 v 2 2 2 (2 (2q (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 (2 2  2 2 2 P2 2 TypeListK2 2 2 2 2 K2 (2 2 2 2 82  2 S! 0,M(MKIi GE[DCy0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.3.151T@; Swap them.TE-??XOTE-??!  ~`(?;@H@s, AH@H@ian.J@0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.3.151T@; Swap them.TE-??AC ACCEPT. table19jjaJHF<$dDB|0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.2.45028T@@ 8TE-??XOTE-??~`(q0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.2.2.6.34824T@5@ 8TE-??XOTE-??!  ~`(;@D@s, AD@nadrian.0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.2.243T`@*@8TE-??XW666642( \<:Y T;@D@s, AD@nadrian.0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.242TV@;@?TE-??XW22220.$   \<:Y :;@H@s, AH@H@ian.J@0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1010.141T@@8TE-??AC ACCEPT. PPP:86, dDB;@I@s, AI@I@ian.0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation05Figures 9-1525EThese figures are too small.Make them bigger.TE-??AC@5sqoeF\<: $;@I@s, AI@I@ian.0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation055.3.21223-49EFigure 3 looks really naf.Z@8TE-??ACD@4fffZXVL@ \<:5`<@laway, Eded.callaway50Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1212.1.2.47322Eextra comma.Delete comma.TE-AgreeXO TE-AgreeMMM753#T<: 4`<@laway, Eded.callaway40Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola1212.1.1.17117Ej@5H@8TE-??XOTE-??'''T<: dLVAL ͪͪ l $ ^r,bx|<@ 0Callaway, Eded.callaway@motinexact statement: "" can support uinexact statement: "" can support up to three channels in the IMS band."""Many variables are used without indicating their meanings, namely: NG, Nmin and p(k)."Why does the 802.15.1 system model have a DBPSK mode?It is not clear to the reader that PTA is the second MAC layer technique.Figure xxx needs defining Table 29 formulas run into boarderLine 3 - 'case, by increasing' Line 8 - 'to around 1..'line 48 - And such Line 51 - another, sodifferentiated In note 3 at bottom of page 'much likely that'There is no group known as 802.119.The sentence is not clear. "Note that the same partition sequence value is assigned to both the master and the slave."It is meaningless to define values contained in LMP commands unless there is a defined coordination between the BT SIG and 802.15.2 that permits 802.15.2 to define LMP commands and features.Section 12.2. It is not clear from this section whether it is an alternative to the AFH that will be defined by the BT SIG, or is intended to be compatible with it.This section is meaningless. There is no NACK in 802.11 or 802.15.1.There is no point defining behaviour requiring negotiation before use (such as setting up an EV3 connection) if there is no agreed means for 802.15.2 to define modifications to the connection setup process and LMP commands.I see packet scheduling only of value when a new master device talks to a legacy device. A legacy device is unable to characterise the channel and report the frequency usage table.Table 19 has an error. The adjacent ""none"" and ""receive"" cells near the bottom RH need to be swapped.Section 10.2 needs some work. The T1 and one of the TWLAN/TWPAN need to be communicated. The other duraction can be calculated from TB. This document should include changes to 802.11 in the form of editing instructions to a particular revision of 802.11(see the other 802.11 drafts for examples). !GNLK;JIHG!FDCBAA5@k/"0Kline, Daviddave_kline2@hp.com541-715-7607Hewlett Packard1010.14146TRx@> @?XO|^^F" ߿"0Kline, Daviddave_kline2@hp.com541-715-7607Hewlett Packard1010.1422TR$@>B@8XO|^^F" ߿0John, Kowalskikowalskj@sharplabs.com(360) 817 7520Sharp Labs44.3.2915TRF@>n@8XOllP$߿0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies55.11026E@>@8TE-??XOTE-??hP 0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies44.3.2922E@>@8TE-??XOTE-??hP 0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies44.3839EX@>@8TE-AgreeXO TE-AgreehP 0Carlos Rioscarlos@riostek.com(408)202-6294(408)202-6294RiosTek LLC1010.1, 10.2, 10.3, 10.440TR @r@8Non collaborative solutions will not solve the collocated issue.XW@l`^\v\B0Housley, Russellrhousley@rsasecurity.com703-435-1775RSA Laboratories11.2221EChange "802.119" to "802.11bChange "802.119" to "802.11bTE-AgreeXO TE-AgreeppX(-0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1212.274TJ@;z@ 8TE-??XOTE-??~`(0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1212.1.1.471T@;Remove sectionTE-??XOTE-??)~`(W0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1111.2.164T@;Remove all mention of EV3.TE-??XOTE-??1~`(;@D@s, AD@nadrian. 0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1111.366Tj@;R@ 8TE-??XW22220.$   \<:Y ;@D@s, AD@nadrian.0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation1111.1.26312-43E!Figure 43 needs to be re-drawn.TE-?? Action for J. LiangDW@}{GG \<:[,LVAL5.^ ̎ ˾ .\"PJACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being suACCEPT. reference changed to 10.3.6ACCEPT 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.11eREJECT. No, 802.11g is not covered by this recommended practiceACCEPT. This is defined in table 24.ACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.ACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.REJECT. The timing of CTS will be investigatedREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e.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.11e.ACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eACCEPT IN PRINCIPLE. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eREJECT. TU is standard IEEE 802.11 terminology, no need to repeat here, which is listed as a normative reference in clause 2.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11e Outside the scopeREJECT. 802.11g will not be included in the recommended practice.REJECT. Scope does not cover 802.11e.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eLVALШ ǢHF**>B?0Stephens, AdrianadrianIn order for AWMA to work and to not burdenMissing space between encodes and \phi\sub{1}Tables 3, 4, 5 should be in decibels.BER calculation should also be in equation form.mechanisms assume DCF, when .11e uses HCFno spec regarding non-collaborative methodology (interference avoidance) between 802.11 and Bluetooth (only Bluetooth)These clauses (5 - 9) belong in an informative annex to the Recommended Practice, as there is nothing within them to 'practice.'The definition of GFSK signal can be found in most textbooks. It is not necessary to have it here.typo: "" Wireless Personnal Communications""typo: "" discusses the physcial layer ""reference is missing: ""Figure xxx shows ""missing space characters: ""1.6ms to 2.6ms "": ""802.15.1 activity havegreater priority ""missing space character: "" transmit activity.The decision ""AWMA is recommended for high density WLAN/WPAN areas. As such there will be 3 non-overlapping WLANs in the same area.. For AWMA to be effective, all the WLANs need to share the same time sharing parameters and have the same clock timing. A method needs to be developed that allows all the WLANs to coordinate timing.AWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.Dividing beacon interval for 802.11 will have problems for legacy stations, will have problems maintaining QoS for 802.11e, and will interfere with certain timers.This discussion of stationarity indicates that the parameters are constant when they are, in fact, assumed constant.Frequency nulling is mentioned, but the definition is not easily found (or possibly unavailable.)This clause starts with a reference to the group that wrote the recommended practice as ""IEEE 802.15.2"". It is awkward in the context of a completed recommended practiceBLVAL. V ` . &2v, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola3.1TRThe phrase ""set of rules"" is used in many definitions, and is undefinSoltanian [B14] contains additional resultChange "must be larger" to be "shall be large"Include some examples with a larger AP distance.Clarify the limitations of this model in addressinChange "must be larger" to be "shall be large"Include some examples with a larger AP distance.Clarify the limitations of this model in addressing implementation isChange "must be larger" to be "shall be large"Include some examples with a larger AP distance.Clarify the limitations of thisChange "must be larger" to be "shall be large"Include some examples with a larger AP distance.Clarify the limitations of this model in addressing implementation issues which are out of the scope of 802.11 and 802.15.Supply a diagram of the spectral effects and calculations and input data used to derive these tables.Signal T1 and TWLAN. Add ""editing instructions"" to this document for any required changes to 802.11.Both frequency-hopping systems are susceptible to interference on the channel in use and the two adjacent channels.Soltanian [B14] contains additional results for flat fading channels.The outline of the clause is as follows: subclause 5.4.1 describes the model for IEEE 802.15.1 and sub-clause 5.4.2 describes the model for for 802.11b.Given the number of bits per symbol, the SER is converted into an effective BER.to impact the performance of higher layers.to-The MAC layer models interface to these PHY models,The IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link, without data loss. A interference increases, the network latency increases, and data throughput decreases.Most implementations allow manual or automatic modification of the data rateThe IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link, without data loss. A interference increases, the network latency increases, and data throughput decreases.!NMLKJIHGF FEDCB$A/@"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.2726-27En@BXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.2725E@ A@?XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.2721-22EX@ AXOh* ߟw"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.2719-23E@ A@?XOh* ߿""0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.1712-15E@@?XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.176-10E@AXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.171ET@AXOh* ߟv"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.1654E|@AXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1611E@XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman11.2220E what is ""IEEE 802.119 WLAN""?try IEEE 802.11b WLANXOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman11.2225-27E@XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman11.2213E@AXOh* ߟ@@ickinsky, alanachick0"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman011.127Tp@AXO^>:ߟ C"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman11.1149-54E@AXOh* ߟ"0Kline, Daviddave_kline2@hp.com541-715-7607Hewlett Packard1010.04050TR @AF@?XO|^^F" ߿`?@H@ DavH@H@line-"0Kline, Daviddave_kline2@hp.com541-715-7607Hewlett Packard1010.14149TR@@AU@zV>:߿۬LVALp N NN ~ $ 2LVXp @ @ where is the detailed interfThe text uses "can" which might be confused as formal language, which is it not.Informal language uses can instead of may which is required.iT is not set off and a space is missing in "as[B4]"Space missing in "equations[B3][B4]." Also, this section has too much space following the period between sentences.Orphaned text, doesn't belong here."different" is redundant and the article is missing. The next sentence needs some help too.Extra capitalization in "802.15.1 Baseband" (line 21) and "802.11b Control" (2 places)All of the paragraphs ended up in the bookmarks of the PDF file, rather than just the chapter headings.The figure cross references have an extra dash following them.The method used to calculate the spectrum factor is not defined in this subclause, or anywhere else in the documentwhere is the detailed interfence model (place reference in text)There is a potential packet collision between a WLAN packet and an interfering 802.15.1 packet any time the WPAN hops into the WLAN passband.This line makes no sense- The higher rates are desirable for many applications but the distance of transmission using the higher rates is less than that of the lower rates.Most implementations allow either manual or automatic modification of the data rate.The example does not support the text. In fact the example appears not to be an example""So the odds are that"" should be deletedThe word ""for say 100 ms"" should be ""for example 100 msec""the sentance talks about a project. Isn't this a recommendation, like stated in line 18?Paragraph 1.1 has 2 Mbit/s specified. Why the comment?the three sentances need and introduction. Or perhaps ""the scope... is"" Bullet 1 ""To ..."" Also note that on page 2 it starts ""The scope of this document..."". Are lines 40-54 really needed?PTA can only work if the WPAN device also uses adaptive frequency hopping to avoid interfering with other WLANs in the same location.LVALΞ > $Ǩ\""nV=&0Callaway, Eded.callaway3 =&0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola11.0EIncorrect period placement and capitalization: ""above. (See 12.1All of the definitions are missing a space betAll of the definitions are missing a space between the : and the start of the definition.The terms master and slave have not been defined in this document.Need to add space between CSMA/CA and its definition.Change "inter frame" to either "inter-frame" or "interframe"SIR: change "interfere" to be "interference"SNR: Parenthetical comment seems out of place.Both packet and packet error rate are definitions and should be in 3.1Clause 4 should start on an odd page numberFirst letter of sentence is not capitalized.Clause 5 does not start on its own page.Font size problem in Table 24, second column second row. Also, missing space in "havegreater" in Table 25, column 2, 4th row.This sampling rate is appropriate for f d up to 22 MHz. A uniform random delay t d = [0,T) and a random phaseThis is then converted into an effective BER given the number of bits per symbol.change impact the performance of higher layer applications and the MAC layer.change The MAC layer models are interfaced to these PHY models,remove the word ""respectively"". With respect to what?specify where the model is located- The detailed model described later quantifies the level of packet error rate.change Both frequency-hopping systems are usually only susceptible to interference on the channel in use and the two adjacent channels.redo ""The IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link. So there is little chance that the data will be lost. The effect the interference has on the WLAN is that the delivered data throughput decreases and the network latency increases. Depending on the application this may or may not be tolerable.""the following sentance makes no sense Since the bandwidth of the 802.11b WLAN is 22 MHz, as the WPAN hops around the ISM band 22 of the 79 WPAN channels fall within the WLAN passband.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%FE#!NMLKJIHHGF$E'D4C7BPAQ@"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.41832-34E@@XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman00--TR@XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.3.61436E@B@ ?XOh* ߿~"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.3.198-12E@XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.3841-43E:@@JXOh* ߿}"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman4233-35E@IN@JXOh* ߻y"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.2831-32E@BV@ ?XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman4829####E~@Bn@?XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.2825Ep@BXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.4811-19E @I*@JXOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.383-7E@I@JXOh* ߿8"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman41.3452E@BXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.3751E@B@ ?XOh* ߿!"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.1612-15E@B@?XOh* ߿H"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman44.1.2735-40E@XOh* ߟX@@ickinsky, alanachick="0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman044.1.2732E@ AXO^>:ߟ HLVAL  ^phens, Adrianadrian.stephens@mobilian.com+44 1954 20Change the double arrow to two inward pointing arrows. I thought the double arrow was a diamond.change Similarly, changes in the behavior of the MAC layer protocol and the associated data traffic distribution could play an important factor in the interference scenario and affect the overall system performance.change IEEE 802.15.1 uses frequency hopping spread spectrum, while IEEE 802.11b is a frequency-static system that uses direct sequence spread spectrum and complementary code keying. The bandwidth of 802.11b is about 22 MHz so of the 79 channels that 802.15.1 hops over, approximately 22 of those channels are subject to interference, depending on signal power levels. 18 The detailed model described later quantifies the level of packet error rate. The 802.11b represents a worse interferer than the 802.11 FH. For data transfer the network throughput would decrease and the network latency would increase, in the presence of 802.11b interference. The packet error rate for SCO link can cause voice quality degradation. Since a frequency hopping system is susceptible not only on the channel it is operating, but also the adjacent channels, the 22 channels susceptible channels could be increase to 24 channels.change So with limited packet error rate the ACL link will have a small decrease in network throughput and a small increase in network latency. However, for delivery of voice IEEE 802.15.1 uses a synchronous connection-oriented (SCO) link. The SCO link does not support automatic repeat request. As a result there will be some perceivable degradation in voice quality over an SCO link in the presence of 802.11 FH interference. The detailed model described later quantifies the level of packet error rate. The 802.11b represents a worse interferer than the 802.11 FH. For data transfer the network throughput would decrease and the network latency would increase, in the presence of 802.11b interference. The packet error rate for SCO link can cause voice quality degradation.LVAL Ɋ . Lower case "collaborative", "non" and "non-collaborative" in this paragraph.Please lower case here and at other occurances as appropriate.Need to define TU and add to Lower case "collaborative", "non" and "non-collaborative" in this paragraph.Please lower case here and at other occurances as appropriate.Need to define TU and add to the acronym list.Please check and correct if necessary.Collaborative is defined as a coexistence mechanism where WPAN and WLAN exchange information r to minimize mutual interference. Non-Collaborative is defined as a coexistence mechanism where no exchange of information between two wireless networks occur.to IEEE 802.15.1 uses frequency hopping spLower case "collaborative", "non" and "non-collaborative" in this paragraph.Please lower case here and at other occurances as appropriate.Need to define TU and add to the acronym list.Please check and correct if necessary.Collaborative is defined as a coeLower case "collaborative", "non" and "non-collaborative" in this paragraph.Please lower case here and at other occurances as appropriate.Need to define TU and add to the acronym list.Please check and correct if necessary.to IEEE 802.15.1 uses frequency hopping spread spectrum, while IEEE 802.11b uses direct sequence spread spectrum and complementary code keying. The bandwidth of 802.11b is 22 MHz. 22 of the 79 hopping channels available to IEEE 802.15.1 hops are subject to interference. A frequency hopping system is susceptible to interference from the adjacent channels. This increases the total number of interference channels from 22 to 24.16 17 18 The detailed model described later quantifies the level of packet error rate. The 802.11b represents a worse interferer than the 802.11 FH. For data transfer the network throughput would decrease and the network latency would increase, in the presence of 802.11b interference. The packet error rate for SCO link can cause voice quality degradation.lLVAL#f * J 6 n*p z,OPNET should probably have TM at its first usage and have a disclaimer somewhere in the text that says who owns this trademark."inter arrival" should be "inter-arrival"DSSS and FHSS have already been defined, no need to spell it out here. "Mobile" should be lower case everywhere it appears.The text for TBTT is not centered under its mark in the figureChange "... is double than when it is ..." to be "... is double that when it is ..."Extra period on the end of the sentenceThe sentence reads better without the delay in parentheses.Bluetooth is referenced (with TM) in the footnote, but ownership of the trademark has not been indicated.Improper capitalization of "Physical"Clause 10 should start on its own, odd page number"And such" should be "As such". Missing space in "Recommendation:Thus"Change "the medium on dynamically" to be "the medium dynamically"Missing space in "Recommendation:Thus""Master" and "Slave" should not be capitalized.Overlapping text on the front pageNo abstract is listed on the title pageShouldn't IEEE Std P802.15.1-2001 be IEEE Std P802.15.1-2002?The scope section is not written in complete sentences."A future revision of this document ... and WPAN standards." presupposes the approval of a PAR which has not yet been written.The purpose section does not match the PAR.802.119 should be either 802.11 or 802.11bWe should be able to put in the approved draft here (it is referenced in 1.1)."sub clause" should be "subclause"figure 48 legand states ""wo"" it should be ""w/o""title in figures 39 and 40 have extra period after ""nulling""is this a recommended practice or a standard?the word ""dynamically"" is an adverb. What is it modifying? ""The PTA technique however coordinates sharing of the medium on dynamically, based on the traffic load of the two wireless networks.""Some of the text and the figures have been taken from Soltanian [B14], which also contains additional results for flat fading channels.!! ONMLJI IH&G)F0E?DLCGBPAO@"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.17041E@P@OXOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.17030-33E^@XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1111.3.1699-10E@P@OXOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1111.3.1691T@PXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1111.36820Ef@ KXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1010.4.2613-17Th@1XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1010.458-5942-17E|@ KXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1010.3.85729TZ@KXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1010.24235E@IXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1010.2425E@KXOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1010.1423-4E@K@OXOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.4.1.22027-28E@ Bp@OXOh* ߿O"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.4.1191TRwhat is meant by '79(23)'?XOh* ߟ"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.41844-45E@K@ ?XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.41841-42E$@K2@ ?XOh* ߿"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman55.41836-37E@1XOh* ߟLVAL14 " v D n n nX4nalloREJECT. Management of the AWMA Coexistence MechREJECT. MaACCEPT IN PRINCIPACCEPT IN PACCEPT IN PRINCIPLE. Effect is nowACCEPT IN PRINCIPLE. Scope will be modified to include FH and delete clause 4.1.3.ACCEPT IN PRINCIPLE. Effect is now acceptable for both postions and affect may no longer be used.REJECT. They are available on a web site.ACCEPT IN PRINCIPLE. To be fixed by IEEE 802 editorsACCEPT IN PRINCIPLE. Background RSSI is a way to do it.REJECT. No, but the previous redundant "access code correlator fails" will be deleted.ACCEPT IN PRINCIPLE. Every packet has at least an access code and a header, but not necessarily a payload.REJECT. A master's receiving time slot is an odd time slot.REJECT. RxQuality is not available for AFH in 802.15.1 (Bluetooth) devices.REJECT. The RSSI here is for 802.15.1/Bluetooth devices, not 802.11b devices.ACCEPT IN PRINCIPLE. Clause is rewritten to address and clarify this comment.ACCEPT IN PRINCIPLE. Clause is rewritten to address and clarify this comment. Answer to question is yes.ACCEPT IN PRINCIPLE. Clause is rewritten to address and clarify this comment.REJECT. Will include LMP commands for setting up EV3 packetsREJECT. Two curves may be overlapping, figure will be enlarged.ACCEPT. It is a recommended practiceREJECT. PTA does not require AFH.REJECT. PTA does not require AFHREJECT. The perceived behaviour is not accurate.ACCEPT IN PRINCIPLE. All parameter are include, simulation time was sufficient for accurate results.ACCEPT. Will change to 1, 2, 5.5, and 11ACCEPT. Will change to 1, 2, 5.5, and 11ACCEPT IN PRINCIPLE. Will delete orthogonal and modify equation for better fit/approximationACCEPT IN PRINCIPLE. Editor will look into changing to dB; we may replace these tables with a figure.REJECT. We have not considered implementation-specific effects.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11er LVAL Nࡱ> <2QlC  6 )   +!ORoot Entry0۵(&VBANSp,o-VBAProject NSХm-VBANSХm-7   , 6# %m 57&k2  t1B?3$<89(@B-DVGHIJKLMPQRSTUXWlYZ[]^_`abcdefghijm nqrsuvz{}~Root Entry(&VBANSp,o-VBAProject NSХm-VBANSХm-YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE:PROJECTPROJECTwmaAcessVBAData 7   6# m 547%&k2  t1?$B;89(=>C-ENGHIJKLMPO\QRSTUXYZ[]p^_`abcdefghijm qxy|DirDataThe document only addresses 802.11B interference while current standardization in the 2.4 GHz band is covered in the 802.11G annex. The new modulation schemes proposed in 11G need to be taken into account in the analysis on mutual interference and in proposed solutions. Any new development in this band is likely to address 802.11G rather than just 11B. Any investment in collaborative schemes must have applicability for 11G to be of interest.LVAL " . 2J"fJ"Note that the same partition sequence value is assigned to both the master-to-slave slot and the immediately following slave-to-master slot."Make a clearer explanation or redo the work?Non-Collaborative ""techniques"" or ""mechanisms""Delete this clause- in fact, delete the whole section relating to AWMADelete it as it exists. A better method is to have fixed channelization partitioned between the 2 systems as in 10.4Include a comparison of before and after AFH similar to figure 46 and its supporting text.Explain more fully how the PCF is affected by a denial at a TX request.Since table 20 defines the ""receive"" collision type as ""in-band"", then it makes sense to swap the entries in table 19 so ""receive"" appears in the ""in-band"" location.Illustrate how the knowledge of T1 is shared, or explicitly share it in the beacon element.Either correct my assumption about what a recommended practice may do, or complete the required coordination with 802.11 to insert this into the standard (possibly under QoS enhancements). (802.15 coordination needed too)Insert a functional definition for colocationChange scope so that this document provides ""guidelines for all current and future 802.15 standards to ensure interoperability""File the document away as an interesting set of ideas and let the market forces develop appropriate solutions. Giving the document the status of recommended practice at this stage implies we understand the spectrum of solutions and can make a reasonable recommendation; we can't!This will compromise the accuracy of the measurements at each channel.12.1.1.1. received signal strength indication (RSSI)(a bit map standing for conditions of different channels) will be used to compile a final list of goodWhen bad channels are used, dropped packets are retransmitted, yielding large delays.The PTA technique coordinates sharing of the medium on dynamically, based on the traffic load of the two wireless networks.This sampling rate for f d up to 22 MHz is appropriate.>LVAL66Z Z   B Bɢ * rc#*0Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola5.3.6.1TR15.1 is *not* orthogonal FSK. The modulation iLine 3 claims 2Mb/s is included; line 7 claims it is not. Which is it?The first paragraph is a list (or non sentences) that needs an introductionThiLine 3 claims 2Mb/s is included; line 7 claims it is not. Which is it?The first paragraph is a list (or non sentences) that needs an introductionThis will, however, compromise the accuracy of the measurements at each channel.This paragraphs repeats the first paragraph. It should be deleted.or profile fLine 3 claims 2Mb/s is included; line 7 claims it is not. Which is it?The first paragraph is a list (or non sentences) that needs an introduction802.15.1 hops from 320 to 1600 hops/secondExtra space between "rate trends"?802.15.1 hops anywhere from 320 to 3200 hops/s depending on the packet type and the mode it is inImproper capitalization of "master" and "slave"802.15.1 hops from 320 to 3200 hops/second.Line 3 claims 2Mb/s is included; line 7 claims it is not. Which is it?The first paragraph is a list (or non sentences) that needs an introductionThis will, however, compromise the accuracy of the measurements at each channel.This paragraphs repeats the first paragraph. It should be deleted.or profile for BER (Bit Error Rate).don't all packets have access codes and headers? ""These packets (during connection) contain at least an access code and a header.""any time slot or odd time slots? in ""any receiving time slot (i.e., each odd time slot)""you state ""failure to synchronize the access code (or access code correlator fails)"" in line 13. In 21 you only use ""if the access code correlator fails,"". Does line 21 have an incomplete list?(usually a bit map standing for conditions of different channels) will be used to compile a final list of goodNote that, when bad channels are used, packets are dropped and have to be retransmitted, which yields large delays.the values in ""error rate is ~ 24% for DM5 and DM3, and 19% for and DM1 packets,"" are not supported in figure 48LVALL|T`DX/XX/ :?(X/P( "Jr*Jz"Jr@h @p@h"Jr*Jz"Jr            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 `  gpNB@  8 8 8  "8 's J8   r8  h#s8 s 8  8 0ss8 s # 8 #s *8  sJ8 H #z8 s  8 $s 8   8 `yH8  s  "8  h$sJ8 s @r8  8 !ss8 s $8 $s Main X" )X:C@c_sc_pg_ln  ` h p x @ h           @  p      @ h   @h @p@h 8 s 8  s8 "8 sPJ8 s sr8  P8 Ps8 s 8  s8  8 s P*8 s sJ8  P z8 Ps 8 s 8  s8 y8 sP"8 s sJ8  Pr8 Ps8 s 8  s8 Main    " J r      * J z     "  J( r0 8 @ H@h @p@h )$ 8XPPPPPPPPPPPPPPPPPPP(!ONMdLkK?J;JHI:H5GVFECBAV@"0Myles, Andrewa$?@H@ AndH@H@w.myl"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco011.123 & 7TR@ P ClarifyAUl@!0ed_noteX>:lo"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco11.2213EWhat is a ""project""? ClarifyXOlP$ \?@H@ AndH@H@w.myj"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco011.1149TR@ ClarifyRUv@   X>:=?@H@ AndH@H@w.myi"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco011.1149TR,@@ORU@std_vs_rp  X>: ??@D@ AndD@ndrew.myh"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco011.1149E@ PAdd introduction to listXW   X>:YA"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco00TR@S.@OXOlP$ n"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.2.47319E@ P@OXOh* ߿k"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.2.3739Eremove ""(say 0.55)""XOh* ߟj"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.2721T(@XOh* ߟ]""0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.1.27130-31EH@P or BER (Bit Error Rate)profileXOh* ߿!"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.1.27120T@PXOh* ߟB@@ickinsky, alanachick`"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.1.27119T@PXO^>:ߟ l@@ickinsky, alanachick_"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.1.27121T@PXO^>:ߟ @@ickinsky, alanachick^"0chickinsky, alanachickinsky@northropgrumman.com70363383008554northropgrumman1212.1.1.1716-8E2@XO^>:ߟ LVAL ~ ~~ @ vtDFWfcnGreat research, information and proposals. Good job.Table 24 shows PCF reacting to denied TX requests by waiting a PIFS time before resuming operation. I don't understand if this is an additional PIFS time, or a PIFS instead of a SIFS, or something else. I read this to mean thGreat research, information and proposals. Good job.Table 24 shows PCF reacting to denied TX requests by waiting a PIFS time before resuming operation. I don't understand if this is an additionalGreat research, information and proposals. Good job.Table 24 shows PCF reacting to denied TX requests by waiting a PIFS time before resuming operation. I don't understand if this is an additional PIFS time, or a PIFS instead of a SIFS, or something else. I read this to mean that the PCF is unaffected by a denial of a TX request.Table 19 appears to swap ""None"" and ""Receive"" in the ""in-band"" and ""out-of-band"" locations of ""receive"" vs ""receive"".There is insufficient information in the beacon element to determine the start of the WPAN interval. The value of T1 is required and does not explicitly appear. There is a mention of shared knowledge of T1, but I can't see how.To the best of my knowledge, a recommended practice is not permitted to directly make changes to a standard. A new beacon element for 802.11 violates my assumption. The description of AFH later in the document attempts to modify 802.15, which is also beyond the license of a recommended practice.""meter"" is spelt ""metre"", even in US English!0.5 metres appears arbitrary; on what basis is this distance chosen?The draft consists of a number of ideas supported by detailed simulations. Most of the ideas will never be implemented in practice (particularly the collaborative mechanisms and the mechanisms that require communictations between entities) and it is not even clear that the simulations are valid given their limited scope|LVALNPPPPPPPPPPP8h/p&"KX"`0LX" 0LX" 0LX" 0LX" 0LX" 0LX" 0LX" 0LX"  0LX"  0LX"  LX"  $LX"  $LX" $0LX" 0LX" 0LX" KX" KX" KX" KX" KX" KX" 0LX" z '.'X" Ph#x###0#h####H# $ $ ($( 8$` H$ X$ h$!x$@!$x!$!$!$ "$ P    0 dh  d d H    (  `  d  !@!x!!! d "`&'''' '('0'8'@'H'P'X'`'h'p'x''''''''P0hH( `   !@!x!!! "X"Main'CommentID(v +*ۄ0))q))))))))))))))))))))))))))))- Pp-,(/(Main0L( 0L( 0L(  0L(  L(  K(+$8+P,p+`,+p, +,,, d+ 8+ dp+ d+ +, d@ @ d@ d@ @ 0L) 0L) 0L) 0L) L) K)p-,-.-... P.../0          ./X"!NdM9L,KJHG2F.FDCC-B>A=@"0Thrasher, Jerrythrasher@lexmark.com859-825-4056Lexmark International Inc44.3.1, 4.3.28-9E@Vd@OXOhhP( ߻`0John, Kowalskikowalskj@sharplabs.com(360) 817 7520Sharp Labs1010.2.45021TRr@VRemove AWMA.XOllP$߿0John, Kowalskikowalskj@sharplabs.com(360) 817 7520Sharp Labs1010.2.2.64729TR@V@OXOllP$߿0John, Kowalskikowalskj@sharplabs.com(360) 817 7520Sharp Labs1010.1411TRp@V@OXOllP$߿"0Thrasher, Jerrythrasher@lexmark.com859-825-4056Lexmark International Inc11.2221EIEEE 802.119 WLAN802.11b-1999XOhhP( ߿0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies00Ej@ STE-Refuse complimentXOTE-Refuse compliment hP 0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies1010.3.55511TR0@S@ OWill investigate furtherXWWill investigate further8hP 0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies1010.3.15112E@SZ@ OTE-??XOTE-??hP g0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies1010.2.34849TR@S@ OWill consider furtherXWWill consider further/  hP 0Spiess, GaryGary.Spiess@Intermec.com319 369 3580319 310 4425Intermec Technologies1010.2.2.6.14733TRT@S@ OTE-??XOhP &"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco33.1.6327E""data"" should be ""Data""FixXOlP$ ?@les, Andrewandrew.myo"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco033.1.4323Eb@SFixXOX>: ?@H@ AndH@H@H@n"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco033.1.4323TR@SZ@ORU@-X>: %?@I@ AndI@I@w.mym"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco011.2220E"""802.119"" should be ""802.11""FixAC ACCEPT. 222X>: PLVAL $Ǹv|TWPAN ...(WPAN should be sub-scripted). The combined duration of these two subintervals must equal... (must is a depricaTWPAN ...(WPAN should be sub-scripted). The combined duration of these two subintervals must equal... (must is aTWPAN ...(WPAN should be sub-scripted). The combined duration of these two subintervals must equal... (must is a depricated IEEE word)The two MAC layer techniques both involve.... (reword)Table 19 Receive-Receive in-band entry should be Receive collision, while out-of-band entry should be None entry.Currently superframe is periodic and we have to define its boundary with respect to some reference signal (i.e. CLK).The result in figure 21 is quite counter-intuitive when compared with the PER in figure 20.802.15-2001 should be 802.15-2002Reference {Blue99} not clear/correct.Figure 1--- (remove/fix the long dash) applies throughout document.Subtitle for 4.3.1 and 4.3.2 Non-Collaborative and Collaborative ""proposals""Here's another deficiency with AWMA: the use of a CTS would only silence the medium for 3.2767ms. Thus it would be effectively unusable to signal the end of a WLAN period, assuming a beacon interval of approximately 100ms, unless one wanted to limit the 802.15.1 system to use less than 3% of the available time.To expand on other comments about AWMA, in this clause, a change is required to 802.11, beyond, I believe the PAR of 802.15.2. Furthermore this change would have to be dealt with in light of changes being made now in 802.11h, 802.11e, and 802.11i.AWMA will not work for legacy stations, will not provide QoS support for 802.11e, and will interfere with timers for legacy equipment. It may also have problems with overlapping BSSs.The minimum number of frequencies permitted by the FCC is something on the order of 72 or 76 hops of the total 80 available. Does eliminating 3 to 7 hops do much to enhance cooperation between technologies? The importance of the AFH technique is not apparent.!OMM.LAKJ I#FED)C:ߛ |?@rasher, Jerrythrashe"0Thrasher, Jerrythrasher@lexmark.com859-825-4056Lexmark International Inc1212.17018E\@ZXO\>:ߟ <?@rasher, Jerrythrashe"0Thrasher, Jerrythrasher@lexmark.com859-825-4056Lexmark International Inc1111.3.1697Ez@) ...policy leads to a delay...?XO"""" \>:߿ LVAL h X DHow 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.AWMA is recommended for high density WLAN/WPAN area. As such there will be 3 non-overlapping WLANs in the same area.. For AWMA to be effective,How is T1 decided? Why the 1-10ms range? Is T1 to be neHow is T1 decided? Why the 1-10ms range? Is T1 to be negoHow is T1 decided? Why the 1-10ms range? Is T1 to be negotiated by the devices or should it be the same within BSS?The period time ... should be changed toThere are very few explicit ""recommendation"" sections. (An exception would be section 10.1.) That being the case, should all statements in the document be taken as recommendations? For example, in section 5.4.3 it says ""This result is not surprising, since the CCK provides a higher bit rate but occupies the same 22 MHz bandwidth, thereby having less of a coding gain. Generally, the receivers used for both 1 Mbit/s and 11 Mbit/s are fairly simple, and improved performance can most likely be obtained using more sophisticated signal processing. This fact is especially true for the 11 Mbit/s CCK system."" Is it, then, a recommendation from IEEE that improved signal processing be used in 11 Mbps 802.11 DS devices in order to reduce their sensitivity to interference from 802.15.1 devices?Several figures(43, 45) refer to Bluetooth throughput, rather than 802.15.1.""The foundation for the effectiveness of these types of methods is to be able to figure out the current channel conditions accurately and timely."" Does this mean ""in a timely manner?""The curve for scenario 3 may need some more explanation. It is clear that at short distances the 802.15.1 voice connection is causing severe interference to the WLAN, blocking packets, and increasing latency. However, why would this peak at 1.5 m? Why isn't the effect worse at 0.5m and 1.0m?Fix ""specifications cite{Bluet99}.""!O"N?MXLKJIHGFEDD,AB@X"0Kline, Daviddave_kline2@hp.com541-715-7607Hewlett Packard1010.458TR@_remove section 10.4XO|^^F" ߻Lars Falklars.p.falk@telia.se+4640105133+46705945555Telia Research AB1010.242TR<@_@`XOnV@Shawn Liushawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.1010.24216T@ \@XXOppDݿShawn Liushawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.55.3.6.81828Er@\Add the curve for 802.15.1.XOppDݿ\"0Wakeley, Timtim_wakeley@hp.com916-785-1619916-712-1474Hewlett Packard1010.04050TR@_H@XOv^F" "0Wakeley, Timtim_wakeley@hp.com916-785-1619916-712-1474Hewlett Packard1010.14149TR@@XOv^F" "0Wakeley, Timtim_wakeley@hp.com916-785-1619916-712-1474Hewlett Packard1010.14146TRz@"@ XOv^F" i"0Wakeley, Timtim_wakeley@hp.com916-785-1619916-712-1474Hewlett Packard1010.1422TR$@^B@ XOv^F" g"0Wakeley, Timtim_wakeley@hp.com916-785-1619916-712-1474Hewlett Packard1010.4588TR @remove section 10.4XOv^F" Shawn Liushawnliu@inprocomm.com+886-3-5165106 ext 865 InProComm, Inc.33.1.1441EP@\The period of time & TE-AgreeXO TE-AgreeppDfBobby Josebobby@ieee.org916 9618977916 9618977NA11.1147TR|@ @XXOxtpnhfbL6"0Chinitz, LeighLChinitz@Proxim.Com781-772-1317240-460-3257Proxim00T\@^@ XXO|dL& "0Chinitz, LeighLChinitz@Proxim.Com781-772-1317240-460-3257Proxim00E@@\N@ XXO|dL& "0Chinitz, LeighLChinitz@Proxim.Com781-772-1317240-460-3257Proxim1111.1.26343E@\Z@ XXO|dL& "0Chinitz, LeighLChinitz@Proxim.Com781-772-1317240-460-3257Proxim1111.06136Ex@\B@ XXO|dL& a"0Chinitz, LeighLChinitz@Proxim.Com781-772-1317240-460-3257Proxim99.13618TN@\f@ XXO|dL& "0Chinitz, LeighLChinitz@Proxim.Com781-772-1317240-460-3257Proxim99.03311E@1 Change references to 802.15.1.XO|dL&  LVAL | B @ AWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.Deterministic spectral excision is a poor recommended practice. 1. WLAN devices still interfere with WPAN deviced 2. WPAN devices still interference with other WLAN devicesAWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.Deterministic spectral excision is a poor recommended practice. 1. WLAN devices still interfere with WPAN deAWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.In all of the coexistence simulation modeling, for example in section 9, there are many figures showing the effect on throughput and delay of various interference scenarios. In section 10, though, which discusses collaborative mitigation techniques there does not appear to be any discussion of the effect that these techniques will have on throughput. For example, AWMA in its simplest implementation would allow 50% of the time for WLAN transmissions, and 50% of the time for 802.11 transmissions. This should reduce the effective throAWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created. LVAL 8 ʮ B @ .  Presumably the recommended practice is more restrictive than just ""IEEE 802.11 WLANS""; it should be 802.11 WLANS operating in 2.4GHz bandsfhop is claimed to be a frequency and yet the definition seems top refer to channel numbers. Is is a frequency or a channel number?The document contains too much ""why"" (with very detailed supporting equations and simulations) rather than a concise statement of the problem and a recommended solution (or solutions)""In a communication system, extraneous"" should be ""Extraneous""Deterministic spectral excision is a poor recommended practiPresumably the recommended practice is more restrictive than just ""IEEE 802.11 WLANS""; it should be 802.11 WLANS operating in 2.4GHz bandsfhop is claimed to be a frequency and yet the definition seems top refer to channel numbers. Is is a frequency or a channel number?The document contains too much ""why"" (with very detailed supporting equations and simulations) rather than a coPresumably the recommended practice is more restrictive than just ""IEEE 802.11 WLANS""; it should be 802.11 WLANS operating in 2.4Presumably the recommended practice is more restrictive than just ""IEEE 802.11 WLANS""; it should be 802.11 WLANS operating in 2.4GHz bandsThe document contains too much ""why"" (with very detailed supporting equations and simulations) rather than a concise statement of the problem and a recommended solution (or solutions)""In a communication system, extraneous"" should be ""Extraneous""It is not clear to me how the collaborative methods in 10.2 and 10.3 will work in a QoS enhanced 802.11 environment. Since it is likely that the collaborative methods will be implemented at the same time as the 802.11 QoS enhancements more than the 802.11 legacy case should be treated.PTA can only work if the WPAN device also uses apative frequency hopping to avoid interfering with other WLANs in the same location.LVAL 2 P@'8.  It is not possible to change, or add to the 802.11 MAC fromIt is not possible to change, or add to the 802.11 MAC from this document (I believe). Redefine this coexistence mechanism to use the existing MAC and define any new functionality separately. Maybe it is OK to say that implementations following the recommended practice have a view of the internal state of the 802.11 MAC? Even if MLME additions are allowed, there is no need for new primitives. This interface would be better done using MLME-GET/SET on the new MIB attributes defined (with the addition that it would be nice to have a capability MIB attribute too).This coexistence mechanism seems to be very confused. Either remove it, or rewrite it to be (a) self-consistent and (b) consistent with a recommended practice. Does it use a side channel, or new elements for parameter communication? Are the parameteters set by the AP in an infrastructure BSS? Are they set by the STA that starts an IBSS? Do other IBSS STAs inherit the values when they join?I don t believe that modifications to the 802.11 MAC are permitted within the scope of a 802.15 recommended practice. Therefore, either this has to be a new 802.11 standard, or the functionality has to be built on top of the existing MAC without modification (like 802.11 TGh has). Maybe it would be possible to still have this coexistence mechanism by assuming that implementations following the recommended practice have a view of the internal state of the MAC but surely new elements, primitives and the like are out. Even if this view is not the case, there does seem to be new on-air signalling!Consider dividing the document into a recommended practice body and informative simulation/analysis annexes.Remove AWMA recommended practice.Remove the recommended practice of using spectral excision for PHY layer coexistence.At the very least remove all the ""why"" to an appendixClarify how the collaborative methods in 10.2 and 10.3 will work in an 802.11 QoS enhanced environment."LVAL2N  tiࡱ> <2QlC  6 )   +!ORoot EntryPcPi&VBANSp,o-VBAProject NSХm-VBANSХm-7   , 6# %m 57&k2  t1B?3$<89(@B-DVGHIJKLMPQRSTUXWlYZ[]^_`abcdefghijm nqrsuvz{}~Root Entryi&VBANSp,o-VBAProject NSХm-VBANSХm-YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE:PROJECTPROJECTwmaAcessVBAData 7   6# m 547%&k2  t1?$B;89(=>C-ENGHIJKLMPO\QRSTUXYZ[]p^_`abcdefghijm qxy|DirData*PropDataReports(NS*U_0Figure 38: This diagram makes no distinction between present collisions versus future collisions the way that Figure 37 does. What should happen when the 802.15.1 logic makes a Tx Request but the 802.11 is already transmitting?!NML`KnJlI~HGFEDCBAA5@w"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine44.1626TV@dv@`XO|znPP" 3"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine11.1221EL@1FixXO|znPP" 1"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine11.127E@dRemove editor s noteXO|znPP" VK Jonesvkjones@woodsidenet.com650.475.1915650.475.1915Woodside Networks1010.24212TR@dB@`XOt\DvVK Jonesvkjones@woodsidenet.com650.475.1915650.475.1915Woodside Networks1010.45810TR@d@`XOt\D"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco1010.2.45028TRl@ ClarifyXOlP$ {"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco1010.2.450TR@d ClarifyXOlP$ u"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco1010.2.3505TR@dFixXOlP$ "0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco44.1.2738E^@dFixXOlP$ "0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco44.1623TR@_FixXOlP$ "0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco44.064E"".."" should be "".""FixXOlP$ "0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco33.3549TR@ ClarifyXOlP$ ?@les, Andrewandrew.my"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco033.1.11345E!""fading"" should be ""Fading""FixXO     X>: "0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco00TRr@_n@`XOlP$ ?@les, Andrewandrew.my"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco033.1.8336E@_FixXOX>: ?@les, Andrewandrew.my"0Myles, Andrewandrew.myles@cisco.com+61 2 84461010+61 418 656587Cisco033.1.7331E""It is a"" should be ""A""FixXOX>: <LVALAWMA has dramatic impact on the proposed 802.11e. Since 802.11e may be approved prior to the approval of this recommended practice, the impact on QoS operation should be addressed.LVAL $ $> Z8@'80Ibzd"0Th"0Kline, Daviddave_kline2@hp.com541-715-7607Hewlett Packard1010.458TRThis document would be easier for a new reader if the analytical work that is the background to the actual recommended practice was moved to an annex (this applies to sections 5 throuThis document would be easier for a newThis document would be easier for a new reader if the analytical work that is the background to the actual recommended practice was moved to an annex (this applies to sections 5 through 8).This high-rate PHY is often referred to as IEEE802.11b. It is not  often referred to but was  standardized as IEEE802.11b!This introductory clause says that the scope of this document is limited to DCF and does not address PCF. However, Table 24 in 10.3.5 addresses how PTA functions for PCF.Remove editor s note referring to 2Mbps. 2Mbps is part of 802.11b and therefore this not is incorrect.How is AWMA coordinated with probable enhancements of fair-queuing in WLAN, such as HCF and EDCF, where time division of the beacon interval is used for QOS reasons. Have the mechanisms of HCF been studied when used in conjunction with AWMA?Using a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will work if the interference location is static through the entire 802.11b packet (which it is not since it hops 160 times in 100ms). Otherwise, changing the location of the notch filter as the 802.15.1 interference hops will create what looks like a time-varying channel response to the 802.11b packet. This type of channel behavior would necessitate the use of an advanced equalization method.The clause does not make clear in what period the CTS is transmitted. If it is sent in the WLAN period there will be cases in which it would not be sent at all. If it is sent in the WPAN period the 802.15.1 master had better know about itThe equations do not cover all cases, eg when RTS/CTS is sent before a packet/ACK""to in increase"" should be ""to an increase"" LVAL N  ࡱ> <2QlC  6 )   +!ORoot EntryPc{j&VBANSp,o-VBAProject NSХm-VBANSХm-7   , 6# %m 57&k2  t1B?3$<89(@B-DVGHIJKLMPQRSTUXWlYZ[]^_`abcdefghijm nqrsuvz{}~Root Entryoj&VBANSp,o-VBAProject NSХm-VBANSХm-YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE:PROJECTPROJECTwmaAcessVBAData 7   6# m 547%&k2  t1?$B;89(=>C-ENGHIJKLMPO\QRSTUXYZ[]p^_`abcdefghijm qxy|DirData*PropDataReports(NS*U_This Document gives details on 802.11B interference while current standardization in 2.4 GHz Band is covered in 802.11G Annex. The new modulation methods mentioned in 11G needs to be taken into consideration in the analysis on mutual interference and in proposed solutions.!NMLL@KeJIHGF(FcECDPC8B_A2@l"0Kandala, Srinivassrini@sharplabs.com(360) 817-7512(360) 907-7318Sharp Laboratories of America, Inc.1010.3.555TR@k@hXOnR, | Leo Montebanmonteban@agere.com+31 3060 97526Agere Systems1010.2.45021T@iB@hXO~z``D ݿ Leo Montebanmonteban@agere.com+31 3060 97526Agere Systems1010.2.2.6.14740TT1 is essential information.Add T1 as extra field.XO~z``D ݿm Leo Montebanmonteban@agere.com+31 3060 97526Agere Systems1010.2.2.14345T@gAdd T1 as parameter.XO~z``D ݿ?@ Montebanmonteban@agMonteban, Leomonteban@agere.com+31 3060 97526Agere Systems1010.24247Tj@gExpress T1 in TUXOxT::ݿ n Leo Montebanmonteban@agere.com+31 3060 97526Agere Systems00T@i@hXO~~~|z``D ݹo Leo Montebanmonteban@agere.com+31 3060 97526Agere Systems00TR@iz@hXO~~~|z``D ݹxRichard van Neevannee@woodsidenet.com+31-346259650Woodside Networks1010.45810TR@ir@hXOjjP$ݿqJonathan Edneyjon.edney@ntlworld.com+44 1954 2057391010.04028TRD@iH@hXO|xplllN"5Allen Tsaiallen@inprocomm.com+886-3-5165106 ext 870InProComm, Inc.33.1.2316-17E@g@hXOll@ݿr"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine1010.2.45023TR@i@hXO~znPP" t"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine1010.2.35017TR@gz@hXO~znPP" s"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine1010.2.2.14340TR@gl@`XO~znPP" t"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine1010.2.24330TR^@g@`XO~znPP" u"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine1010.04028TR@g@`XO~znPP" ?@ack, Simonsimon@moti"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine055.0936Ez@ d@`XOV>: 4?@ack, Simonsimon@moti"0Black, Simonsimon@motix.demon.co.uk+44 7780 677453Qosine044.1636E@ dUse  standardized .XOV>: LVAL , ~<'80IbShows IEEE 802.15.1 (Draft 1, July 2001 Sponsor Ballot).Text currently reads IEEE 802.119T1 is also required in order to do an accurate calculation of the two periods.T1 could possibly be better expressed in 802.11 TU's.The definition of coexistence seems to (partly) overlap with interoperability. Do we want to strictly divide between the two?Firstly see comments from this author on appropriate scope for an 802.15 recommended practice. Second the 802.11 MAC behaviour around the start and end of the WPAN interval needs to be more precisely defined, for example, do STAs that defer due to a pending WPAN period select a backoff value, increment their retry counters, etc..New 802.11 MLME primitives are outside the scope of this recommended practice. If it is possible to specify this coexistence mechanism without change to the 802.11 MAC then this MIB should be defined as an 802.15.2 MIB.Timing values to be distributed through the WLAN network management tool (i.e. outside the scope of this recommended practice). This implies that the element defined is not actually required and that some 802.15.2 MIB is being set by a higher layer protocol. If that is the case why define the element at all (which is outside the scope of a 802.15 recommended practice). I also note that (a) these need to get into STAs before active scanning to avoid getting management frames sent in the WPAN period, and (b) some description of IBSS operation is required. No new on-air signalling is required . However, a new information element for beacon and probe response management frames is defined. Sounds like new on-air signalling. This together with new MLME primitives and MIB extensions seems to be defining extensions to the 802.11 MAC. Given this is the case I don t see how this can be a recommended practice since it is defining new protocol elements and modifying the behaviour of the 802.11 MAC - it has to become a new 802.11 standard surely.LVAL D D X Z  <hFhcoordinate the order number with other task groups, 11e, 11i, 11hTake this section out or ask more results to backup its performance: 2,5.5, 11mbps, with equalizercoordinate the order number with other task groups, 11e, 11i, 11hTake this section out or ask more results to backup its performance: 2,5.5, 11mbps, with equalizer considered.Change the hopping sequence in the MAC model to BT sequenceRerun simulation to extend the results to more BERs.Suggest adding multipath results in the simulated and analytical results.When the schedule for this LB allows, AFH section should be harmonized with Bluetooth SIG.Depending on the progress/schedule of this LB, it may be possible to incorporate changes to harmonize with Bluetooth SIG. If it becomes feasible to do so, changes are recommended. Replace with IEEE 802.15.1 Standard (and appropriate date)add sensing function in .15.1 master.remove collaborative proposals; focus on non-collaborative proposals.Work with 802.11 group to make that addition.Clarify. If my understanding is correct, remove this restriction.Add this shortcoming to the text.Include a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.Include analysis and simulation material addressing the 802.15 and 802.11G coexistance. Include outcome of those analysis and simulation in proposed schemes for interference reduction.Remove the recommended practice of using notch filtering.State clearly whether interoperability is included in coexistence or not.Remove this mechanism as no such facility exists and it overloads the CTS functionality.If I'm incorrect about it being inappropriate for this 802.15 recommended practice to add to, or modify the 802.11 MAC, then specify explicitly the MAC behaviour around the WPAN period, including back-off, IFSs used and retry counter behaviour. See the behaviour of the .11 MAC around dwell boundaries for an example.FLVAL zzz`The proposed control of legacy systems will not work when a legacy device is operating in power save mode and wakes up to transmit a packet.The document lacks a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.The document only addresses 802.11B interference while current standardization in the 2.4 GHz band is covered in the 802.11G annex. The new modulation schemes proposed in The proposed control of legacy systems will not work when a legacy device is operating in power save mode and wakes up to transmit a packThe proposed control of legacy systems will not work when a legacy device is operating in power save mode and wakes up to transmit a packet.The recommended practice to use a notch filter has the problem that 802.15.1 signals are frequency hopping; this means that the 802.11b receiver woulThe proposed control of legacy systems will not work when a legacy device is operating in power save mode and wakes up to transmit a packet.The recommended practice to use a notch filter has the problem that 802.15.1 signals are frequency hopping; this means that the 802.11b receiver would have to change its notch and equalizer if a hop occurs within a packet. It is not clear whether this is possible without fatal transient effects that would kill the 802.11b packet.The 802.11 MAC does not allow the transmission of a CTS frame in isolation with a specific duration value. This frame exchange sequence and duration setting facility simply do not exist in the current 802.11 MAC. This is one reason why in the IEEE802.11 TGh draft we have defined a new quiet period mechanism (an aside is that even if it did exist the duration is limited to 32Kus). Note that (a) even if this CTS mechanism existed it would be imperfect and (b) the group addressing scheme to involve other APs violates the current rules further. This latter point is due to the fact that CTS is not used in multicast communication.TLVALdN  ࡱ> w<*QlC  6 )   +!ORoot Entryj&VBANSp,o-VBAProject NSХm-VBANSХm-7   , 6# %m 57&k2  t1B?3$<89(@B-DVGHIJKLMPQRSTUXWlYZ[]^_`abcdefghijm nqrsuvz{}~Root Entry j&VBANSp,o-VBAProject NSХm-VBANSХm-YXXBWhile this document does reasonable job of characterizing interference potential between 802.11 FH and 802.11b WLANs and 802.15.1 (Bluetooth) WPANs and proposing some methods of improving coexistence, I think it falls short of what is currently needed in the following respects: First, it will be obsolete in short order because it does not address the proposed 802.11g extension at all. Second, neither does it address 802.15.3 WPANs. Third, neither does it address 802.15.4 WPANs. Finally, while it offers a definition of "coexistence," that definition is very "fuzzy" and essentially ignores the pressing need to quantify just what constitutes acceptable coexistence between systems and what does not. What is needed is a "figure of merit" or "measure of goodness" that defines both how much a system is affected by other systems and how much it affects them, and that should apply to ALL 802 wireless standards that operate in a given band, not just a subset.&LVAL P  lZL It would be nice to have the OPNET MAC model as appendix.It would be nice to have source code for the PHY coexistence model as AppendixTake out Section 10.4: the method is only shown effective for 802.11b 1Mbit/s mode. The impact of equalizer is unknown. Cost of implementing an 802.15.1 receiver to just get the hoppingIt would be nice to have the OPNET MAC model as appendix.It would be nice to have source code for the PHY coexistence model as AppendixTake out Section 10.4: the method is only shown effective for 802.11b 1Mbit/s mode. The impact of equalizer is unknown. Cost of implementing an 802.15.1 receiver to just get the hopping sequence and timing is expensive and hardly feasible due to cost consideration.Should use BT hopping sequence instead of random sequence in MAC OpNet modelSome of the simulation curves only cover BER down to somewhere between 10-2 and 10-3. Should use BER of at lease 10-4 as the threshold for more useful results, because a BER of 10-2 to 10-3 will yield too high a Packet error rate for pactical usage.Need to consider the impact of equalizer for the coexistence PHY model simulation.Section 12 (Adaptive Frequency Hopping) needs to be harmonized with Bluetooth Coexistence group work when schedules from both groups allow.Section 11.2 (Packet Scheduling for Improving SCO Links) needs to be harmonized with Bluetooth 1.x Speech Improvement when schedules from both groups allow.Since there is no sensing in .15.1 master, how can the proposed collaborative proposal to prevent the .15 device sending in WLAN subintervals?As the recommendation suggests additions of the Information elements, this needs to be added into 802.11 standard so that non-802.15.2 devices can still be conformantTable 24, third column (PCF(as CF-pollable STA)): This condition here seems rather artificial. If a STA gets a poll and has a WLAN MPDU to send, would it be still denied access? Am I not understanding this correctly?,!NN-MHL{KJIIOHGFE#END7CHBGA^@ HungKun Chenhkchen@inprocomm.com+886-3-5165106 ext 661InProComm, Inc.55.3.313T@m@oXOttH ݻ HungKun Chenhkchen@inprocomm.com+886-3-5165106 ext 661InProComm, Inc.55.3.313T@mCorrect this sentence.XOttH ݻAlbert Youngayoung@ralinktech.com408-725-8070 x 31Ralink Technology1010.2.2.6.348TD@m@oXOjjHݻAlbert Youngayoung@ralinktech.com408-725-8070 x 31Ralink Technology1010.2.2.6.1 Beacon frame format47TD@m@hXOjjHݻA"0Jie, Liangjliang@ieee.org2144804105Texas Instruments0000ET@mCorrect the typos.XO|zzzvrPP< ߹y"0Jie, Liangjliang@ieee.org2144804105Texas Instruments0000Er@ kAdd if possible.XO|zzzvrPP< ߹"0Jie, Liangjliang@ieee.org2144804105Texas Instruments0000E@ kAdd if possible.XO|zzzvrPP< ߹"0Jie, Liangjliang@ieee.org2144804105Texas Instruments1010.458T@ k@hXO~vrPP< ߻"0Jie, Liangjliang@ieee.org2144804105Texas Instruments06T@kv@hXOxvvvvrPP< ߸'"0Jie, Liangjliang@ieee.org2144804105Texas Instruments0000T@kh@hXO|zzzvrPP< ߹"0Jie, Liangjliang@ieee.org2144804105Texas Instruments055.3 & 5.411-28T@k@hXOvrPP< ߻}"0Jie, Liangjliang@ieee.org2144804105Texas Instruments1212.069T@k@hXO~vrPP< ߻"0Jie, Liangjliang@ieee.org2144804105Texas Instruments1111.264T8@kf@ hXO~vrPP< ߻7Denis Kuwaharadenis.kuwahara@boeing.com425-957-5366Boeing22.0248Ep@gv@ hXOzxllT"ݿ6Denis Kuwaharadenis.kuwahara@boeing.com425-957-5366Boeing11.2221EB@gChange to IEEE 802.11bXOzxllT"ݿ"0Xu, Shugongsxu@sharplabs.com360-834-8672Sharp Labs of America0000TR@kJ@ hXOZZB ߹k"0Xu, Shugongsxu@sharplabs.com360-834-8672Sharp Labs of America0000TR@k@ hXOZZB ߹z"0Kandala, Srinivassrini@sharplabs.com(360) 817-7512(360) 907-7318Sharp Laboratories of America, Inc.1010.242TRL@kZ@ hXOnR, LVAL h$$Ϡ V  The use of a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will likely not bThe use of a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will likely not be effective, since the interference location is not static through the entire 802.11b packet (hops 160 times in 100ms). Changing the location of the notch filter aThe use of a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will likely not be effective, since the interference location is not static through the entire 802.11b packet (hops 160 times in 100ms). ChThe use of a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will likely not be effective, since the interference location is not static through the entire 802.11b packet (hops 160 times in 100ms). Changing the location of the notch filter as the 802.15.1 interference hops creates what appears to be a time-varying channel response to the 802.11b packet. This type of channel behavior necessitates the use of an advanced equalization method.TGg is describing mechanisms to enable coexistence between legacy .11b devices and .11g capable devices. Have the performance impacts and increased complexity of these mechanisms been modeled when used in conjunction with PTA?TGg is describing mechanisms to enable coexistence between legacy .11b devices and .11g capable devices. Have the performance impacts and increased complexity of these mechanisms been modeled when used in conjunction with AWMA. A mechanism needs to be defined regarding the prioritization of 802.15, 802.11b legacy and 802.11g.There should be no difference betweem spectrum factors of Barker mode and CCK mode in Table 4.The definition of frequency offset in Table 3 should be clarified.order 11 is already defined in 11eorder 11 is already defined in 11elines after figure number, i.e. figure 34-p LVAL N  tiࡱ> w<*QlC  6 )   +!ORoot EntryBk&VBANSp,o-VBAProject NSХm-VBANSХm-7   , 6# %m 57&k2  t1B?3$<89(@B-DVGHIJKLMPQRSTUXWlYZ[]^_`abcdefghijm nqrsuvz{}~Root Entry+Uk&VBANSp,o-VBAProject NSХm-VBANSХm-YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE:PROJECTPROJECTwmaAcessVBAData 7   6# m 547%&k2  t1?$B;89(=>C-ENGHIJKLMPO\QRSTUXYZ[]p^_`abcdefghijm qxy|DirDataThe document only addresses 802.11B interference while current standardization in the 2.4 GHz band is covered in the 802.11G annex. The new modulation schemes proposed in 11G need to be taken into account in the analysis on mutual interference and in proposed solutions. Any new development in this band is likely to address 802.11G rather than just 11B. Any investment in collaborative schemes must have applicability for 11G to be of interest.xLVAL|||*2B  < "HĮMove the two sentences "The WBAN ... minus the WPAN interval." to be after the figure as is the convention for the rest of the 802.11 information elements.possible correction: ""but also the adjecent channels, the 22 channels that are susceptible could be incrMove the two sentences "The WBAN ... minus the WPAN interval." to be after the figure as is the convention for the rest of the 8Move the two sentences "The WBAN ... minus the WPAN interval." to be after the figure as is the convention for the rest of the 802.11 information elements.I believe the correct reference should be 802.11b.The rates supported needs to be consistantly stated in the doc. I suggest that you Remove the Editor's note:Correct the ""This introduction is not part of the IEEE std xx-200x, title"" statement.Correct the formatting of the page.Have one or more technical editors review and fix the text. Watch out especially for number mismatches ("one item are..."), "effect" when "affect" is meant, and typos in table fields. Aside: Is a "Recommended Practice" a *Standard*?Change title word "Other" to 802.11-1999Remove the recomended practice of spectral excision.Remove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.Provide a mechanism that addresses co-existence in PCF and HCFRemove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.Remove AWMA recommended practice.Expand the scope of this set of recommended practices to include .11g now, rather than waiting for some future revision.Remove the recommended practice of using spectral excision for PHY layer coexistenceRemove PTA recommended practice for now.Remove AWMA recommended practice for now.coordinate the order number with other task groups, 11e, 11i, 11hK[                     .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   D Although not part of the standard, the comment that the Intro is not part of the standard should be complete and correct.Although not part of the standard, the comment that the Intro is not part of the standard should be complete and correct.This document is a yeoman technical effort, but needs a thorough editorial review and fixes.It appears to me that the AWMA technique can be easily extended to PCF/HCF.It is not clear from the text if PTA is another technique or part of AWMA. Both of them appear to have the requirement of WLAN/802.11 and WPAN/802.15.1 are collocated. Also, is there a reason to distinguish between WLAN and 802.11 as well as WPAN and 802.15.1It is not clear how the spectrum factor values have been derived. An informative reference would be useful to the reader.Given that a modification of PCF (called HCF) would most certainly exist in the future, I think the co-existence mechanism should cover that as wellIEEE 802.11b is mis-spelled as 802.119This draft is for a recommended practice, not a (supplementary) standard. However, I find that it changes many MAC operations at least from the 802.11 perspective. For example, AWMA in Clause 10.2 modifies the 802.11 MAC to time share with 802.15.1. The operations to handle the legacy (?) 802.11 stations as described in Clause 10.2.4 are not also compliant with 802.11-1999.TGg is describing mechanisms to enable coexistence between legacy .11b devices and .11g capable devices. These need to be taken into account in regards to the AWMA recommended practice or the recommended practice needs to be removed.Given that TGg has made significant progress and is likely to be finished soon, it makes much more sense to expand the scope of this document now to include the issues associated with coexistance between 802.15 devices and 802.11g devices. It is highly likely that most if not all future products in the 2.4 GHz WLAN space will be incorporating .11g it is practically irrelevant to speak to coexistence with .11b only devices.!NMLK+KlJIH!HVGFEDCBA*AK@"0Oakes, Ivanifo@tality.com+44 1223 421 025-Tality (UK) Ltd00011Eh@Set up boomarks!XO|^\< Maarten Hoebenmhoeben@intersil.com+31-30-2296083Intersil1010.3T@@@}XOzvffJ"ݹMaarten Hoebenmhoeben@intersil.com+31-30-2296083Intersil0000E^@{~@}XO~~~zvffJ"ݹ"0Hayes, Vicvichayes@agere.com+31 30 609 7528+31 30 609 7498Agere Systems1010.2.14336T@@!Replace ""shall"" by ""should""XO~`B "0Hayes, Vicvichayes@agere.com+31 30 609 7528+31 30 609 7498Agere Systems033.1.2316T@@}XO~`B ["0Hayes, Vicvichayes@agere.com+31 30 609 7528+31 30 609 7498Agere Systems000010E@@8@}XO~`B Tim Godfreytgodfrey@intersil.com913-664-2544Intersil0000El@{@}XOxvvvrn^^FݹDave Halaszdhala@cisco.com330-664-7389Cisco Systems, Inc.1010.241-50TR@{F@}XO|xRR:ݻ["0Rosdahl, Jonjrosdahl@ieee.org801-617-2508Micro Linear041.4815E`@{@oXO~xt\\D" ߿Z"0Rosdahl, Jonjrosdahl@ieee.org801-617-2508Micro Linear012221EF@ ;d@oXO|zxt\\D" ߿Y"0Rosdahl, Jonjrosdahl@ieee.org801-617-2508Micro Linear01127T@{@oXO~|zxt\\D" ߿"0Rosdahl, Jonjrosdahl@ieee.org801-617-2508Micro Linear00E@ y@oXOzxxxxt\\D" ߸F"0Rosdahl, Jonjrosdahl@ieee.org801-617-2508Micro Linear00ED@{F@oXOzxxxxt\\D" ߸EDavid Hunterhunter@timefactor.com 805 687 2885 TimeFactor0000E@ y@ oXO|xbbHݹ]David Hunterhunter@timefactor.com 805 687 2885 TimeFactor0000I1+E@ 1P@ oXO|xbbHݿ^James Gardnerjamesgardner@woodsidenet.comWoodside Networks1010.458TR@{h@ oXO~zXXX ͻ_Ritter, Bennobenno.ritter@philips.com408-474-5116408-768-2411Philips0000TR@{p@ oXOhP Z?@H@a, SH@H@H@"0Kandala, Srinivassrini@sharplabs.com(360) 817-7512(360) 907-7318Sharp Laboratories of America, Inc.1010.242TR@y Make it so.AU@MMMA?==$`>:=hLVAL  FRu(jk"0Kandala, SriThe Bookmarks in the PDF do not makeThe Bookmarks in the PDF do not make any sense.The bookmarks in the PDF file are incorrectly extracted from the main document. They do not include the headings or subheadings oThe Bookmarks in the PDF do not make any sense.The bookmarks in the PDF file are incorrectly extracted from the main document. They do The Bookmarks in the PDF do not make any sense.The bookmarks in the PDF file are incorrectly extracted from the main document. They do not include the headings or subheadings of the document, but rather portions of the body text.AWMA will have limited benefit in the presence of overlapping cell. This is because BSS are not coordinated in an ESS. However, clause 10.1 page 41 line 51 recommends using AWMA when there is a high density of users.Initial Page nees to be checked. When I printed mine, the ""Committe of the IEEE Society"" , "" Abstract:"" and ""Keywords "" were floating in amoungst the text.Spectral excision is a sub-optimal method of removing the effects of WPAN devices on WLAN devices. If a device is required to have both WPAN and WLAN receivers, an optimal receiver would make joint decisions given information from both detectors, i.e. searching the entire receive space given knowledge about the two waveforms. Furthermore, if spectral excision is used, more advanced equalization techniques will need to be used in the WLAN reciever at the hop-boundaries due to the time-variation required on the nulling filter. Using a joint detector will obviate the need for a nulling filter or an equalizer.This draft is for a recommended practice, not a (supplementary) standard. However, I find that it changes many MAC operations at least from the 802.11 perspective. For example, AWMA in Clause 10.2 modifies the 802.11 MAC to time share with 802.15.1. The operations to handle the legacy (?) 802.11 stations as described in Clause 10.2.4 are not also compliant with 802.11-1999.4LVALDN  ࡱ> w<*QlC  6 )   +!ORoot EntryP\k&VBANSp,o-VBAProject NSХm-VBANSХm-7   , 6# %m 57&k2  t1B?3$<89(@B-DVGHIJKLMPQRSTUXWlYZ[]^_`abcdefghijm nqrsuvz{}~Root Entrypk&VBANSp,o-VBAProject NSХm-VBANSХm-YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE:PROJECTPROJECTwmaAcessVBAData 7   6# m 547%&k2  t1?$B;89(=>C-ENGHIJKLMPO\QRSTUXYZ[]p^_`abcdefghijm qxy|DirData*PropDataReports(NS*U_0(Extra space in "transmitter. This knowledge" and "layer solution. This" Actually, there is too much space at the end of all of the sentences in 10.4, most likely due to pasting from Word. Also 10.4.1, page 59 line 41.LVAL" l ,  ` (FLrRemove editor's note (all of line 7).Change "802.11" to "802.11b" [multiple places] ***also in: (subclause,page,line) 4.1,6,23 4.2,8,28 4.4,9,28 5.4.4,28,32 6.2,30,5 9.,34,5 10.1,41,10 10.1,41,25 10.2,42,1Remove editor's note (all of line 7).Change "802.11" to "802.11b" [multiple places] ***also in: (subclause,page,line) 4.1,6,23 4.2,8,28 4.4,9,28 5.4.4,28,32 6.2,30,5 9.,34,5 10.1,41,10 10.1,41,25 10.2,42,12 10.2.4,50,20 10.2.4,50,22 10.2.4,50,24 10.2.4,50,25 10.3.2,52,7 10.3.2,52,24 11.,61,26 11.,61,28 11.,61,33Remove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.Remove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.It may be desirable to have a method to synchonise the WLAN intervals and so WPAN intervals to allow meaningful 802.15.1 transmissions perhaps by sychronisation of TBTT's between BSS's?remove the word ""other"" so implying that STAs may also send CTS to reserve the channel for WPLAN.Reacled ""802.119"" with ""802.11b""Replace ""project"" with ""this recommended practice""Change title to ""Coexistence of Wireles Personal Area Networks with Wireless LAN Devices Operating in 2.4GHz Unlicensed Frequency Bands.""Refer me to the text that specifies the expected behavior or add clarifying text on how to recover, possibly based on one of the scenarios I identified above.Replace bookmarks with usable list or remove them all together.Change ""working group"" into ""working groups"" and change ""this standard was completed"" into ""this standard approved for submission to Sponsor Ballot""Configure Acrobat properly - verify bookmarks before distributing next draftAWMA and clause 10.2. Leave in PTA.LVAL.H z f f  R RF w l a V K @ 5 *   REJECT. Management of the AWMA Coexistence Mechanism is being submittREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eACCEPT IN PRREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusionREJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion iREJECT. ManagemACCEPT IN PRINCIPLE. Terms 11 and 11b are used where appropriate.ACCEPT IN PRINCIPLE. Suggested remedy will be appliedACCEPT IN PRINCIPLE. To be done by IEEE editors.ACCEPT IN PRINCIPLE. To be done by IEEE 802 editorsACCEPT IN PRINCIPLE. Adding trade mark and related information as per IEEE style.ACCEPT IN PRINCIPLE. Will be done by IEEE 802 editors.ACCEPT IN PRINCIPLE. ACCEPT IN PRINCIPLE. Modify PTA paragraph to include secondACCEPT. In annex Delete clauseACCEPT IN PRINCIPLE. No data rate scaling. See text to ensure no data rate scaling is statedACCEPT IN PRINCIPLE. Clauses 7 and 8 are to be moved into an Annex(es)REJECT. Not a requirement for IEEE 802 StyleACCEPT IN PRINCIPLE. Inclusion of the last name with a reference is IEEE standard Style manual 9/2002 clause 19.ACCEPT. For space and hyphen, but third item is still open.ACCEPT IN PRINCIPLE. Terms 11 and 11b are used where appropriate.ACCEPT IN PRINCIPLE. Suggested remedy will be appliedACCEPT IN PRINCIPLE. To be done by IEEE editors.ACCEPT IN PRINCIPLE. Adding trade mark and related information as per IEEE style.ACCEPT IN PRINCIPLE. Will be done by IEEE 802 editors.ACCEPT IN PRINCIPLE. Will be done by IEEE 802 editors.REJECT. Management of the AWMA Coexistence Mechanism is being submitted for inclusion in IEEE 802.11eACCEPT IN PRINCIPLE. Many clause will be moved to informative annexes.REJECT. AWMA is not complicated. Non-collaborative will not solve the collocation issue.$LVAL Ѐ $"`J@This draft is generally well written and ready for comment.802.11 FH is not in the scope of the RP.802.11 FH is not in the scope of the RP.Editor's note is not consistent with document. 2Mbps is included in 5.3.6.3 and 5.4.3 Figure 10.It is unclear what will happen if there is more thanThis draft is generally well written and ready for comment.802.11 FH is not in the scope of the RP.802.11 FH is not in the scope of the RP.Editor's note is not This draft is generally well written and ready for comment.802.11 FH is not in the scope of the RP.802.11 FH is not in the scope of the RP.Editor's note is not consistent with document. 2Mbps is included in 5.3.6.3 and 5.4.3 Figure 10.It is unclear what will happen if there is more than one AP(or perhaps STA) reserving WPAN intervals.""allows any other Access Point"" implies that this node is an AP. I don't this is the most likely scenario. A co-loctaed STa-BT device seems more likely.scope ""limited to coexistence of IEEE Std 802.11b-1999 Wireless Local Area Net-works (WLAN) and IEEE Std 802.15.1 Wireless Personal Area Networks (WPAN)"" is inconsistent with document title ""Coexistence of Wireles Personal Area Networks with _Other_ Wireless Devices Operating in Unlicensed Frequency _Bands_.""PDF bookmarks could do with being reduced in number!It is not clear to me how the 802.11b MAC should recover if the PTA determined that the transmission is not allowed. I think, the following scenarios are possible: 1. Transmit immediately after the deny condition is revoked. 2. Schedule a new transmission attempt, as if the previous attempt didn't happen (e.g. don't regards it as a retry). 3. Consider the deny as a 'virtual' collision and schedule a new transmission attempt as a retry.The definition of coexistence is not giving a clear picture as to th