Standard Jet DBnb` Ugr@?~1y0̝cßFNj7՜]('`{6n߱eCT>3y[ $|*J|C1 f_Љ$g'DeFx -bT4.0%WN%%`Y Y DataIDdmn%YAOIndexCommentSuggestedRemedyResponse SubclauseText50 {\}eOhW{\}eOhW{\}eOhW?hI2")}RJBh9b!nK¯? fFinalReports afDBO(XդOhWkWKhDESTդOhW ClauseListcmdWEBasciiReportcmdFancyCommitteeReportLabel16cmdEditorsASCIIReportcmdSummaryReportLabel22cmd_tildereportLabel26cmd_StatusReportLabel28TypeListLabel9cmd_StatusReport_ClickcMeasurecmd_tildereport_ClickcmdEditorsASCIIReport_ClickcmdSummaryReport_ClickcmdWEBasciiReport_Click cASCIIReportb:?QN)!HcmdFancyCommitteeReport_ClickcSummaryReport  4SELECT * FROM ClauseList ; ClauseList CHECK 6WHERE ResponseStatus = "O"  NoWritten rWHERE CommentStatus In("X","D") AND ResponseStatus = "W"  NoAction 2WHERE CommentType = "TR" rFoO I nAND CommentStatus In("A","R") AND ResponseStatus = "W"  NoSig 2AND ResponseStatus = "U"  TRproblem zWHERE ((CommentType = "TR" AND ResponseStatus In ("C","Z")) ! ~OR (CommentType <> "TR" AND ResponseStatus In ("C","U","Z")) + OR (CommentType <> "TR" AND ResponseStatus = "W" AND CommentStatus In("A","R")))  Done ,Record counts complete StatusReport ,ClauseList <> "CHECK"  ALL  AND Clause In( ) 4SELECT COUNT(*) AS rcount  FROM Main  bcMeasure: horrible error, could not count records rcount Summary DPlease select from the Clause List TypeList @Please select from the Type List zChecking for records that don't match any known clause number fHoundDogging Committee report rIsNull([Clause]) OR [Clause] Not In ("00","01","02","03",, "04","05","06","22","30","30A","30B","31","31B","34","35","36","36A","36B","37","38", N"38A","38B","38C","38D","39","41","42") 4WEB Ascii report generator TPreparing to print report for all clauses 2SELECT * FROM Main WHERE  BNo Comments Match Search Criteria AND  2Ready t ջ߿W c? YX0S mm 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\alSlY 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{|}~ YwSY  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 CdXEbN   : k & W  C t / `# $ % & ' ( ) , - . / 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@:8  !ppx"(&vM @  @    @  @  @  @@@ @ @ 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+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^^++OYkfJmMWYbOQu`JYb`JYbdomfom `kvkJMMQkkdL[QMmk!`kvkJMQk`kvkY`QuMd^o`bk"`kvkY`QukfQMk#`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkidoUW$miMd``QbmQi%mvfQ^Ykm&qdmQibJ`Qk'qdmQikmJmok(JMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQOokQiOQSYbQO1m45n2o2`2 Detail6e5]`abtchbox_commente5_`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%D" !_#c$h&l'p(BCDEFGHIJKLMNPQRSTUVWXYZ[\]^_`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|>|/|0|1|2|&|'|(|3|4|5|6|7|8| |||||||||||D|)D|*D|+|| |!|"|#|$|%_|,_|-_|.c|9c|:c|;h|?h|@hlllppptttt tt tttt!t"t#t#t#t#t#t4Y0š]                        \    ! " # $ % & ' ( ) * + , - . / 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 DE`E`E`E`WKR Cx@'0%ltF@%'P%lxF`%p$ `p `p<''' , pp ,>,F p6  O , tx$,p KR Cx@'0%ltF@%'P%lxF`%p$ `p `p<''' , pp ,>,F p6  O, tx$,p KR Cx@'0%ltF@%'P%lxF`%p$ `p `p<''' , pp ,>,F p6  O, tx$,p 0 P  KRCx@'0%ltF@%'P%lxF`%p$ `p `p<''' , 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\@SxbX@SummaryInfom>T@,DDD88888886 @)g\@g\@SysRelm>.........., g\@g\@Scriptsm>0000000000. g\@g\@Reportsm>0000000000. g\@g\@Modulesm>0000000000. g\@g\@Formsm>,,,,,,,,,,*  @ @DataAccessPagesm>@@@@@@@@@@>  g\@ g\@MSysRelationshipsl@-:::......., @ g\@ g\@Relationshipsl<<<<<<<<<<<:  g\@ g\@Databasesl<44444444442  g\@ g\@Tablesl<.........., 8LU L L 1 -K ʎJ I6 2IwG51G3EYR;wsBEE4@L4@~sq_ffMainm>4MR2KeepLocal Tvvv666666 @s\@>nX@AccessLayoutm>4MR2KeepLocal Tj!6zz:::::::8 @p~Nh@zDJT|@VoterStatusm>@DDD88888886 @l@Eh@'0Np@VoterNamesm>@BBB66666664 @ yDy@y@TR Commenterm>@w@zRFF:::::::8 @ckC]@xbX@Roughm> @888,,,,,,,* @_g\@g\@MSysIMEXSpecsm><<<<<<<<<<: Dg\@ԂZ_@MSysIMEXColumnsm>@@@@@@@@@@> =s{3@gw{3@MSysAccessObjectsm>DDDDDDDDDDB ʲw@a.D@MainOutputm>@=|PBBB66666664 @JN^@ CD@Mainm>,.m|P666*******( @gb~b@:5^ @Indexm>E@}888,,,,,,,* @^*ue@f@Dispatchm>h@}>>>22222220 @yBln@ ln@0CloseEandTcommentsm>@w@z^RRFFFFFFFD @LG0f@;M@ClauseListm>@BBBB66666664 @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> @\4MR2KeepLocal Tl``````^ `y0 ۏ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$$ 8ΞA WM ] 6L L 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_cConfirmationListnnnnnnnnnnnA"B","C"-"A" "11"Jeyhan Karaoguzjeyhan@broadcom.comB- "06"John Sarallosarallo@appairent.comA* "D","E","F"James Gilbgilb@ieee.org>/#*"10"Gregg RasorGregg.Rasor@motorola.comC) "08"Jay Bainjay.bain@timedomain.com?& -----CHECK ALL "07"Allen Heberlingaheberling@xtremespectrum.comL- "10"Gregg RasorGregg.Rasor@motorola.comC) "08"Jay Bainjay.bain@timedomain.com?& "06","09"Allen Heberlingaheberling@xtremespectrum.comQ2! "00","01","02","03","04","05"James Gilbgilb@ieee.orgPA5LVAL ( @ @ @ @ @ @ @ @ @ @ @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"))) cO%sM b ( F ˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩ Y  ]Y  Y  V Y  Y  Y ] Y ]V Y 2VY  Y  ] Y  Y ConnectDatabaseDateCreateDateUpdate 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:Main :  G: : G9Main 9  G9 9 G8Main 8  G8 8 G7Rough 7  G7 7 G6Main 6  G6 6 G5Dispatch!!! 5  G5 5EMainEMainEMain E D 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 cla _YNY  Y  Y  Y d Y d Y d Y  Y d Y  Y   Y  Y  Y  Y   Y   Y  Y dY Y  Y Y Y $Y , Y CommentIDCommenterNameCommenterEmailCommenterPhoneCommenterFaxCommenterCo ClauseSubclausePageLineCommentTypeCommentSuggestedRemedyResponseCommentStatusResponseStatus TopicCreateDateLastModDateDispatchDateWrittenDate"Accept_RejectDate&Closed_UnsatisfDateVoterStatusYCommentID   /Hx  QxoX H  6XH,Xx  x X(h]4x5X(7:hXx  x XH%  x6XHX X d 5XX X 4 5X,Xx  x X:h]4x5X%:h %  7:h!Xx  x XH%  x6XHX X d 5XX X 4 5X,Xx  x X:h]4x5X:h %  X 4$  xXH0 X  0   0   0 P  0   t$ Qtx(d%t! t t Y'%'%'%:4D(T D$%t$ `t `t6TD$d  x X( xtTD$0 P  0   0   0 P  0   p$ Qpx"p'@%'P%'`%x QptP(<:`%pt p 0< D(`#$8!  8 /$)p<85( t  x X.  *#$ *# p!  p 2$ p.  *#$ *# p! x p 2$ p. *#$ *# p! X p 2$ p. *#$ *# p!  p 2$ p. *#$ *# p!  p 2$ p3<:`%p$ Tp $< )p<3<:`%p$ Tp $< )p<(`%p! p pp!  p p p! | p |p p!  p |p p!  p |p(( 6(l, xt($ p<8(0   0d:h%x$ Tx $d <)xdTx! x TDxD(h]4x!  x x x! | x |x x!  x |x x!  x |xD(h]4Fx!  x x x! | x |x x!  x |x x!  x |xD(h]4x!  x x x! | x |x x!  x |x x!  x |x8( @DxdT0 P  . l  W=   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 reFF. Kr(EA"`*DP( @! $RlLVAL|.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 LVAL6Z#ʾxxxxMainCommenter--FullCreate query in Design viewkC0Bzbmo3ZZзWF<7'OW7'Ov=B0v=dzWн=WWB0l(Create query by using wizardkC0Bzbmo3ZZзWF<7'OW7'Ov=B0v=dzWн=WWB0l(Commenter--Fullusing wizardkC0Bzbmo3ZZзWF<7'OW7'Ov=B0v=dzWн=WWB0l(rTR Commenterllusing wizardkC0Bzbmo3ZZзWF<7'OW7'Ov=B0v=dzWн=WWB0l(+_GetAllCommentsusing wizardkC0Bzbmo3ZZзWF<7'OW7'Ov=B0v=dzWн=WWB0l(CloseEandTcommentsng wizardkC0Bzbmo3ZZзWF<7'OW7'Ov=B0v=dzWн=WWB0l(fMainDispatch+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90fCommitteeReports+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90jfHoundDoggingrts+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90fMainDoggingrts+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90MfNewInputingrts+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90jMfRoughutingrts+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90MfStatus j LVALz    PopUprts+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90STARTsPopUprts+pn0 bbbn0q0DbwB e8=0 {5wj%080j%0h90j90jVoterStatus Edit Web page that already existsmCommitteeReportCommon utilities^3H*W{ͥ DmȅǞ +Nez# p! Xp 2$ p@3@@3@  Y McInnis, Michael D.michael.d.mcinnis@boeing.com435-865-2840206-290-7758The Boeing CompanyAD231TRm@*!;@( XOwiK6@3@@3@  Y McInnis, Michael D.michael.d.mcinnis@boeing.com435-865-2840206-290-7758The Boeing CompanyA229TRe@)!:@' XOwiK6@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.1111.2.3188TRA@(!9@& XOrrZB6@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.1111.2.3188TRA@'!9@% XOuu]H6U@3@@3@  Y Chen, Hung-Kunhkchen@inprocomm.com+886-3-516-5106 ext 661InProComm, Inc.1111.2.3188TRA@&!9@$ XOuu\F6@3@@3@  Y Chen, Kwang-Chengkc@inprocomm.com+886-3-5165106 ext 668InProComm, Inc.1111.2.3188TRA@%!9@# XOss[I6l@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.1111.6.52139T]@$!9@" XO{kk]H6@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.1111.4.42033E#@#!See the comment.XO{kk]H6@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.1111.4.120046E@"!See the commentXO{kk]H6>@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.1111.4.120010T4@!!6@! XO{kk]H6@3@@3@  Y Rofheart, MartinMartin@xtremespectrum.com703-269-3007240-463-3306XtremeSpectrum11TR=@ !/@ XOqcH6@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.10177TR@!:@ XOrrZB6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.10175TR@!:@ XOuu]H6o@3@@3@  Y Chen, Hung-Kunhkchen@inprocomm.com+886-3-516-5106 ext 661InProComm, Inc.10177TR@!:@ XOuu\F6o@3@@3@  Y Chen, Kwang-Chengkc@inprocomm.com+886-3-5165106 ext 668InProComm, Inc.10177TR@!:@ XOss[I6oO@3@@3@  Y Rofheart, MartinMartin@xtremespectrum.com703-269-3007240-463-3306XtremeSpectrum10TRO@!/@ XOqcH6@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.09175E8@!(@ XOrrZB6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.09175E8@!(@ XOuu]H6o  LVAL two [CTA/Isoch] Rename the SPSSetIndex parm to PSSe'PNC response' was change to 'Lines 32:34 describe an two cases of handover cThe information is not only associatThe information is not only associations and CTRB, but also PS and ACL./KOThe information is not only associations and The information is not only associations and CTRB, The information is not only associations and CTRB,The information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an The information is not only associations and CTRB, but also PS andThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe aThe information is not only associations and CTRB, but also PS and ACL./KOLiThe information is not only associations and CTRB, bThe information is not only associations and CTRB, but also PS and ACL.The information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an tThe information is not only associations and CTRB, but also PS and ACL.The information is not only associations and CTRB, but alsThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two casThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two caseThe information is not only associations and CTRB, but also PS and ACL.The information is not only associations and CTRB, but also PS and ACL./KOThe information is not only associations and CTRB, but also PS and ACL./KOThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describThe information is not only associations and CTRB, but alThe information is not only associations and CThe information is not only associations and The information is not only associations and CTRB, but also PS and AThe information is not only associations and CTRB,The information is not only associations and CTRB, but also PS and ACThe information is not only associations and CTRB, but alsoThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two cases oThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an The information is not only associations and CTRB, but also PS and ACL./KOLines 32The information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two cases oThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two cThe information is not only associations and CTRB, bThe information is not only associations The information is not only associations and CTRBThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe anThe information is not only associationThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two cases of handover cancThe information is not only associations and CTRB, but also PS anThe information is not only assocThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two casThe information is not only associations and CTRB, but also PS and ACL./KOLines 32:34 describe an two cases of handoverThe information is not only associations and CTRB, but also PS and ACL./KO M0Y΂Gwʥ/]Ƌŭ#]gLPDHdW@3@@3@  Y Huckabee, Lauralaura.huckabee@timedomain.com256.428.6422256.759.0678Time Domain Corporation00Tj@*r@ (XOtfG6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.008.2.714336TRm@*)@ (XOugH6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp00E2@*@)XO{kk]H6o@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp00E@&P@ (XO{kk]H6o@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent00E@&;@ (XO}}}}yn`RC6#@3@5@ 5@5@5@Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000Th@&@)@ ACyhWD6v@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000E>@&T@(XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000E@&@)XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000EV@&@(XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000E@&@(XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000E^@&W@(XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000048E@&K@(XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self00002E@&@(XOyhWD6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments00TR@4@(XO|xxxxtaaSC6o_@3@@3@  Y CYPHER, DAVIDdavid.cypher@nist.gov1 301 975 4855NIST00Eq@ &y@5 XOxvvvvrll\E6o^@3@@3@  Y CYPHER, DAVIDdavid.cypher@nist.gov1 301 975 4855NIST00Ef@ &@(XOxvvvvrll\E6ot@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola00multipleTR@ &K@(XOvhZB6=@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola00Abstract0EH@ &W@4 XOvhZB6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain000E]@&u@3 XOvhZA6   LVALast Change tAdd I suggest either "...alAChange piconet type codes to: 0 -> Independent or Change "SIFS"Remove this subclaremove (or possibly remove (or possibly do what it suggests!)remove (or possibly do what it suggests!)Remove this subclause and references to ASIE from remove (or possibly do what it suggests!)Remove this subclauseremove (or possibly do what it suggests!)Remove this subclremove (or possibly do what it suggests!)Remove this subclause and references to ASIE fremove (or possibly do what it suggests!)remove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the draftChange the referred entrremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from thremove (or possibly do what it suggeremove (or possibly do what it sugremove (or possibly do what it suggests!)Remove this subclause and references to ASIEremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from tremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the draftChange the referrremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the draftChange the referred enremove (or possibly do what it suremove (or possibly do what it suggests!)Remove this suremove (or possibly do what it suggests!)remove (or possibly do what it suggests!)Remove this subclause and referemove (or possibly do what it suggeremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from theremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the draftChange the referred remove (or possibly do what it suggests!)Reremove (or possibly do what it suggests!)Removremove (or possibly do what it suggests!)Remove remove (or possibly do what it suggests!)Remove this sremove (or possibly do what it suggests!remove (or possibly do what it suggestremove (or possibly do what it suggests!)Rremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the drafremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the drafremove (or possibly do what it suggests!)remove (or possibly do what it suggests!)Remove this subclause and references to ASIE fremove (or possibly do what it suggests!)Remove thremove (or possibly do what it suremove (or possibly do what it suggests!)Remove tremove (or possibly do what it suggests!)Remove this remove (or possibly do what it suremove (or possibly do what it suggests!)Remove thisremove (or possibly do what it suggests!)Remove this subclause and references tremove (or possibly do what it suggests!)Remove thisremove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the draftCremove (or possibly do what it suggests!)Remove this remove (or possibly do what it suremove (or possibly do what it suggests!)Remove tremove (or possibly do what it suggests!)Remove this remove (or possibly do what it suremove (or possibly do what it suggests!)Remove this subclause and refremove (or possibly do what it suggests!)Remove thiremove (or possibly do what it suggests!)Remove this subcremove (or possibly do what it suggests!)bP<CHECK ALL  "A","B","C","D","E","F","G"#"10" "08" "09","10"Ari SingerASinger@ntru.com?-!-Ó̳.<^Œġ 3 ;@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola011.2211E@*@,XOvhZB6:@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola011.223E Bad Grammar6@(XOvhZB6@3@@3@  Y Alfvin, Rickalfvin@appairent.com585-214-2464585-781-0952Appairent Technologies, Inc.011135Tm@*_@(XOvhZD6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America00TR@*^@(XOkk]G6o@3@@3@  Y Siwiak, Kazimierzkai.siwiak@timedomain.com954-755-6828256-990-9062Time Domain00-126EB@*use just "WPAN"XOrdI6@3@@3@  Y Siwiak, Kazimierzkai.siwiak@timedomain.com954-755-6828256-990-9062Time Domain00Et@*XOrdI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00E@*S@(XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum008.4.2.114716TR @ *Q@(XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum008.41465E/@ *@,XOugI6@3@3@  3@ Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00TR@ *!Change all values of Kus to ms.ACugI6&0@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00E@ *I@,XOugI6W@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00E@ *x@ (XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00E@*S@)XOugI6@3@3@  `3@`3@Shellhammer, Steveshell@symbol.com(631) 738-4302Symbol Technologies00TR@*@)XOll\J6of@3@@3@  Y Shellhammer, Steveshell@symbol.com(631) 738-4302Symbol Technologies00TRO@*@)XOll\J6o/@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00E@*@)XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum007.5.7.112431TR@*@)XOugI6@3@@3@  Y Kinney, Patrickpat.kinney@ieee.org724-425-7952Invensys00Eq@*"remove all references to 2.4 GHzXOzxxxxtjj\G6o;LVAL.m|PKNMR2MR2ValidationRuleValidationText FilterOrderByOrderByOnColumnWidthColumnOrderColumnHiddenDescription FormatCaptionInputMaskDefaultValueRequiredAllowZeroLengthDisplayControlDecimalPlacesOrientation$UnicodeCompressionB $ Main.CommentID 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       m8 0In ("O","W","C","U","Z")l dAllowed value for Response Statuss: O, W, 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","A","B","C","D","E","F") Allowed value for Clause: 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, A, B, C, D, E, F hVoterStatus       m bP</"N     CHECK ALL  "A","B","C","D","E","F","G"#"10" "0 "A"Allen Heberlingaheberling@xtremespectrum.comK,K[P h   ] ] ] ])Check that a type selection has been made d""h$b!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$$. Please select from the Type ListA@@| k ,Details of all comments to date, by editor ( Z)'',Ask for filename prefix(Please enter prefix for Summary report: seCreateTildeFiles_Clickc:\Comments\tildes\$j'",Make sure the user didn't hit the cancel key "aA filename prefix is required. It should include the directory pathname. Use OK to accept defaultA@@|k$$. SELECT * FROM ClauseList %&. !*a ">$ "to_ "> _$ _tilde.txt'Check to see if file exists $l  Warning: File _  exists. Overwrite file? nseCreateTildeFiles_Click$@ |dx A@pk`kXWHERE Main.Clause In( ",) AND  d""h 'H Here is where we do all the work   H ,Ak B@> B@B B@BAll tilde reports completeA@@oP <Create detailed email containing all records for each editor]`x]]]])Check that a type selection has been made d""h$b Please select from the Type ListA@@|@k8Ask for filename prefix,Please enter prefix for NEW records report: seGeneralReports_Click c:\mydocs\$j'",Make sure the user didn't hit the cancel key "aA filename prefix is required. It should include the directory pathname. Use OK to accept defaultA@@|kFile',Details of all comments to date, by editor ( Z)'',$$. SELECT * FROM ClauseList %&. !*a ">$ " "> _$ _readable.txt'Check to see if file exists $l  Warning: File _  exists. Overwrite file? nscGeneralReports_Click$@ | d A@pkkWHERE Main.Clause In( ",) AND  d""h 'H Here is where we do all the work    H ,AkP B@>8 B@B B@B'All general (readable) reports completeA@@o?0;Create summary email containing all records for each editor]p]]]]()Check that a type selection has been made d""h$b Please select from the Type ListA@@|>k>Email',Summary of all comments to date, by editor ( Z)'',$$. SELECT * FROM ClauseList %&. !*a ">$ "B'WHERE Main.Clause In( ",) AND  d""h 'H Here is where we do all the work    H ,Ak@= B@>(= B@B B@BAll summary reports completeA@@o<@BCreatK[e Tilde-delimited file containing NEW records for each editor]]]] ]8$Details of NEW comments, by editor ( Z)'',Ask for filename prefix,Please enter prefix for NEW records report: snSummaryReports_Click c:\mydocs\$j'",Make sure the user didn't hit the cancel key "aA filename prefix is required. It should include the directory pathname. Use OK to accept defaultA@@|:k:$$. SELECT * FROM ClauseList %&. !*a ">$ "to_ "> _$ _tilde.txt'Check to see if file exists $l  Warning: File _  exists. Overwrite file? nscCreateTildeFiles_Click$@ |@9d89 A@pk 9k9 WHERE Main.Clause In( ",) AND Main.CommentStatus = "X" 'H Here is where we do all the work   H ,Akx8 B@>`8 B@B B@BAll Tilde reports completeA@@o8P@Create detailed email containing all NEW records for each editor]]]]0]HEmail'%Details 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 ,Ak6 B@>5 B@B  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]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 wantsclear 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 ((K["@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`yAccept_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%!K[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 Databa0\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%$yğGmģ%Thm,op_wymo`dify K[Qu zdd.Po bcXhan A`s=coderom X-->D.? !et ߨ h0is54XD!op  ؕ^ppJV<Z!ן'@, 8 * Fpt`Gw+@b(?hDEST.gJ @4XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.2157TRh@5Need clarification.XO}xtaaSC6r@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.21448E@ 5Wording issue.XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments05Figure 11441T@ 5,@4XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.11427TR@ 5 ClarifyXO}xtaaSC6o@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0531423Eh@ 5Make a bullet itemXO~zxtaaSC6n@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0531413EH@ 5Order appropriatelyXO~zxtaaSC6m@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments051.21342EF@5Clarify point.XO}xtaaSC6l@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments05.1.21342E8@5?@4XO~xtaaSC6k@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments05.1.11333E@5(@4XO~xtaaSC6j@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0511316E3@5+@4XO~zxtaaSC6I@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.5.61722E Bad GrammarP@4XOvhZB6C@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.3.4151820E#@5(@ 4XOvhZB6B@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.3.31512EBad grammar.:@ 4XOvhZB6K["  ( v8  @  L tp  H  @! P!p! x! !! 6!! \! tP" "t" P# `# p# ## # H# # $$ $ ($ 8$ "@$ (H$p$*$$$$%xp!Check for existence of input file d"L"N$l%New input datafile not found.A@@|hk` PRough import with tildesRough 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@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", "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@ProceeK[d 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 corresponding 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)Mr̈˱ 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%p%P% 3IsNull(Clause) OR Clause Not In ("00", "01", "02", "03", "04", "05", )"06", "07", "08", "09", "10", "11", "A", "B", "C", "D", "E", "F")'p%Attribute VB_Name = "Form_fInput" Bas0{033FE3A9-FEEC-11D0-8168-444553(540} |GlobalSpacFalse dCreatablTru Pre declaId"Expose_TemplateDerivCustomizD$Option Comp@ D3T  co nvert@to \130 TILDEM ~, aM"StatusBClaufieldszcupper c`/^IBOpen(Cal As IntegeroM@| Chief gets .see all tons; editors don'cGetOwnerq(G!s#GI NNYUbpIeVo/]x.EnaeGr?.WhichEqDtusG_1xAssignIDxDim dlbs2qbrst, IndexRecordseSet= CurrentDba9Selecm8r#k`BmID=0this quer y isos n@}es (E .I(WuSELECT "{.,eeb-``hLastMod FROMC cWHERE ((( )=0))j;b'a[i'hoha s{#,#bmE$ =n"8" number $%m6=4%"B$Save÷!value `N G !} we h`tba@out>t@`F.Ew ![Ǧ ]`9' ]g.uDo Un@R.EOFc'AdFdO% IDCcu( Cp![Rz l![X [/ 2![-  vaPq ] Movedfp ? " @i9] + 1uLoop.Clo_8lA?ID' d* c $2v03(JPodA"BaGgKOn ErrGoTo_Uick#1MstDocaLrStngc`CBr`wria1OmwK2OATypeuu?qk?PdbP-a]'f2`stIsNull(R(espxe) OR + Not In (""O"""WcSc CcUcZ"")_xia2`*"T/H8XsDcAcRY WR TEcTSS70001t2rl& "K[""034t5r67t8t9s11nBTF)=^11"" &3vqS-o/\ @ (cIsBlank(stm ) tp(dbs*Ma`M~q1Q9!j?!Q $I,  #;Q1U`0wcsqtbadcop,aqrqtHs, Rp}sWwN|o X?2XJpI{0la/(~"+CaÔ" #"F) Then  DoCmd.OpenForm stDocName, stTCriteria MsgBox ("se records contain ba"datu$des,2mment typor clau:num@bers")`ElsenNo B [Ro 4nd I f6E rst.CloPdbExit_cmd`Check))_Click:? Sub 8Err.DescriptioResume :3]8Private@ T etIndexQ"(Dimp As _et db Databa~ argDe faultInteger O n ,@dGoTo9M&Set = CurrsDb A@Y =’F"("+",@QDyn"t- IffEOFȥkAddNew[q AEdi60=!NextCoBIDB % Input("Last saved value of  wa s " &OldF". Pl e/ >er a newfN 4: <_Ð"M@odify C TableG3@D9![].GCAUpdLnW4!.fF`qchange to )r ^ aJ=4^oughImportG^ 'Bv .exist(encb9i!= fLilK(p_F ([s]![NfAE]),"";# `.a  notund^.ǃ%Z(c("ProceM#refrom k ?@4a7C2 !'e "ad?!!'A0 assign ID $_ @ AID sastamps eS"> c;$ /RA%$R!J i)BJ p3s!mplete:Qexdbsϭh `sNvs'this query o s theire J` Witho Until.`WI.Uq='Fiq preserve" Gs aXvokpZ} -m whe@ y 91# cPQ s (O1.M'Now! Bi9$R e&All 2 3o} tP`Transfer$3%'c Str@?yXrM`(рRLLtQ! " :0iL//_-?_-;c ?("b `Udb=Do Wh` (N\#0(/`.G`Z rw4that mat@JCc$!#= "SELECT * FROMCWHERE (![L" h*& s !7" );"SE(" ϘadA2'r8e4wfop0eT irAn  Dd!7Dbߓ0p1'0G@51?Rdger?1<erE2lpTPhoneFaxpq_UCoO@`?r`LCGqPag:^Li^2T tb?t] SuggedRemedy9ppons6o Гn t_esR- = RRough![ResponseStatu s] rMain![Top8ic]@NCreateD X*bLastMod 2 3Dispa8tch 4 5Written 4 Accept_RejectClosed_Unsatisf !Voter .Up>dĉ7'Move to next record in .Delete N Lo0op D db.D MsgBox ("AllDs mergeAA table") End SubPriv3 Function cPreserv s(Dim @db As [axbas,DRA9set queryStringASet= Curre`ntDb(&'Partial u@xPfi-P4with U@t CommI@D (we'@Bfi@[the @p of :lh_!#$(Not ( .EOF)) Then'AND i6wm@ n;\o4utFj,d@#from m cbDNOTE -- EDMAIL sends us@ NULL , b@Hauto:m cdBb import I am plannA focbverjslwaTpdmAmCc a#cIsBko 5ǿ$%&+* i i  - G x M i'  q / ook]o?e# 'Now fix up vAn s⇐9desDq&IsNullf opR?4;QU1'BBoPZfiel4a;bA-;9y29 3Ca \cvOne3HOnly(db,t0HEli5'%mSaluJ`Ba1I@%%R9Yf uIf!%U{Qqx! y0{ cmdClear2T1}_Clicktxstxv:{xQr^d("",!`D4yntp~o Until\stb\zG0Ս. < IcUBAfred11Reaabe'Check 1Yexisc`bfdp]) .paFile([Forms]![fIn0])0!""kqf New-Q Akound.a Exit! #ACmd.TkferTacpimtfb`=v1T & , Tru0 'A f՟Dmod@ule "concSPpSpecCharancD8Lnw`hite Āhas beenHripped Ć@In0qt} \1300kTILDE~, and㳼RCla@PGcu0r c,A#G6C56?077S&WhichlG"  bnod]'\ < <(5*`.) ;? !V12 +]cs/ s/ rd/ *? f_F8PRs(ct `)lchFҰ&ub8 MyY9F P1r :OEdit Call cUpdateVoterStatusOneRecordOnly(K[db, rsMain)0.l $MoveNext Wend  VClos@e db.MsgBox ("Iv sw u complete"p End Sub Priv +Dim`Names As rseXSet = VOpen("SELECT * `FROM \* WHERE.Commen%`""" _4&3![ ]H;", dbHDynaYIf (rsC.EOF@) Then5'E n no t fouin0table; add the AddNew1=7G'check to see ifs(already exists *%B\Do+nnD oC.FvOnEo[o pqrrNgrs"s 'piG; fi@outWvڧGN ;![&]@TMY"ccoD _ ] |Ifʌc%aEl!a#_H "8 H%0IsNulllj")k assuming,Bmfield is`nn-blank, look'[A [o$$'[5d\ʓ& s\\a!-\cmd():gcol@umn ofΛ doe1tA/%bAaiد*D)UIExitgbda]0;Q]_=KX=f|? ?;DataFile_Afv!(Pq'Ceforsence inpPQ'p([Forms]![fI1])22g?(p$ГaQu.S$ qp([Forms]![fI1])22g?(p$`aQu>.S$ q _summary.txt'7Back to you, chief -- summary of all comments to date ( Z) from $<' 'H',Ask for filename*Please enter filename for Summary report: scSummaryReports_Click $j',Make sure the user didn't hit, 5 ?R+xME(@ <:@ ;XOugI6i@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.5.4174E&@ <#@;XOugI6h@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.5.31648E4@ <add "or MTS"XOugI6g@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.3.11435E2@<@;XOugI6f@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.5.21642ED@<6@;XOugI6K[ % @x  P % p % D   %  , C% F  P % p %x`P ( Xx    1= B   (8 X`h 8p  & 8P p  ( ,  @@ P` :h     0B 8@P p     B   ( 0H `x  R   B  (08  0@ p       (P8   B      ( 0Pp x      ( @ H B PX` h x      0 P X `        B  2  ( 8 @ H  P ` h p x       "  P : X 6`   $   ,  ( *0  ` h p  2x   @      4 X h :p       B      <  ,`  B K[  0 80XX@  R ,(Xpx  B     >8 Xhpx *n8   V0 <   B ( H X >`  8  >  B  ( 0HPX `p x B  P  V ` p    B  P  @VP      B   (P8  ^    (  8 HXB `hp xP  ^ H Xhp x    xp]@]`$$. Rough ( %&. 5*aC@.1 Scrub out extra spaces; convert and 6$:6$: 6$: Force status codes to upper case6$$:p6G!:j26$$:.6G!:j 6$$:6G!:j !Force clause number to upper case% ![Clause] = UCase(cScrub(![Clause]))9Force null value to GLOBAL so Chief will see this comment6$b00: k4Force single-digit clause number to use leading zero 6609LT06:nkC@<C@>q B@B B@BJi] $ $ '' $ ' $ '   $' ~$' ' $bG 'j G 'ji] ' $bGzj  Gzj $bGzj  Gzj  '      $        $'ki]h]]*Set a default in case nothing else happens $bGzj  Gzj $bGzj  Gzj Default value ' ' '  '      $        $'    'X 'iH]](@' '  $bGzj  Gzj'  $ $   $'' k  $     $'' k0 $    $QLVAL=|PaNMR2MR2OrderByOnOrientationColumnWidthColumnOrderColumnHiddenRequiredAllowZeroLengthDisplayControl$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","A","B","C","D","E","F") Allowed value for Clause: 00, 01, 02, 03, 04, 05, 06, 07, 08, 09, 10, 11, A, B, C, D, E, F hVoterStatus      m bP</"N      CHECK ALL  "A","B","C","D","E","F","G"#"10" "08"  "B","C"Ari SingerASinger@ntru.com=+q LVAL   " , MR2ValidationRuleValidationText FilterOrderByOrderByOnColumnWidthColumnOrderColumnHiddenDescription FormatInputMaskCaptionDefaultValueRequiredAllowZeroLengthDisplayControlDecimalPlacesG 2 *ClauseList.ClauseList]ClauseList       mU Editor 4      mS Email       m^ Owner    Yes/No   j^ Chief    Yes/No   jeNoWritten      0   mcNoAction      0   m] NoSig      0   meTRproblem      0   m[Done      0   m                                                                                                                                             !"#$%& '!(")#*$+%,&-'.(/)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:;<=>?@ABCDEFGHI./1234578:;<>?JKLMNOpqrstuvIJKLOPRSUVWXZ[QXRYSZT[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%FEeLVALuNR;wsB @s\@MKM@AccessLayoutm>4MR2KeepLocal.DG(( @M?`(P F &NvN8`8!&NvN d  d  d         )ClauseList.ClauseListClauseList!ClauseList.EditorClauseList.EmailClauseList.OwnerClauseList.Chief'ClauseList.NoWritten%ClauseList.NoActionClauseList.NoSig'ClauseList.TRproblemClauseList.Done   ( Xݨ @ X+ @я&@я N@я" Hv@я"@я @яH" @яH@яN@я"     @  HX;M@A~sq_cfFinalReports~sq_cClauseList     8  `      (  0   88 8`8 @я "@я&@я"PN@я" "v@я P@яP "@я " @я "@я%N@я" PClauseList     &  N  v  (  0  8  @  NH 8`8  X8`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 x8 0H 0H 0H H H H H H H H  z H`ӏPXhx0h d dP d0hP( (08P0hHClauseListhv hPq P  ClauseListhhHK[ d"f"h ORDER BY Main.Clause, %Main.Subclause, Main.Page, Main.Line; ( %&.d8Ready to print Clause(s) d"f", rCommittee Report By Clause$@ tG|j$$.  *, SELECT * FROM Main WHERE Main.Clause In( d"f",) AND  d"f"h :ORDER BY Main.Clause, Main.Subclause, Main.Page, Main.Line; ( %&.k X Restricted ^ !*a $v B@>`V XGenerale ^ !*a $x B@> V XTildee@Output records as a Tilde-delimited ASCII-readable database file !*No recrods to process B@B B@B|0 k(  SELECT * FROM MainOutput; %&.\clear all entries in MainOutput \!*a \B@z \B@> GTransfer records to the new table, applying cUnScrub to all memo fields !*a \B@| "~ \)~ " \) " \) " \) " \) " \) " \) " \) " \) " \) " \) "$ \) "$ \) "$ \) " \) " \) " \) " \) " \) " \) " \) " \) " \) " \) \B@<%Move to next record in Main recordset B@>0 \B@B,TransferText the new table to an output file MainOutput Export with Tildes MainOutput ^ BB@d /Error in module cASCIIReport. Invalid argument.A@@kP B@B B@Breport completeA@@| Z !A@@|oCommittee reportATo&General purpose summary-report writer.]P]h]+Check that a clause selection has been made d"f",$b"Please select from the Clause ListA@@|k)Check that a type selection has been made d"f"h$b Please select from the Type ListA@@|PkH d"f",CHECK=Checking for records that don't match any known clause numberA@@|k d"f",ALL*Preparing to print report for all clausesA@@!Check to see if any records exist$$.  "$SELECT * FROM Main WHERE d"f"h; %&. !*  F d"f"h BB@Dd!No Comments Match Search CriteriaA@@kd  SELECT * FROM Main WHERE " AND  d"f"h; %&. !*     F " AND  d"f"h BB@Dd!No Comments Match Search CriteriaA@@kk B@B B@B|`kXReady to print Clause(s) d"f", rSummary Report$@ tG|j!Check to see if any records exist$$.  "$   & SELECT * FROM Main WHERE d"f"h AND  [Clause] In ( d"f",); %&. !*   F d"f"h AND  [Clause] In ( d"f",) BB@Dd!No Comments Match Search CriteriaA@@khd`   * SELECT * FROM Main WHERE " AND  d"f"h AND  [Clause] In ( d"f",); %&. !*    F " AND  d"f"h AND K[ [Clause] In ( d"f",) BB@Dd !No Comments Match Search CriteriaA@@kk B@B B@Bo` x    Committee report F4IsNull([Clause]) OR [Clause] Not In ("00","01","02",5"03","04","05","06","07","08","09","10","11","A","B","C","D","E","F","G") BB@D Committee report F4IsNull([Clause]) OR [Clause] Not In ("00","01","02",I"03","04","05","06","07","08","09","10","11","A","B","C","D","E","F","G") BB@DZAttribute VB_Name = "Form_fFinalReports"D Bas0{576B9BA7-014B-11D1-8168-444553540} |GlobalSpacAIFalse dCreatablTru PredeclaId"Expose_Templat@eDerivCustomizD$Option Comp@ DT  "CHECK") Then*y .EQCJf diffeAR measure"sD 1. podnsNneVbe writtEiWHERE 8ResB Ã"O8"" P0No&WcM(d:bH,@ '2.ady !Wcomm$e acQ [m`A$In(""X"@",""D"'ANDWAb (k3m er sign-offTyp""TR!%S+e& "A) 1i5Sign4. HYitem - TR unsatisfied/PNU6TRpro`m_G*A'5. Idon`aM((d/5 5p.In PC2ZP) "T:OR A@ !\ ezAc!M) 'ID'0I.Upd@ϡ End@!a MoveNex fLoop '```d of uahl'PqlWClu db.MsgB ox` counts`0vete"=Q 1DoCmdc "3qa@acView0~v`, , \Rri]T w wFunH/Tv, arg* uuvoc addtial[ ybnpnu 2 kseb bALLjJ4* 0R_V@M$|] & s)h#)|~COUNT(*SS r :Main Q p ";$&B|v(E: hor0error,uld nVS r%*00x!# 4u0%'ñ!Mtild/7qcASCII0("T AB-g-Aors h_ [Gene(ralvȪSu`mmary/ c (" <Z'@G . WEpcibi COktricted !3stqexiste% ofɈ(pDataA)(*) <> +8ret(,("Warning! OHalready s. Do you wish/continue?vbODKCJ, "ejC`O2 eP 'O[re|Kill E0lC9[Forms]![fFinalCClaqL@H]8"CHECKiT@=TrecordsadoAmatch any known cB numberEDoCmd.Open "Committee}GacVie wPrev, `$IsNull([]) OR a NotX ]"00"",""0Z12I&:"T03456U7891գ 1 AbBN CbDEFzGI"rjA=4t4ALL3 h%Xpar4ept[$*6aC#2se1 Se`7b>Curr`Db(jBrst`db5>et("SELECT * "f ,FROM MaWHERE & VT#Q ORDER BY .@BA.,#PageD Line;KdbODyntc3頜 (e|RyF)Cx(s)[vbYesNo@]1$`By := vbNo}2555?/5B* l(" 77$ xAND'?in. (qbEm4 R&~Restrictedj7!$V U`As 1%_U _l p4.EOFTruZA P2:#1, cConcat(08Mov eNextLoopClose1@_Go h? a , Fap  ߕ '' gas aB delipded -xabd}b1#Svst7c'NopScromo process?R ' Ryz ?7&q<@+ = sOV VU;'\ 'c r ^ ]riesS)!  Delet,*c'TranPle frome  +b:$KRtypTAc *)t!"CHECK"*F*9ing, fuÖs;don't8 any known%>number-POpenC: ^acViewPrerv, @B8]@) OR [ Not`V"00"",""0122 _8 :& "34567891 1 AbBCDEF`G"")"fEJ2e! "ALLrSpar!dpt P= CurrPWDbK cIsBlank(F8Y pYn D("SELECT * FROMoWHERE ""8R+h@F4 ;'p "!cEOF  )S*, .)X%1_ ] EpS36NoP\mnsA5Search CZia9 %;%\ &Xer AND|& oU (FaO /r//r)XkI -7SI13(("Re8ady1SEV(s) cK,)vbYesNo`\ 4 S5`M= vbNo8Ф Je}J .J1 JsJt221 '%nInmL44QO)nTP`s"P"4 4-  ??'1@P _6_rtq7WWtW W! uX%dp2ECT * FROM Main WHERE " _ & Conditionsl" ANDh[Forms]![fFinalR eportTypeList]("[Clause] In (" & ^(`& "B)";")If (Not rst.EOF) Then DoCmd.Openc , acVi@ewPrev, , iQ *FElseIMsgBox gNommentstch SearCriteria_End8 IfCcCl"odb.D A Sub A( 8 @ H  P ` h p x       "  P : X 6` ME (SLS S<N0{B16FB71B-B4F9-11D1-AF4D-00C0F0090F24}H(%H0(81= xphAttribute VB_Name = "Report_Big-Font Committee rd" Basn0{B16FB71B-B4F9-11D1-AF4D-00C0F0090F24} |Global|SpacIFalse dCreatablTru PredeclaId"Expose_TemplateDerivCustomizD$ dehikmno7eeeeeefffmOpt(ionp@ D3T  and 6$:6$: 6$: Force status codes to upper case6$$:p6G!:j26$$:.6G!:j 6$$:6G!:j !Force clause number to upper case% ![Clause] = UCase(cScrub(![Clause]))9Force null value to GLOBAL so Chief will see this comment6$b00: k4Force single-digit clause number to use leading zero 6609LT06:nkC@<C@>q B@B B@BJi] $ $ '' $ ' $ '   $' ~$' ' $bG 'j G 'ji] ' $bGzj  Gzj $bGzj  Gzj  '      $        $'ki]h]]*Set a default in case nothing else happens $bGzj  Gzj $bGzj  Gzj Default value ' ' '  '      $        $'    'X 'iH]](@' '  $bGzj  Gzj'  $ $   $'' k  $     $'' k0 $    $'Ȃ' k '  GzjiX]]' '  $bGzj  Gzj'  $ $   $'' k  $     $'' k $    $'' kP '  Gzj(i , Check for the existence of the data file dx]H "$b'lzk " 'lzk "$~'$ $'ldX "'lkHi@`J Initially designed for a recordset argument, with a current record active3 Works from within a form if you call cFixDates(Me) 0If there is n-*T̹ͪ&5@IR] @3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 32629TI@)JI@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 32622TR/@(J@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 32616TR$@'J4@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.2.1267TR$@&Jb@LXOugH60@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32319E5@%J[@LXOugH6/@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32317E:@$Jl@LXOugH6.@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32319EB@#Jy@LXOugH6-@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32315E9@"J@LXOugH6,@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32314E=@!Jo@LXOugH6+@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32314E9@ Jp@LXOugH6*@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3236EE@J@ LXOugH6)@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3235EE@Jm@ LXOugH6(@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.32237EC@Jx@ LXOugH6'@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp066.87641TR@Jb@ LXO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp066.17641TR@JM@ LXO{kk]H6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.4.19.19222T}@J@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.9.4.138934T[@Jq@LXO}yn`RC6r *5@KT_jszăʕP   )@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.63238T-@P0@OXOugH6"@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.5321TRO@PR@OXOugH6 @3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.4.23126TR1@P?@OXOugH6A@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.4.13119EN@P&@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.4.13120TRF@5Jq@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.43112TR.@4J,@OXOugH6>@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.3.2313E;@3JW@OXOugH6=@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.1.2308E4@2JI@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 82932TR6@1JT@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 82933T5@0J@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 82925T.@/JS@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.3.1288TRO@.J@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 52741T9@-J@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 52739T&@,JS@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 52737T,@+J9@LXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 52735TR;@*J@LXOugH6K[                     o CreateDate, fill it in with today6$G Z:jAlways update the LastModDate Z:%Fill out the WrittenDate if necessary6$6WKT Response has been written Z:nk+Fill out the Accept_RejectDate if necessary6$6AKRKT' Response has approved by the committee Z:nk-Fill out the Closed_UnsatisfDate if necessary6$6CKUKZKT Response has been written Z:n@k8q0o(] 8 $ $ ''6Strips out carriage returns -- useful when you need to&put a whole comment onto just one line   $' ~$'i0P]]]] $ $ ''  ----------- '& %. CommentID: 6~ CommenterName: 6 CommenterEmail: 6 CommenterPhone: 6 CommenterFax: 6 CommenterCo: 6 '(( %0;ALR] Clause: 6  Subclause: 6 Page: 6 Line: 6 CommentType: 6   Comment:  6  CommentEnd:   SuggestedRemedy:  6  RemedyEnd:    Response:  6 ResponseEnd:  '*K The restricted format is for viewing by non-editors. It includes most, but& not all, of the fields in each record & ( *'vC@.C@<qx ip (]]]] $ $ '' 7First figure out if we should force Comment Status XtoD ,6XD'0d 6'0k #Now build up the rest of the fieldsCommentStatus: 0 ResponseStatus: 6 Topic: 6 '2 %.7 CreateDate: 6 LastModDate: 6 DispatchDate: 6 WrittenDate: 6 Accept_RejectDate: 6 Closed_UnsatisfDate: 6  VoterStatus: 6 '.P The general format includes everything in the restricted format plus additional5 fields for internal date tracking and comment status $v 2 .'xq i  ]]] $ $ '' 7First figure out if we should force Comment Status XtoD ,6XD'0d( 6'0k !(CL:6 6 Type:6/ 0/6 SC: 6 #6~ '66$P$ '88These fields should match with the report: SummaryReport 6 8'4qi :$b'zk :$ 'zk Otherwise'ix]]$$. SELECT * FROM ClauseList WHERE Owner = True; %&. !*JNo Owner Found: make sure one DB owner is selected in the table ClauseListA@@ B@B B@Bzxkp ">'< B@B B@Bi8]8 ]X $$. SELECT * FROM ClauseList WHERE Owner = True; %&. !*JNo Owner Found: make sure one DB owner is selected in the table ClauseListA@@ B@B B@Bz0k( "B'@ B@B B@BiK[                     x ] ] $$. SELECT * FROM ClauseList WHERE Chief = True; %&. !*QNo Chief Editor Found: make sure one DB chief is selected in the table ClauseListA@@ B@B B@Bzk ">'D B@B B@Bi ]8 ]X $$. SELECT * FROM ClauseList WHERE Chief = True; %&. !*QNo Chief Editor Found: make sure one DB chief is selected in the table ClauseListA@@ B@B B@Bzk "B'F B@B B@BiPHAttribute VB_Name = "Common utilities" 0OptiHdpare Database`Expl@icit FHunc^cSpSpecialCharacters() Dim db AsLrstRecordseQSet)= CurrepntDb?+=A.Open1("Rough",Dynts With 6!o Un .@EOF . Ed`' Scrub out extra spaces; convert and <@TILDE>!!V[R]c!( A.![SuggestedRepmedy  Response C'Force statusYdes to upper cܛDSB AUC(. )If 5O"") Then ![!@JRLJTTypS =BR ; A#Kdclause numbbPd'N>C bE$znull valuezGLOBAL so ChiefH wi@sehrimm!9IsNUC)8E"008E_ If%Ningle-digit C`lead 0zeroC!Len'1MSelect Sg$!"0" To l"9 **!&?A# C I#.U0pdat .MoveN L`oop a B .Cloadb%Ţ (sng1kACR, asc0iiCRng "#Chr(`13) +; 0A @-1{Lc/ *T$rangSReplAll,rCRH F""~" 4 cc=A R DR fEmpty#'q 0!(sou, findubsˡA2n0Loa0*# I%Ex@a>#] #$s  nInI(1@" n <> 0w7cgLefBtn - 9_Qr1& sa Righa=#)@(n+! RC:D  ((  p(3 !6 'a default inbr noth ) elKhas|ns@#tyonqsq = #T'~D "a'+p W+n#V n= /1"#e#While "$!3#)"#c?B# '" G % - Wenzd?u`&&AWp&SsHas@q$Boo m &st0P[[as\YJYja?s%%!!!f = Fa- 10>0f9@ 0q > =Trusu^a`=Up0,*Sjb`N" tB#U"=   l5&P3( ?A1AT".,,},,U+p.0o%,x JlO M,,,,),߿j/#qGb )3, ?1,,,Е`O, , ,ce = Left(source,nX) - 1) Ha sWhitTr ueLEnd If cStripTrailing< J (False) Then Exit Function, Wend `   pDataFile(dx' Check for the existe@nce ofd . f/ dx Dim s A$s ng4If (IsNull(MF3g""V  dxEmpty0 s8Dirh' ""%zFEI oJ Sub cFixes(rst ' Initially designedBRa recordset argument, with a 0curr aov' Works from in em if you cH!tMe!WA@$3 '@Sqre is no Cre(ate-,Aql "today `cIsBla nk(![G ])}Q \C'Always u p@eLastMod![]l outWrit@necessar, ,Select Case1ResponseStatus]@"W" '  has be@wC"G A ![iGC}#'*Accept_Rej@A4N1ComAPA", "R.appHrov Zby1c2Ad![O!a!Closed_Unsatisf!!@@jC!"UZB AdO\CyEAcUnScrub(s ngABtrCR, asciiCR=r(13)4 +#0@= `"a@' Sasocarriage@turns -- useful wρne Cto8p@vaole Donto just one GD`DcReplaceA`Ǥ, h+"~5"*'!)(cCo0ncat| cted⹉'D+IntroDNameFieldp6?tr Ch~g_3 P-" &#W AID: G^ ID] F_& "$e~rmSE>mbPh0%bFaxO@CoC>of !la3?cC/"@P:Lin>e$ Typ8g%"g-&R%_Z;K(SuggedRemedy?3//@rԃ%OEclG57@WpiQImatqviewxnon-editors. Inclu mo"s`butnoѰll,fJeach^QH#EBIyCcs..E U{W` myY General!!Y, Fo`XtoD)YXTtr ernalt6XɘX3_\r_Z u(1uqu(2 @@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.26230T9@P<@O@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.26230T9@P<@OXOugH6b@3@`6@ `6@`6@ Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1.26221TJ@P0@O ACCEPT. ACugH66a@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1.26220EQ@P"Please add the appropriate xref.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1.16216T4@P;@#;XOugH6_@3@`6@ `6@`6@ Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1628T@P?@O ACCEPT. ACugH66@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1627T7@P Please change to RemoteDevAID.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 286133T[@ Pf@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.166123TRw@ P@OXOugH6[@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.12322E@ P@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.134845TRM@ Pf@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.12.24820TRW@ PU@ OXOugH6X@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.124713E@Ps@ OXOugH6W@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11461Es@P>@ OXOugH6 U@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.1.24640TM@P@ OXOPiconetShutdownugH6T@3@`6@ `6@`6@ Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.1.24640T2@P\@ O ACCEPT. ACugH66K[                    ZZ @spguawe shoulpT6 1(&!S A"X"ς`pC"DA naA'Now buip upr9' s'hc5 &RlFe7![k?9PPTopic![ <& Ս: " & ![CreateD0]xstrCR _ & "LastModLlDisppatch n (8Written 76Accept_Reject <BClosed_Unsatisf " #VoterStatus:  ' The general format includes every thing t reictedplus additional)fieldsOI d trackAand comment s,%cCo ncatG$= R(rst)+C;F&rInC E!WithFu|nc+S@ummaryA, ForceXtoD) As Str/ Dim Fi@"Line,ASecond; C@;+R, asciiH= Chr(13) +C0)  E = ""18 $R'' figure ouuf we@ shoulBoc|e A%`D&9CIf ((> = True@R( nC ]@"X"))nA/=*D@)Else #a8If`` #f/CL:la0use],aTopicn Type#! /! '![Tponse# SBCsSubC #IDwM= Left(cUnScrub4@]), 80DeC.Rc'A0#'`se@DuCch we~port: bRer$0?2qpGpIsBlank(xmBooleaJQIsNull )McAT#Exit e #G  Len(cypLeady" = $O!X 'O`rwiZ(Fa"]#  e cGetOwName^(z@xaRrdsetÍdb@aba SetF `urr`xD.b=`.Open("SELECT * FROM #OListcdTWHERE bD*;"B'! .EOF|MsgBox ("NodFound:0 mak@"ne DB o i`s selprcin&tablHr0?!*o#db. A* p!Eior1RXEEmailoa ?pLheD,"72{3Chie:f3 3Pu3 C3t0 33332 @H3F3S*744c4e 4#3.5??6  p4!H;Public4soNoNoNRoN44sÍaN3 sNNeA 4"4  8 I  ( @ H B PX` h x     (S<S<S<<N0{BFF2D379-FF46-11D0-8168-444553540000}8 @   (% "  ( "0 8  H "PX h x    " xp A@oP@ A@o0 $W' A@xkp OW't gene A@\mydk8o0 A@oAttribute VB_Name = "Form_fRough" Bas0{BFF2D379-FF46-11D0-8168-444553(540} |GlobalSpacFalse dCreatablTru Pre declaId"Expose_TemplateDerivCustomizD$Option Comp@ D3T  _qZ+rRoughq8/Oq@lCrJ+?@py ( 0 @P X "`hx " " " "   NX`px 2.   0 @ ,X     .  l P vh  t p <x   2  B X `  (h  f  (  8 H P Jp `   6  (08l h8x ` h   (8@ H F`      6  &@ h x   N   0@P`p(8HXhx   ,     2DH <     (0@ H"PXx"  ,   2 . PX  0` , JX 6  (X P (( .0`h(jp B8 .@px     ` ( 8H(X f` .h 8P0 ` .  ( 8 H  xp]@X]x]$$. <prepare to index through all entries in the ClauseList tableSELECT * FROM ClauseList ; ( %&.'for all entries in the ClauseList table !*b ",CHECK B@.K[                     prepare five different measures1. responses need to be writtenWHERE ResponseStatus = "O" '"   "$2 )02. Ready for committee action9WHERE CommentStatus In("X","D") AND ResponseStatus = "W" '"   "$2 )43. Ready for commenter sign-offWHERE CommentType = "TR" 7AND CommentStatus In("A","R") AND ResponseStatus = "W" '"   "$2 )64. Hot item - TR unsatisfiedWHERE CommentType = "TR" AND ResponseStatus = "U" '"   "$2 )8 5. Item done=WHERE ((CommentType = "TR" AND ResponseStatus In ("C","Z")) ?OR (CommentType <> "TR" AND ResponseStatus In ("C","U","Z")) SOR (CommentType <> "TR" AND ResponseStatus = "W" AND CommentStatus In("A","R"))) '"   "$2 ): B@<k B@> end of clause loop B@B B@BRecord counts completeA@@ StatusReport FClauseList <> "CHECK" BB@DoH]p]5prepare addtiional conditions based on the ClauseList ",ALL H'"d H AND Clause In( ",)'"k SELECT COUNT(*) AS rcount FROM Main  "; %&. !*1cMeasure: horrible error, could not count recordsA@@'2d "J'2 B@BkiTildeANoGeneralANoX(SummaryATo0h RestrictedANoZHThis subroutine outputs comments according to clause and type selections]](@]`]x+Check that a clause selection has been made d"f",$b"Please select from the Clause ListA@@|k)Check that a type selection has been made d"f"h$b Please select from the Type ListA@@|pkh'This subroutine creates one output file X RestrictedPlease enter output file nameWEB Ascii report generatorc:\mydocs\WEBascii.txt$j'^ XGeneralePlease enter output file nameEditor's Ascii report generatorc:\mydocs\EDITORSascii.txt$j'^ XTildeePlease enter output file nameEditor's Tilde-file generatorc:\mydocs\EDITORStilde.txt$j'^d/Error in module cASCIIReport. Invalid argument.A@@|@k8,Make sure the user didn't hit the cancel key ^6A valid filename is required. Use OK to accept defaultA@@|k"Check for existence of output file ^$l=Warning! Output file already exists. Do you wish to continue? nOutput file error$@'` `G|j Otherwise ^A@pk d"f",CHECK=Checking for records that don't match any known clause numberA@@|hk` d"f",ALL)Preparing to print report for all clausesA@@$$.   SELECT * FROM Main WHERE  d"f"h ORDER BY Main.Clause, %Main.Subclause, Main.Page, Main.Line; ( %&.d8Ready to print Clause(s) d"f", rCommittee Report By Clause$@ tG|j$$.  *, SELECT * FROM Main WHERE Main.Clause In( d"f",) AND  d"f"h :ORDER BY Main.Clause, Main.Subclause, Main.Page, Main.Line; ( %&.k X Restricted ^ !*a $v B@>`K[                     V XGenerale ^ !*a $x B@> V XTildee@Output records as a Tilde-delimited ASCII-readable database file !*No recrods to process B@B B@B|0 k(  SELECT * FROM MainOutput; %&.\clear all entries in MainOutput \!*a \B@z \B@> GTransfer records to the new table, applying cUnScrub to all memo fields !*a \B@| "~ \)~ " \) " \) " \) " \) " \) " \) " \) " \) " \) " \) "$ \) "$ \) "$ \) " \) " \) " \) " \) " \) " \) " \) " \) " \) " \) \B@<%Move to next record in Main recordset B@>0 \B@B,TransferText the new table to an output file MainOutput Export with Tildes MainOutput ^ BB@d /Error in module cASCIIReport. Invalid argument.A@@kP B@B B@Breport completeA@@| Z !A@@|oCommittee reportATo&General purpose summary-report writer.]P]h]+Check that a clause selection has been made d"f",$b"Please select from the Clause ListA@@|k)Check that a type selection has been made d"f"h$b Please select from the Type ListA@@|PkH d"f",CHECK=Checking for records that don't match any known clause numberA@@ Committee report F4IsNull([Clause]) OR [Clause] Not In ("00","01","02",)"03","04","05","06","07","A","B","C","D") BB@D"11"|k d"f",ALL*Preparing to print report for all clausesA@@!Check to see if any records exist$$.  "$SELECT * FROM Main WHERE d"f"h; %&. !*  F d"f"h BB@Dd!No Comments Match Search CriteriaA@@kd  SELECT * FROM Main WHERE " AND  d"f"h; %&. !*     F " AND  d"f"h BB@Dd!No Comments Match Search CriteriaA@@kk B@B B@B|`kXReady to print Clause(s) d"f", rSummary Report$@ tG|j!Check to see if any records exist$$.  "$   & SELECT * FROM Main WHERE d"f"h AND  [Clause] In ( d"f",); %&. !*   F d"f"h AND  [Clause] In ( d"f",) BB@Dd!No Comments Match Search CriteriaA@@khd`   * SELECT * FROM Main WHERE " AND  d"f"h AND  [Clause] In ( d"f",); %&. !*    F " AND  d"f"h AND  [Clause] In ( d"f",) BB@Dd !No Comments Match Search CriteriaA@@kk B@B B@Bo`   Committee report F4IsNull([Clause]) OR [Clause] Not In ("00","01","02",!"03","04","05","06","07","A","B","C","D") BB@Dx ZAttribute VB_Name = "Form_fFinalReports"D Bas0{576B9BA7-014B-11D1-8168-444558ʿɧȬ:^f%-@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.4.210252T@Zspecify setting for MTS.XOvhZA6,@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.4.31048T@Zs@ XXOvhZA6+@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain07figure 251051T@ZE@XXOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.7.412541T$@Z@XXOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.7.612632TR@Z@XXOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.113112Eextra words presentremove "PNC it the"XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.113112TRX@Zt@XXOvhZA6~@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America063.13, 3.145055TR&@)US@XXOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America063.1.12332E-@(Uchange to MLME-CREATE-STREAMXOkk]G6@3@6@ 6@6@ Siwiak, Kazimierzkai.siwiak@timedomain.com954-755-6828256-990-9062Time Domain066.6.9791023TR@Z!Remove the PHYPIB_Range object.@AWrdI66@3@6@ 6@6@ Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.5.3 Table 3976319Ty@'Ut@X ACCEPT. ACugI66@3@`6@ `6@`6@`6@Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.18.1661939T@&Uk@X(@ACugI6v@3@`6@ `6@`6@`6@Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.10T@%U=@XZ@ACSecurityugI6w@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.9T@$UComment via Ari Singer.XOugI6@3@`6@ `6@`6@ Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.9 Table 16423147T@#UComment via Ari Singer. ACCEPT. ACSecurityugI67@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.8 Table 1540E0@"UComment via Ari Singer.XOugI6K[                     3540} |GlobalSpacAIFalse dCreatablTru PredeclaId"Expose_Templat@eDerivCustomizD$Option Comp@ DT  "CHECK") Then*y .EQCJf diffeAR measure"sD 1. podnsNneVbe writtEiWHERE 8ResB Ã"O8"" P0No&WcM(d:bH,@ '2.ady !Wcomm$e acQ [m`A$In(""X"@",""D"'ANDWAb (k3m er sign-offTyp""TR!%S+e& "A) 1i5Sign4. HYitem - TR unsatisfied/PNU6TRpro`m_G*A'5. Idon`aM((d/5 5p.In PC2ZP) "T:OR A@ !\ ezAc!M) 'ID'0I.Upd@ϡ End@!a MoveNex fLoop '```d of uahl'PqlWClu db.MsgB ox` counts`0vete"=Q 1DoCmdc "3qa@acView0~v`, , \Rri]T w wFunH/Tv, arg* uuvoc addtial[ ybnpnu 2 kseb bALLjJ4* 0R_V@M$|] & s)h#)|~COUNT(*SS r :Main Q p ";$&B|v(E: hor0error,uld nVS r%*00x!# 4u0%'ñ!Mtild/7qcASCII0("T AB-g-Aors h_ [Gene(ralvȪSu`mmary/ c (" <Z'@G . WEpcibi COktricted !3stqexiste% ofɈ(pDataA)(*) <> +8ret(,("Warning! OHalready s. Do you wish/continue?vbODKCJ, "ejC`O2 eP 'O[re|Kill E0lC9[Forms]![fFinalCClaqL@H]8"CHECKiT@=TrecordsadoAmatch any known cB numberEDoCmd.Open "Committee}GacVie wPrev, `$IsNull([]) OR a NotX ]"00"",""0Z12I&:"T034567ABCbDC"me7E_.tB.ALL . c&c parA._pmtd$B0a>c,sQ+ Se1b9CurryDb(#dBrst`db#0B8et(f"SELECT * "f`&FROM Ma@WHERE & VTcK ORDER BY .; =A.@,#PageDLine;EDdbJDyn@tc3 (vRsF)C(s)[vbYesNo@'XdZBy := vbNow2555?/5B*`f(" 77$ AND'?l?=ne (_Ej4 PF{Restrictedj7!$T R]As 1%]U@\l p4.EOFTruWA P2:#1, cConcat(08Mov eNextLoopClose1`\G $e? a , Fap  G' das aB deliaed -uabd{bQ#S"sst7c'NopScrojo process?R ' Rw ?7&q<@+ = sOV VU;'\ 'c@r ^ ]riesќS)!  Delet,*c'Tran"Closed_Unsatisf # $VoterStatus p.Upd҃'Move to next record in ֱset.N Loo6py.6'TransferTthew tabl an oAB fileCD oCmd. acExportDe@lim, "G  with Tildes" @Fname, Tru ElsMsgBox ("Error!@modu&cA@SCIIRe. Invalid argument.")nd If9G=db?rK[                     completexit Sub@_I:A@.DescriptionE@!BPrivz cmdFancyComme2_Clic k(.Call cSummary("F >R;c, Co(ndis 'General pHurpa s-"wser. (Dim`t- As .tegertstaRTSdb@jaba9$ 'Check that a clause sel z) has been m adAIf (IsNull([Forms]![fFinalC List])`) The2 b >Ple frome  +b:$KRtypTAc *)t!"CHECK"*F*9ing, fuÖs;don't8 any known%>number-POpenC: ^acViewPrerv, @B8]@) OR [ Not`V"00"",""0122 _8 :& "34567ABCD"")"mED,e=@"ALLt,@parˁ,pt raw._ss u6oa.e if"ex2sSet `;@= CurrpTDbH cIsBlank(D5V V#k@A("SELECT * FROMlWHERE "B5r)Of=f1 ;$p A`EOF  's', N&x"1_ ] em33NopYmksa2Search CXia9 %;EY &xbr AND& oU (a|O /r//r)xhI -7SIэ13(("RpeadyQSES(|s) cK,)vbYesNoYT S5`M= vbNo8𡷖 JbJ .J1 JsJt221 '%&kInjL44QO)nTPp"P"4 4-  ??'1@P _6|rtq7WWtW@ݟWA uX%dppX& [Forms]![fFinalReportxTypeList@] _ & " AND`[Clause] In (" 'PQ)"f;")zIf (Not rst.EOF) Then DoCmd.Open , acViewPrebv, , knConditionsQzElse @MsgBoxNo Comments Match SearCr@iteria_End IfCcClodb.D Sub A 6  (08l h8x ` (S<S<S<<N0{B16FB71B-B4F9-11D1-AF4D-00C0F0090F24}8(%H xphAttribute VB_Name = "Report_Big-Font Committee rd" Basn0{B16FB71B-B4F9-11D1-AF4D-00C0F0090F24} |Global|SpacIFalse dCreatablTru PredeclaId"Expose_TemplateDerivCustomizD$Opt(ionp@ D3T  @@Change 'should' to 'shall'XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.423120T@k@OXOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.6.219746E#@{9@hXOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.2.416814EEditors Note in the text.&@hXOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola077.5.4.414518E@9@5XOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola066.3.156116E"There" instead of "These"4@$XOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola066.3.94953EN@@XOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola066.3.74311T@2@#XOzjZB6`X@`X@orm&StartUpShowDBain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.4.1112921E1@/make change as requested.XOvhZA6`X@`X@orm&StartUpShowDBain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain066.3.24.48535TN@/@"XOvhZA6`X@`X@orm&StartUpShowDBain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain066.3.24 table 298317EI@change as requestedXOvhZA6`X@`X@orm&StartUpShowDBain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain066.3.24.28427Tn@"Add a parameter as defined aboveXOvhZA6LVAL`I suggest:<CR>Draft Standard for Information technology-<CR>Telecommunications and information exchange between systems-<CR>Local and metropolitan area networks Specific requirements-<CR><CR> Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs)<CR><CR>Please make the change globally.<CR><CR>Additionally, and in terms of the LB19 CommentID: #10 rejection, I understand the PAR issue but I think this is a clear editorial issue and we have WG precedents to apply the editorial suggestion. Here are some issues to consider in this rebuttal<CR>1. The 802.15.3 PAR is incorrect and is in conflict with itself and should state the previously mentioned item in the title section i.e., "2. Assigned Project Number [P802.15.3]" or section 4 should state "...Part 15.3...". http://grouper.ieee.org/board/nescom/802-15-3.pdf<CR>2. An example is the 802.15.1 PAR which TG3 copied and is why you have the error in the first place :). When 802.15.1 got to Sponsor Ballot the PE said 15.1 was ok cuz (a) we had a corrigendum: http://ieee802.org/secmail/msg00600.html<CR>and (b) implicitly it was necessary to add the dot level based on the 15.2, 15.3, 15.4, etc. approvals. http://ieee802.org/15/par.html<CR>3. Specifically, having the 802.15.1(TM)-2002 published sets a precedent as our PAR says "Part 15..." but we are published with "Part 15.1..." http://grouper.ieee.org/board/nescom/802-15.pdf<CR><CR>Note: 802.15.4/D17 is in Sponsor Ballot with "Part 15.4..."<CR>4. If you release the 15.3 Draft to Sponsor Ballot there might be an issue and someone might object BUT I think going forward w/ the title as-is is a bad idea. For example the 3rd of the 802 five criteria "Distinct Identity" will be problematic if the IEEE titles are NOT distinct and/or inconsistent in the WPAN Standards Family: http://ieee802.org/3/rules/rules.html#P72<CR><CR>Note: I applied (Session #20) the latest edit to the 802.15.3a DRAFT PAR because of this very issue and afte LVAL m]m]m]m] m] m/m/m/m/mi] StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.423120T@%k@ )XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.6.219746E#@%9@ )XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.2.416814EEditors Note in the text.&@ )XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola077.5.4.414518E@%9@ )XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola066.3.156116E"There" instead of "These"4@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohnr careful review of other approved Alt PHY Layer Standards and their titles: http://ieee802.org/secmail/msg02824.html<CR>In terms of the next step I suggest you ask Jennifer Longman what her opinion is i.e., leave as-is, apply edit, submit a corrigendum to the 802.15.3 PAR, etc.<CR>Finally, I think just from a publishing and distribution point of view it will become confusing - make the edit. If the Editor or Chairs need to change the PAR then please do so, however, the approved IEEE Std 802.15.1-2002 states "Part 15.1" and the PAR does not. It was not an issue for RevCom and the StdBD so it should be an easy edit to apply to keep our family of standards consistent.&. 3,=CV[QC8@^XOseH6*@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.4.63239TR Missing MSC%@^XOseH6u@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.4.5329E add a comma and remove a commaC@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 82931T#@b!Should be integer with 2 octetsXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 62825TType for SyncFailureTimeout5@^XOseH6r@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.3.12813ERemove comma3@^XOseH6 @3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 32627T)@b:@^XOseH6p@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.2.1267EMissing comma,@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 22443TRI@ZC@^XOseH6n@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 22425Emissing definite article.@^XOseH6m@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 22417E&@Z&@^XOseH6l@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.1.12335E!missing commas after parametersI@^XOseH6k@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.22026E(@Z9@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.22020T'@Z&@^XOseH6c1G]sˉʝɳ'=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@ XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@@XOyhWD6$`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC044.0942Eg@{'@XOyhWD6#`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.101942EI@{&@XOyhWD6"`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.5784EI@K@hXOyhWD6!`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3664950E6@-@hXOyhWD6 `X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3564447E@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.2661819E@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.1353839EP@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3511Ed@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC022.045354ED@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC022.0322Ef@{>@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC011.1143T@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC011.1278E%@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC011.1147E<@{@ XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC0000515E]@{Z@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC000020E@;@XOyhWD6  *9@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.2.24119TRN@ bW@dXOseH6V@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.1.14041TR,@ b@.^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 1540TRUnused parameter@-^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 1540TR$@ bDEK DIK SEEDXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 1540TH@bMAC/security provide octetsXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 154013TR%@bp@,^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.7.4.23944Emissing phrase ...>@+^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.7.43931TRMissing ReasonCodeh@*^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.7.1383TR4@bG@)^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 143735T@b@@(^XOseH6@3@5@ 5@5@5@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.6.2.23632TRF@bX@'^@KACSecurityseH6wR@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.6.2.23630TR@bY@&^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 133517T Wrong wordn@%^XOseH6|@3@5@ 5@5@5@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 13358TRReference to cipher suite@$^@KACSecurityseH6w@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 133528TUnused parameters@#^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 133522TRUnused parameters@"^XOseH6 LVALВI! ] z  ,lThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support thThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support the primitives describeThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not hThe sentence "If the SAP interfaces are not exposed in an 802.15.3The sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do nThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then tThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as descriThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exThe text that introduces Figure 3 is accurate but does not reference the ISO/IEC 7498-1 : 1994(E) normative reference in Clause 2; which IThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support thThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support the primitives described in this clause."; is vague. Is the term "not exposed" going to be clear to all readers? The sc 6.1 is normative but the statement "do not have to be implemented" is informative.The sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces arThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described The sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support the primitives deThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support the primitives described in this clause."; is vague. Is the term "not exposed" going to be clear to all readers? The sc 6.1 is normative but the statement "do not have to be implemented" is informative.The text that introduces Figure 3 is accurate but does not reference the ISO/IEC 7498-1 : 1994(E) normative reference in Clause 2; whichThe sentence "If the SAP interfaces are not exposed in an 802.15.3 DEV, then these interfaces do not have to be implemented as described here. If the interfaces are exposed, then they should support the primitives described in this clause."; is vague. Is the term "not exposed" going to be clear to all readers? The sc 6.1 is normative but the statement "do not have to be implemented" is informative.'  !.>AU@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 2555TR~@b;@dXOseH6@3@4@  4@ Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 2555TRK@bAdd this figureROseH6&@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.13.1.25033E0@b;@dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 2249TR@b(@ dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.12.14754TRReference to CAP Modea@ dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.12.14753TRAdd a figure1@ dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.12.14722E add commase@ dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.9.3.14415TR@b@ dXOseH6@3@`6@ 3@`6@`6@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.9.3448TRReasonCode missingc@d3@ ACseH6v@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.9.2.24345Tquestion on command type@dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.9.1/.2/.3431TR1@bE@dXOseH6W@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 1642TR;@b&@dXOseH6@3@`6@ `6@`6@`6@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.4424TR8@bS@d@ACSecurityseH6w@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.3.14143E grammatical?@dXOseH6@3@`6@ 3@`6@`6@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.34135TR#@ b|@d@ACseH6v@3@`6@ `6@`6@`6@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.2.24122TRN@ bt@d@ACSecurityseH6w LVAL @ @ @In a series of three or more terms with a single conjunction, use a comma after each term except the last. I suggest "This standard defines the PHY and MAC specifications for high data rate wireless connectiIn a series of three or more terms with a single conjunction, use a comma after each term except the last. I suggest "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable, and moving devices within or entering a personal operating space."; adding a comma after portable. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause 4 then they should be found in the draft. Also, I submit that for "DLL" it should be "Dynamic-Link Library" not "Data Link Layer". Finally, if you want to create an acroynm or abbreviation for "Data Link Layer" use "Layer 2" or "L2".Again, change sentence to read "The area of overlapping coverage between the two piconets may vary between congruency with the parent coverage area to mostly non-overlapping."; change "congruent" to "congruency".To minimize the entries into IEEE 100, I suggest that we standardize on the definition of "interoperability". I suggest the Editor use the P802.15.2/D6 definition: "interoperable: The ability of two systems to perform a given task using a single I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globallI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hypI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.$c*`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP0813.1215TR@l@XOq]H6=`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP081321556TRm@{@XOq]H6<`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP074.4TRR@XOq]H6;`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP074TR@@XOq]H6:`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP073.2.21185051TR@ XOq]H69`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP073.2.3E@@ XOq]H68`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP00TR@2@ XOq]H67`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC077.01071E4@{I suggest "MAC frame formats"XOyhWD6LVALmI suggest: Draft Standard for Information technology- Telecommunications and information exchange between systems- Local and metropolitan area networks Specific requirements- Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs) Please make the change globally. Additionally, and in terms of the LB19 CommentID: #10 rejection, I understand the PAR issue but I think this is a clear editorial issue and we have WG precedents to apply the editorial suggestion. Here are some issues to consider in this rebuttal 1. The 802.15.3 PAR is incorrect and is in conflict with itself and should state the previously mentioned item in the title section i.e., "2. Assigned Project Number [P802.15.3]" or section 4 should state "...Part 15.3...". http://grouper.ieee.org/board/nescom/802-15-3.pdf 2. An example is the 802.15.1 PAR which TG3 copied and is why you have the error in the first place :). When 802.15.1 got to Sponsor Ballot the PE said 15.1 was ok cuz (a) we had a corrigendum: http://ieee802.org/secmail/msg00600.html and (b) implicitly it was necessary to add the dot level based on the 15.2, 15.3, 15.4, etc. approvals. http://ieee802.org/15/par.html 3. Specifically, having the 802.15.1(TM)-2002 published sets a precedent as our PAR says "Part 15..." but we are published with "Part 15.1..." http://grouper.ieee.org/board/nescom/802-15.pdf Note: 802.15.4/D17 is in Sponsor Ballot with "Part 15.4..." 4. If you release the 15.3 Draft to Sponsor Ballot there might be an issue and someone might object BUT I think going forward w/ the title as-is is a bad idea. For example the 3rd of the 802 five criteria "Distinct Identity" will be problematic if the IEEE titles are NOT distinct and/or inconsistent in the WPAN Standards Family: http://ieee802.org/3/rules/rules.html#P72 Note: I applied (Session #20) the latest edit to the 802.15.3a DRAFT PAR because of this very issue and after careful review of other approved A LVAL N  `X@`X@orm&StartUpShowDBain, Jayjay.bain@timedomain.com256 4StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822MotorolaCC.1.436627E5@%{@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.3.5.129647E@%@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.2.22851315TR@%@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.82332122EK@%@@ )XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.623151T>@%Change 'should' to 'shall'XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.423120T@&%k@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.6.219746E#@%%9@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.2.416814EEditors Note in the text.&@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola077.5.4.414518E@ %9@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola066.3.156116E"There" instead of "These"4@)XOzjZB6StartUpForm&StartUpShowDBarr, JohnJohnk.Add ChallengeResponse to Table 105 with proper Length, Value, and Descriptiolt PHY Layer Standards and their titles: http://ieee802.org/secmail/msg02824.html In terms of the next step I suggest you ask Jennifer Longman what her opinion is i.e., leave as-is, apply edit, submit a corrigendum to the 802.15.3 PAR, etc. Finally, I think just from a publishing and distribution point of view it will become confusing - make the edit. If the Editor or Chairs need to change the PAR then please do so, however, the approved IEEE Std 802.15.1-2002 states "Part 15.1" and the PAR does not. It was not an issue for RevCom and the StdBD so it should be an easy edit to apply to keep our family of standards consistent. %$+9FQ^N2`X@`X@OrderByOrderByOGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC000020E@;@XOyhWD6 @3@`6@ `6@`6@ Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.7 Table 14373554T@mComment via Ari Singer. ACCEPT. ACSecurityugI673@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.6 Table 1335140T@mComment via Ari Singer.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3 Table 12251T@m2@oXOugI67@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.1.1.1 Table 224E>@mC@oXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.9.4.4.28621TRI@mI@oXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 568433TRL@m#@oXOugI6@3@6@ 6@6@6@Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table5584TRL@m8@o@ ACugI6v@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.8.181TG@mAdd a MAC_DATA.confirmXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.7.3803439ER@m9@,hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.7.1.1806TR@m*@+hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.7.1.28015E@mRemove this sentence.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.7.1.1806E@mRemove this sentence.XOugI6@3@6@ 6@6@ Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table447752TR\@ m.@*h ACCEPT. ACugI66@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table43TR@ m3@)hXOugI6@3@6@ 6@6@ Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table4277TRj@ m,@(h ACCEPT. ACugI66 LVAL Revert back to the use of GTS when referring to time slot in super frame and CTA beingI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. The DEV shall enter SLEEP state only at the start of superframefollowing the succesful transaction of power-save-commands(s) with PI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. The DEV shall enter SLEEP state only at the start of superframefollowing the succesful transaction of power-save-commands(s) witI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. The DEV shall enI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the commeI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode inI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. The DEV shall enter SLEEP state only at the sI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. The DEV shall enter SLEEP state only at the start of superframefollowing the succesful transaction of power-save-commands(s) with PNC.A wake beacon is a beacon sent by PNC at a previously declared periodic interval at which time all the sleeping DEVs, excI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction oI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.K[, Check for the existence of the data file dx]H "$b'lzk " 'lzk "$~'$ $'ldX "'lkHi@`J Initially designed for a recordset argument, with a current record active3 Works from within a form if you call cFixDates(Me) 0If there is no CreateDate, fill it in with today6$G Z:jAlways update the LastModDate Z:%Fill out the WrittenDate if necessary6$6WKT Response has been written Z:nk+Fill out the Accept_RejectDate if necessary6$6AKRKT' Response has approved by the committee Z:nk-Fill out the Closed_UnsatisfDate if necessary6$6CKUKZKT Response has been written Z:n@k8q0o(] 8 $ $ ''6Strips out carriage returns -- useful when you need to&put a whole comment onto just one line   $' ~$'i0P]]]] $ $ ''  ----------- '& %. CommentID: 6~ CommenterName: 6 CommenterEmail: 6 CommenterPhone: 6 CommenterFax: 6 CommenterCo: 6 '(( %0;ALR] Clause: 6  Subclause: 6 Page: 6 Line: 6 CommentType: 6   Comment:  6  CommentEnd:   SuggestedRemedy:  6  RemedyEnd:    Response:  6 ResponseEnd:  '*K The restricted format is for viewing by non-editors. It includes most, but& not all, of the fields in each record & ( *'vC@.C@<qx ip (]]]] $ $ '' 7First figure out if we should force Comment Status XtoD ,6XD'0d 6'0k #Now build up the rest of the fieldsCommentStatus: 0 ResponseStatus: 6 Topic: 6 '2 %.7 CreateDate: 6 LastModDate: 6 DispatchDate: 6 WrittenDate: 6 Accept_RejectDate: 6 Closed_UnsatisfDate: 6  VoterStatus: 6 '.P The general format includes everything in the restricted format plus additional5 fields for internal date tracking and comment status $v 2 .'xq i  ]]] $ $ '' 7First figure out if we should force Comment Status XtoD ,6XD'0d( 6'0k !(CL:6 6 Type:6/ 0/6 SC: 6 #6~ '66$P$ '88These fields should match with the report: SummaryReport 6 8'4qi :$b'zk :$ 'zk Otherwise'ix]]$$. SELECT * FROM ClauseList WHERE Owner = True; %&. !*JNo Owner Found: make sure one DB owner is selected in the table ClauseListA@@ B@B B@BzK[xkp ">'< B@B B@Bi8]8 ]X $$. SELECT * FROM ClauseList WHERE Owner = True; %&. !*JNo Owner Found: make sure one DB owner is selected in the table ClauseListA@@ B@B B@Bz0k( "B'@ B@B B@Bix ] ] $$. SELECT * FROM ClauseList WHERE Chief = True; %&. !*QNo Chief Editor Found: make sure one DB chief is selected in the table ClauseListA@@ B@B B@Bzk ">'D B@B B@Bi ]8 ]X $$. SELECT * FROM ClauseList WHERE Chief = True; %&. !*QNo Chief Editor Found: make sure one DB chief is selected in the table ClauseListA@@ B@B B@Bzk "B'F B@B B@BiPHAttribute VB_Name = "Common utilities" 0OptiHdpare Database`Expl@icit FHunc^cSpSpecialCharacters() Dim db AsLrstRecordseQSet)= CurrepntDb?+=A.Open1("Rough",Dynts With 6!o Un .@EOF . Ed`' Scrub out extra spaces; convert and <@TILDE>!!V[R]c!( A.![SuggestedRepmedy  Response C'Force statusYdes to upper cܛDSB AUC(. )If 5O"") Then ![!@JRLJTTypS =BR ; A#Kdclause numbbPd'N>C bE$znull valuezGLOBAL so ChiefH wi@sehrimm!9IsNUC)8E"008E_ If%Ningle-digit C`lead 0zeroC!Len'1MSelect Sg$!"0" To l"9 **!&?A# C I#.U0pdat .MoveN L`oop a B .Cloadb%Ţ (sng1kACR, asc0iiCRng "#Chr(`13) +; 0A @-1{Lc/ *T$rangSReplAll,rCRH F""~" 4 cc=A R DR fEmpty#'q 0!(sou, findubsˡA2n0Loa0*# I%Ex@a>#] #$s  nInI(1@" n <> 0w7cgLefBtn - 9_Qr1& sa Righa=#)@(n+! RC:D  ((  p(3 !6 'a default inbr noth ) elKhas|ns@#tyonqsq = #T'~D "a'+p W+n#V n= /1"#e#While "$!3#)"#c?B# '" G % - Wenzd?u`&&AWp&SsHas@q$Boo m &st0P[[as\YJYja?s%%!!!f = Fa- 10>0f9@ 0q > =Trusu^a`=Up0,*Sjb`N" tB#U"=   l5&P3( ?A1AT".,,},,U+p.0o%,x JlO M,,,,),߿j/#qGb )3, ?1,,,Е`O, , ,ce = Left(source,nX) - 1) Ha sWhitTr ueLEnd If cStripTrailing< J (False) Then Exit Function, Wend `   pDataFile(dx' Check for the existe@nce ofd . f/ dx Dim s A$s ng4If (IsNull(MF3g""V  dxEmpty0 s8Dirh' ""%zFEI oJ Sub cFixes(rst ' Initially designedBRa recordset argument, with a 0curr aov' Works from in em if you cH!tMe!WA@$3 '@Sqre is no Cre(ate-,Aql "today `cIsBla nk(![G ])}Q \C'Always u p@eLastMod![]l outWrit@necessar, ,Select Case1ResponseStatus]@"W" '  has be@wC"G A ![iGC}#'*Accept_Rej@A4N1ComAPA", "R.appHrov Zby1c2Ad![O!a!Closed_Unsatisf!!@@jC!"UZB AdO\CyEAcUnScrub(s ngABtrCR, asciiCR=r(13)4 +#0@= `"a@' Sasocarriage@turns -- useful wρne Cto8p@vaole Donto just one GD`DcReplaceA`Ǥ, h+"~5"*'!)(cCo0ncat| cted⹉'D+IntroDNameFieldp6?tr Ch~g_3 P-" &#W AID: G^ ID] F_& "$e~rmSE>mbPh0%K[bFaxO@CoC>of !la3?cC/"@P:Lin>e$ Typ8g%"g-&R%_Z;K(SuggedRemedy?3//@rԃ%OEclG57@WpiQImatqviewxnon-editors. Inclu mo"s`butnoѰll,fJeach^QH#EBIyCcs..E U{W` myY General!!Y, Fo`XtoD)YXTtr ernalt6XɘX3_\r_Z u(1uquZZ @spguawe shoulpT6 1(&!S A"X"ς`pC"DA naA'Now buip upr9' s'hc5 &RlFe7![k?9PPTopic![ <& Ս: " & ![CreateD0]xstrCR _ & "LastModLlDisppatch n (8Written 76Accept_Reject <BClosed_Unsatisf " #VoterStatus:  ' The general format includes every thing t reictedplus additional)fieldsOI d trackAand comment s,%cCo ncatG$= R(rst)+C;F&rInC E!WithFu|nc+S@ummaryA, ForceXtoD) As Str/ Dim Fi@"Line,ASecond; C@;+R, asciiH= Chr(13) +C0)  E = ""18 $R'' figure ouuf we@ shoulBoc|e A%`D&9CIf ((> = True@R( nC ]@"X"))nA/=*D@)Else #a8If`` #f/CL:la0use],aTopicn Type#! /! '![Tponse# SBCsSubC #IDwM= Left(cUnScrub4@]), 80DeC.Rc'A0#'`se@DuCch we~port: bRer$0?2qpGpIsBlank(xmBooleaJQIsNull )McAT#Exit e #G  Len(cypLeady" = $O!X 'O`rwiZ(Fa"]#  e cGetOwName^(z@xaRrdsetÍdb@aba SetF `urr`xD.b=`.Open("SELECT * FROM #OListcdTWHERE bD*;"B'! .EOF|MsgBox ("NodFound:0 mak@"ne DB o i`s selprcin&tablHr0?!*o#db. A* p!Eior1RXEEmailoa ?pLheD,"72{3Chie:f3 3Pu3 C3t0 33332 @H3F3S*744c4e 4#3.5??6  p4!H;Public4soNoNoNRoN44sÍaN3 sNNeA 4"4  8 IB@.prepare five different measures1. responses need to be writtenWHERE ResponseStatus = "O" '"   "$2 )02. Ready for committee action9WHERE CommentStatus In("X","D") AND ResponseStatus = "W" '"   "$2 )43. Re(SLS S<N0{BFF2D379-FF46-11D0-8168-444553540000} ` @   (%@81= "  ( "0 8  H "PX h x    " xp A@oP@ A@o0 $W' A@xkp OW't gene A@\mydk8o0 A@oAttribute VB_Name = "Form_fRough" Bas0{BFF2D379-FF46-11D0-8168-444553(540} |GlobalSpacFalse dCreatablTru Pre declaId"Expose_TemplateDerivCustomizD$Option CompK[@ D3T  _qZ+rRoughq8/Oq@lCrJ+?@py ( 0 @P X "`hx " " " "   NX`px 2.   0 @ ,X     .  l P vh  t p <x   2  B X `  (h  f  (  8 H P Jp    6  (08l h8x ` h   (8@ H F`      6  &@ h x   N   0@P`p(8HXhx   ,     2DH <     (0@ H"PXx"  ,   2 . PX  0` , JX` h6 ( PX (h .(jH BX .     ` (xK[ (P f` . 80 H .P    X xp]@X]x]$$. <prepare to index through all entries in the ClauseList tableSELECT * FROM ClauseList ; ( %&.'for all entries in the ClauseList table !*b ",CHECK B@.prepare five different measures1. responses need to be writtenWHERE ResponseStatus = "O" '"   "$2 )02. Ready for committee action9WHERE CommentStatus In("X","D") AND ResponseStatus = "W" '"   "$2 )43. Ready for commenter sign-offWHERE CommentType = "TR" 7AND CommentStatus In("A","R") AND ResponseStatus = "W" '"   "$2 )64. Hot item - TR unsatisfiedWHERE CommentType = "TR" AND ResponseStatus = "U" '"   "$2 )8 5. Item done=WHERE ((CommentType = "TR" AND ResponseStatus In ("C","Z")) ?OR (CommentType <> "TR" AND ResponseStatus In ("C","U","Z")) SOR (CommentType <> "TR" AND ResponseStatus = "W" AND CommentStatus In("A","R"))) '"   "$2 ): B@<k B@> end of clause loop B@B B@BRecord counts completeA@@ StatusReport FClauseList <> "CHECK" BB@DoH]p]5prepare addtiional conditions based on the ClauseList ",ALL H'"d H AND Clause In( ",)'"k SELECT COUNT(*) AS rcount FROM Main  "; %&. !*1cMeasure: horrible error, could not count recordsA@@'2d "J'2 B@BkiTildeANoGeneralANoX(SummaryATo0h RestrictedANoZHThis subroutine outputs comments according to clause and type selections]](@]`]x+Check that a clause selection has been made d"f",$b"Please select from the Clause ListA@@|k)Check that a type selection has been made d"f"h$b Please select from the Type ListA@@|pkh'This subroutine creates one output file X RestrictedPlease enter output file nameWEB Ascii report generatorc:\mydocs\WEBascii.txt$j'^ XGeneralePlease enter output file nameEditor's Ascii report generatorc:\mydocs\EDITORSascii.txt$j'^ XTildeePlease enter output file nameEditor's Tilde-file generatorc:\mydocs\EDITORStilde.txt$j'^d/Error in module cASCIIReport. Invalid argument.A@@|@k8,Make sure the user didn't hit the cancel key ^6A valid filename is required. Use OK to accept defaultA@@|k"Check for existence of output file ^$l=Warning! Output file already exists. Do you wish to continue? nOutput file error$@'` `G|j Otherwise ^A@pk d"f",CHECK=Checking for records that don't match any known clause numberA@@|hk` d"f",ALL)Preparing to print report for all clausesA@@$$.   SELECT * FROM Main WHERE  LVAL '=O>StartUpForm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@))Remove "max frames" from Figure-17 and instead include a two-octet wide "total numbeRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause 4 then they should be found in the draft. Also, I submit that for "DLL" it should be "Dynamic-Link Library" not "Data Link Layer". Finally, if you want to create an acroynRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defiRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of tRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definitioRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collectioRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload ofRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burst LVAL Remove open/association MTS/MCTA mechanism and Revert back to the use of GTS when referring to time slot in super frame and CTA beingRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Add ChallengeResponse to Table 105 with proper Length, Value, and Description from other portions of clause 10 or by definition by Rene Struik.Change "ECMQV manual, NTRUEncrypt raw 1, or RSA-OAEP raw 1" with "ECMQV manual, ECMQV implicit, ECMQV X.509, NTRYEncrypt raw 1, RSA-OAEP Raw 1, or RSA-OAEP X.509 1"Change the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Again, I suggest adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells. Please make the change globally.I suggest "...being updated, Clause 10."; that is if you mean "10" refers to Clause 10. Please make thRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Add ChallengeResponse to Table 105 with proper Length, Value,Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Add ChallengeResponse to TRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocatRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTSRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is uRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTSRevert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV. LVALh@)XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.3.5.129647E@i@ xXOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.2.22851315TR@i@xXOzjZBsame as comment #537 in LB12 and Comment 387 in LB19 ORIGINAL COMMENT (LB12): What is the point in having slotted aloha access in addition to the backoff in CAP, TDMA in CFP? Why is this complexity being thrusted on the implementors of this "low cost", "low complexity" and "low power" standard?I don;t see any justification in having yet another access scheme with WPAN.ORIGINAL SUGGESTED REMEDYRemove slotted aloha scheme in 8.4.3.4 and all references to it from the draft.RESPONSE: REJECT. Slotted Aloha was added to make the MAC more versatile so thaSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that areSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.same as comment #537 in LB12 and Comment 387 in LB19 ORIGINAL COMMENT (LB12): What is the point in having slotted aloha access in addition to the backoff in CAP, TDMA in CFP? Why is this complexity being thrusted on the implementors of this "low cost", "low complexity" and "low power" standard?I don;t see any justification in having yet another access scheme with WPAN.ORIGINAL SUGGESTED REMEDYRemove slotted aloha scheme in 8.4.3.4 and all references to it from the draft.RESPONSE: REJECT. Slotted Aloha was added to make the MAC more versatile so that more PHYs that could use the 802.15.3 MAC. While it could be added at a later date, that would make the MACs incompatible.REBUTTAL:SAME AS THAT FOR COMMENT 536 in LB12Commenter's response (LB22)If slotted aloha is added so that the MAC is used in other PHYs, sinceDEVs using different PHYs can not directly communicate with each otherwhy should it cause incompatibility? The new mechanisms in MAC must beadded only when a defined PHY needs it, all of which we may not knowtoday. At the time of addition of new mechanism, it has to be overlaidon the existing mechanism. and there is definitely a way to do the samewith slotted aloha as and when it is needed. For example, a set of streamindices can be left reserved and used at that time for the purposedesired.RegardinSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.LVAL>Same as CID 410 in LB22Original comment:The new field "Num max frame size" is mostly useless. What if all the framesare (aMaxFrameSize-1) octets long? Instead of that, it is useful to includethe total number of octets as sum of number of octets in the payload of all frames sent in the dly-ack-window. this total number of octets is helpfulin buffer management at the receiver which is supposed to hold all theframes (in some corner cases) until a delayed-ack-frame is sent.Suggested Remedy:1. Remove "Num max frame size" from Figure-15 and all its references from the fraft2. Include total number of octets as sum of number of octets in the payload of all frames sent in the delayed-ack-windowResponse:REJECT. Two variables are needed, the total amount that can be sent as well as the number of frames that the destination DEV is able to handle. The number of frames is important because there are physical limitations in the Dly-ACK generation. The other reason is that there are physical limitations in the buffer implemention, e.g. addressing.Commentor's response:The commenter agrees that there are two variables needed and it is evidentby the suggestion. But what is not clear is the intention in providing number of frames of size aMaxFrameSize, instead of providing a direct bound of max on totalnumber of octets that is entertained in the burst. The implementations can makeuse of this information in a useful way while the current info does not given anycluse on the size of the (MAxNumFrames - NumMAxFrameSize) of the frames. How doyou expect the implementations to guess those sizes? If all of them are(aMaxFrameSize-1), they are not indicated to the rx-DEV in this frame and the rx-DEVis supposed to handle them properly. In the worst case if all of the NumMaxFrames areof the size (aMaxFrameSize-1), then NumMAxFrameSize will be indicated as zero althoughthe rx-DEV has the pain of dealing with these mega-burst!! LVALha[MCTA] We need a little better specification on how often MCT[MCTA] We need a little better specificLooks like period seWhMissing the clause xref Missing the clause xref for the Non-secure beacon.Missing the clause xref for the Non-secure beacon.Why are raw keys called manual certificMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like peMissing the clause xref for the Non-secure beacon.WhMissing the clause xref for the Non-secure beacon.Why arMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for Missing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like periMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for EMissing the clause xref for the Non-secure beacon.Why are raw keys caMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like periodMissing the clause xref for the Non-secure beaconMissing the clause xref for the Non-secure beacon.Missing the clause xref for the NonMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks liMissing the clause xref for the Non-secure beacon.Missing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks lMissing the clause xref for the NMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like peMissing the clause xref for the Non-secure beacon.Why are raw keys cMissing the clause xref for the Non-secure Missing the clause xref for the NoMissing the clause xref for the Non-secure beacon.Why are raw keys callMissing the clause xref for the Non-secure beacon.Missing the clause xref for the Non-secMissing the clause xref for the Non-secure beacon.Why are raw Missing the clause xref for the Non-secure beacon.Why are raw keys called Missing the clause xref for the Non-secure beacon.Why are raw keys called manual certificateMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks Missing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like periodMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like period sMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks liMissing the clause xref for the Non-secure beaMissing the clause xref for the NonMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates forMissing the clause xref for the Non-secure beacon.Why are raw keys called manual certificates for ECMQVLooks like perioMissing the clause xref for the Non-secure beacon.Why are raw keys callMissing the clause xref for the Non-secure beacon.WMissing the clause xref for the Non-secure beacon.*T~ͨ*&OxȋǴ9lß@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074TR@{6@}XO{k@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074TR@{6@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp072.3978TRo@{]@ }XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp072.3TR`@{%@ }XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp072.9.1E~@{>@ }XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp072.1.7TR@{f@ }XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp072.1.49532E:@{X@ }XO{kk]H6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.313338T]@ {@}XO}yn`RC6i@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.313320T<@ {]@}XO}yn`RC6h@3@`6@ `6@`6@ Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.213217T-@ {k@} ACCEPT. AC}yn`RC66g@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.113122Tp@ {&@}XO}yn`RC6f@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.113114TR@ {Z@}XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.8.31284T@{@}XO}yn`RC6c@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.8.212722T@{@}XO}yn`RC6b@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.8.11273T@{&@}XO}yn`RC6a@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.612634T[@{@vXO}yn`RC6`@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.512619T@{@ yXO}yn`RC6_@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.512616T\@{@ yXO}yn`RC6^@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.312522T@{@ yXO}yn`RC6LVAL> vsame as CID 414 in LB19Original comment:In this sentence what does "multiple beacons" actually mean? Multiple beacons in the same superframe, similar to fragementing beacon, OR IEbeing present in beacons sent at different TBTT but each time with differentcontents of association info. I think what is intended is to say thatif there are too many assoc/disassoc, the beacon at current TBTT may notbe big enough to carry them all, so the remaining Dev-assoc-IEs will befilled into the next beacon sent at next TBTTSuggested Remedy:If intended, do NOT allow fragementation of beacon. Alter the sentence inln42:43 to mean that the PNC may send IE corresponding to a recent assoc/deassoc in the beacon at next TBTT if the current beacon does nothave space for it.Response:ACCEPT IN PRINCIPLE. Delete the sentence "The PNC may use multiple beacons to broadcast successive DEV association IEs if too many DEVs are associating than will fit in a single beacon.." as it is confusing and does not add any new information. The PNC is able to choose when it sends any IE.Commentor's response (LB22)The response addresses the issue only partially. For interpretations towardsconformance, "The PNC is able to choose when it sends any IE" is not correct The interpretation by vendors can go either way. that is, a group of implementors might expect the Dev-Assoc-IE contianing the recently associated DEVs to appear immediately after assoc while the rest might tolerate it appearing anytime. Hence the inclusion of the suggested remedy is required. I have rephrased the same in thefollowing text for editor's peruse (Applicable after the removal of sentence asin the response)."The the DEV association IE corresponding to an association shall be included in thebeacon sent at the start of immediate next superframe, excepting the case where thatbeacon is already at its maximum allowed size where the inclusion of IE is delayeduntil the space in the beacon permits the same."76`Ύ;Gpɟ(Uńı8kg$ C@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.4TR@@XO{kk]H6Z@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.3TRf@@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.2E@ h@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.1Esome inconsistencies@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.15110TR@ 1@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.15110Es@ s@XO{kk]H6A@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.15110TR@ s@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.14109E#@ @XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.13109TR@@}XO{kk]H6@@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.12108TRe@PH@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.11108E`@j@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.1010746TRF@@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.10107EE@@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.10107TR)@C@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.10106TR,@@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.7105E`@\@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.6105TRk@M@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074.210313TR@{J@}XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp074TR@{@@}XO{kk]H6 LVALn  @ @ @ @ @ @ @Table-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MACTable-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provides a list of PHY parameters in a table, the values have to be searched through in those referred clauses, which can easily be avoided.Table-120:Definition of MIFS and BIFS: Since MIFS is less than SIFS, make them same as SIFS. Table-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provides a list of PHY parameters in a table, the values have to be searched through in those referred clauses, which can easily be avoided.Table-120:Definition of MIFS and BIFS: Since MIFS is less than SIFS, make them same as SIFS. The channel time saving by the use of MIFS is very little given the probability of its use, but this is another unnecessary IFS that the MAC has to deal with and it is not optional. Making MIFS same as SIFS adds to uniformity at the lowest level of MAC. If the committee is so bent on saving channel time, please explore putting back the chaining of commands and similar options where the saving is huge and not just a few (at most 10+) microseconds.Lines 53-54 on pp-178 with lines 1-3 on pp-179 create an unnecessary special case for starting backoff algorithm at the start of CAP. The save is not worth the special case at the lowest level of MAC where Backoff algo is run. Added to that, applicability of this special case gets narrowed by another level by the probability of not-correctly-receiving the beacon and/or the last extended beacon by a DEV. Although this specail case has a "may" in it and hence does not enforce its applicability, it is worth the space in the standard given the above reasoning.Same as commenTable-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provides a list of PHY parameters in a table, the values have to be searched through in those referred clauses, which can easily be avoided.Table-120:Definition of MIFS and BIFS: Since MIFS is less than SIFS, make them same as SIFS. The channel time saving by the use of MIFS is very little givTable-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provides a list of PHY parameters in a table, the values have to be searched through in those referred clauses, which can easily be avoided.Table-120:Definition of MIFS and BIFS: Since MIFS is less than SIFS, make them same as SIFS. The channel time saving by the use of MIFSTable-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provides a list of PHY parameters in a table, the values have to be searched through in those referred clauses, which can easily be avoided.LVAL> 4 Same as comment 513 in LB19Comment:same as comment #536 in LB12ORIGINAL COMMENT (LB12)If SA is broadcast and anybody could start tx, how's collision handled?What is the point in getting devices to collide here instead of makingthis MTS part of CAP and letting devices freely use CAP as alreadydefined. This is useless and adds unnecessary complexityORIGINAL SUGGESTED REMEDY (LB12): Remove lines 8:22 on page 151 and all references to "MTS/GTS with BC/MC-SA"from the draftResponse: REJECT. The slotted aloha access method is used to provide access to theseslots just as CSMA/CA is used in the CAP. The TG has decided to allow bothaccess methods, CSMA/CA in the CAP and slotted aloha in the MTSs so thatthe 802.15.3 MAC is capable of supporting different types of PHYs.REBUTTAL (LB19):The response does not resolve the issue of having COLLISION basedtransmissions under COLLISION FREE PERIOD, instead of making this partof CAP.I do not see 802.15.3 PHY or applications listed in PAR requiring it.I do not see how CSMA/CA mechanism used in CAP and TDM mechanism used inCFP fail in achieving whatever the slotted-aloha cheme is achieving.I do not see any reason or justification to add extra complexityresulting from having one another channel access mechanism. Suggested Remedy:Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Response:ACCEPT IN PRINCIPLE. Add new subclause 11.2.10,  Channel access methods with text  A PNC-capable DEV compliant to this standard shall allow the use of the CAP for contention based access for association, data and commands, {xref 7.3.1} when using the 2.4 GHz PHY. A DEV compliant to this standard shall support the use of the CAP when using the 2.4 GHz PHY. Use 1 bit from the reserved bits to the  Piconet mode field ,  MCTAs used with definitions  The MCTAs used bit shall be set to 1 if the PNC will be using open or association MCTAs. Delete the sentence on page 111, lines 1-2, 5hΝͽ?oɟȴ@ p80"H\@S@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.07Figure 3811315T:@@XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.077.5.1.311251E$@8@XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.077.5.1.211242TRX@#@XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.077.5.1.111236TR.@Please delete clause 7.5.1.1XOugH6R@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.07Figure 3711212T'@!Please change to DeviceAddress.XOugH6Y@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10.3TR@@XO{kk]H6`@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10.3TR@n@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10.1TRAction type is incompleteJ@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10.1TR@@XO{kk]H6D@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10.1TR@@XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10.1TR@s@XO{kk]H6 @3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.10Elength nconsistencyJ@ XO{kk]H6 @3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.8.3EP@V@ XO{kk]H6 @3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.8.2Euse of "TX slots"U@ XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.7E_@~@ XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.7TR@1@ XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp075.6E#@G@XO{kk]H6 LVAL v1b N  @ @ @ @ @ @66]66b66b66k68b68b68b68g6:b6:b6<b6<b6<b 6<b 6<b 6<b 6>b6@b 6@b6@b6@g6@g6@g6B]6B]6B]6B]6B]6B]6Bg6Bg6Bg6Bg6Bg6Bg 6Bg 6Bg 6Bg 6Bg 6Bg6Bg6D]6D]6Dk6Dk6Dk6Dk6Dk6D/6D/6D/6D/6F]6F] 6H] 6H] 6H] 86] 86]M]^mYbU^^MbYUYSSdiOMdbko^mYbU^^MbYUYSSdiOMdbko^mYbU^^MbYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^Mg YUYSSdiOMdbko^mYbU^^Mg YUYSSdiOMdbko^mYbU^^Mg YUYSSdiOMdbko^mYbU^^Mg YUYSSdiOMdbko^mYbU^^Mg YUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^MgYUYSSdiOMdbko^mYbU^^Mk`dmdid^J]`dmdid^J]`dmdid^J]`dmdid^J]`dmdid^J]`dmdid^J] `dmdid^J] `dmdid^J] `dmdid^J] `dmdid^J] `dmdid^J]`dmdid^J]mY`QOd`JYb]mY`QOd`JYb]mY`QOd`JYb]mY`QOd`JYb]mY`QOd`JYb/mY`QOd`JYb/mY`QOd`JYb/mY`QOd`JYb/ If the CAP end time indicates no available time and no message types are permitted during the CAP, then MTSs are implied. (note this deletion is in response to CID 407).Expand MLF13 in the PICs (note this will become MLF13.1 and MLF13.2 due to another comment.)MLF13.1; Open and association MCTA operations; 8.4.4.4, 8.4.4.5; O.1MLF13.2; Regular MCTA operations; 8.4.4.4; M{ed. note: the CAP stuff is like MLF13.3 now}Commentor's response:Response to this comment do not address the core issue of an additional access mechanism(MTS and slotted aloha) in the standard. The proposal does not justify why they are needed in802.15.3. Hence the resolution is unacceptable.cHYMUiyɇȕǣƳż @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ @@V`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.4.414515E6@{ pick one.XOugH6U`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.11129Eu@{8@hXOugH6T`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.81283TRi@{-@hXOugH6S`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum07Table 5212721E%@{?@hXOugH6R`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum07Figure 5108E@ Flip it!XOugH6Q`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 298312EV@)6@-XOugH6P`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.18.77245TR@ @XOugH6O`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 226941TRf@([@,XOugH6N`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 226939TRq@'+@+XOugH6M`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.16.26516T@ g@*XOugH6L`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.16.164T@g@)XOugH6K`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.15.3638E=@& pick oneXOugH6J`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.3.2.23349ERepetition of line 47./KO.@(XOugH6I`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.4.44017T@(@'XOugH6H`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORPEE@ XOq]H6G`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP0814TR@=@ uXOq]H6LVAL ?I suggest: Draft Standard for Information technology- Telecommunications and information exchange between systems- Local and metropolitan area networks Specific requirements- Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs) Please make the change globally. Additionally, and in terms of the LB19 CommentID: #10 rejection, I understand the PAR issue but I think this is a clear editorial issue and we have WG precedents to apply the editorial suggestion. Here are some issues to consider in this rebuttal 1. The 802.15.3 PAR is incorrect and is in conflict with itself and should state the previously mentioned item in the title section i.e., "2. Assigned Project Number [P802.15.3]" or section 4 should state "...Part 15.3...". http://grouper.ieee.org/board/nescom/802-15-3.pdf 2. An example is the 802.15.1 PAR which TG3 copied and is why you have the error in the first place :). When 802.15.1 got to Sponsor Ballot the PE said 15.1 was ok cuz (a) we had a corrigendum: http://ieee802.org/secmail/msg00600.html and (b) implicitly it was necessary to add the dot level based on the 15.2, 15.3, 15.4, etc. approvals. http://ieee802.org/15/par.html 3. Specifically, having the 802.15.1(TM)-2002 published sets a precedent as our PAR says "Part 15..." but we are published with "Part 15.1..." http://grouper.ieee.org/board/nescom/802-15.pdf Note: 802.15.4/D17 is in Sponsor Ballot with "Part 15.4..." 4. If you release the 15.3 Draft to Sponsor Ballot there might be an issue and someone might object BUT I think going forward w/ the title as-is is a bad idea. For example the 3rd of the 802 five criteria "Distinct Identity" will be problematic if the IEEE titles are NOT distinct and/or inconsistent in the WPAN Standards Family: http://ieee802.org/3/rules/rules.html#P72 Note: I applied (Session #20) the latest edit to the 802.15.3a DRAFT PAR because of this very issue and after careful review of other approved A LVAL N  ЅυυυυυυυυυυυυυJ: 4  e ;  N &StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC000010Tz@ilXOyhWD6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822MotorolaCC.1.436627E5@+%{@)XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.3.5.129647E@*%@)XOzjZB6`X@`X@orm&StartUpEChange "ECMQV manual, NTRUEncrypt raw 1, or RSA-OAEP raw 1" with "ECMQV manual, ECMQV implicit, ECMQV X.509, NTRYEncrypt raw 1, RSA-OAEP Raw 1, or RSA-OAEP X.509 1"Change the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Again, I suggest adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells. Please make the change globally.I suggest "...being updated, Clause 10."; that is if you mean "10" refers to Clause 10. Please make the change globally. Note 1: that this repeats further in the table i.e., column three last row. Note 2: The point being that clauses are called out e.g., "Clause 10" but subclauses e.g., "10.1" are not.I suggest capitalizing columns 2-5, adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells, and add the word "(continued)" to the second page overflow for Table 3. Refer to the May00, IEEE Standards Style Manual, page 19. Please make the change globally.I suggest "Valid range". Refer to the May00, IEEE Standards Style Manual, page 19. Please make the change globally. Note: Also, in Table 2 add periods to the first and second "description" entries to match the third entry...or delete the third entry period for consistancy. Please make the changes globally.I suggest you capitalize all three (3) column titles "Name Request Confirm". Refer to the May00, IEEE Standards Style Manual, page 19. This repeats on Table 3, etc. please make the change globally. Note: "Only the initial letter of the first word and proper nouns shall be capitalized in Column and line headings in tables (see Table 1)" IEEE Standards Style Manual.I suggest the Editor define the term "exposed" or provide examples for non native English speakers.s aRemove blank between period and last word in sentence ('key').Change 'should' to 'shall' and lt PHY Layer Standards and their titles: http://ieee802.org/secmail/msg02824.html In terms of the next step I suggest you ask Jennifer Longman what her opinion is i.e., leave as-is, apply edit, submit a corrigendum to the 802.15.3 PAR, etc. Finally, I think just from a publishing and distribution point of view it will become confusing - make the edit. If the Editor or Chairs need to change the PAR then please do so, however, the approved IEEE Std 802.15.1-2002 states "Part 15.1" and the PAR does not. It was not an issue for RevCom and the StdBD so it should be an easy edit to apply to keep our family of standards consistent. LVALЦh;h U  c =  Y P | A [SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable and moving devices within or entering a personal operating space." is gramatically incorrect.Again, the text "...20 Mb/s is proposed to be the lowest rate..." and the text on the next page, pg 2, ln 14 "...20 Mb/s or more..." are from the PAR but Clause 11, Table 118, pg 313, ln 14 states "...11 Mb/s...". It is very likely that this inconsistancy (PAR vs. Draft) issue will come up in Sponsor Ballot. A parallel PAR change now will add mimimal to no delay to the project BUT RevCom can add 3-6 months!The sentence "Compatibility and coexistence criteria were included in the proposal evaluations." is vague. The IEEE does not mandate the use of CFAs, CFPs, evaluations, and down selections so to say "...included in the proposal evaluations." does not make sense for non-IEEE 802.15 members.Change of GTS into CTA from D11 to D14 in clauses 5, 7 & 8:AT many places in clause-8, this has caused lot of confusion.For example pp-188[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard de[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropr[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with [SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request comman[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be li[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.LVAL ? kSame as comment 513 in LB19Comment:same as comment #536 in LB12ORIGINAL COMMENT (LB12)If SA is broadcast and anybody could start tx, how's collision handled?What is the point in getting devices to collide here instead of makingthis MTS part of CAP and letting devices freely use CAP as alreadydefined. This is useless and adds unnecessary complexityORIGINAL SUGGESTED REMEDY (LB12): Remove lines 8:22 on page 151 and all references to "MTS/GTS with BC/MC-SA"from the draftResponse: REJECT. The slotted aloha access method is used to provide access to theseslots just as CSMA/CA is used in the CAP. The TG has decided to allow bothaccess methods, CSMA/CA in the CAP and slotted aloha in the MTSs so thatthe 802.15.3 MAC is capable of supporting different types of PHYs.REBUTTAL (LB19):The response does not resolve the issue of having COLLISION basedtransmissions under COLLISION FREE PERIOD, instead of making this partof CAP.I do not see 802.15.3 PHY or applications listed in PAR requiring it.I do not see how CSMA/CA mechanism used in CAP and TDM mechanism used inCFP fail in achieving whatever the slotted-aloha cheme is achieving.I do not see any reason or justification to add extra complexityresulting from having one another channel access mechanism. Suggested Remedy:Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Response:ACCEPT IN PRINCIPLE. Add new subclause 11.2.10,  Channel access methods with text  A PNC-capable DEV compliant to this standard shall allow the use of the CAP for contention based access for association, data and commands, {xref 7.3.1} when using the 2.4 GHz PHY. A DEV compliant to this standard shall support the use of the CAP when using the 2.4 GHz PHY. Use 1 bit from the reserved bits to the  Piconet mode field ,  MCTAs used with definitions  The MCTAs used bit shall be set to 1 if the PNC will be using open or association MCTAs. Delete the sentence on page 111, lines 1-2,  LVAL v1b N '=O> @ &`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@3)XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@d@wXOyhWD6$`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC044.0942Eg@:%'@wXOyhWD6#`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.101942EI@;%&@2)XOyhWD6"`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.5784EI@9%K@1)XOyhWD6!`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3664950E6@8%-@0)XOyhWD6 `X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3564447E@i@wXOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.2661819E@ i@wXOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.1353839EP@7%@wXOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3511Ed@6%@wXOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC022.045354ED@5%@oXOyhWD6`X@`X@orm&StartUpShowDG If the CAP end time indicates no available time and no message types are permitted during the CAP, then MTSs are implied. (note this deletion is in response to CID 407).Expand MLF13 in the PICs (note this will become MLF13.1 and MLF13.2 due to another comment.)MLF13.1; Open and association MCTA operations; 8.4.4.4, 8.4.4.5; O.1MLF13.2; Regular MCTA operations; 8.4.4.4; M{ed. note: the CAP stuff is like MLF13.3 now}Commentor's response:Response to this comment do not address the core issue of an additional access mechanism(MTS and slotted aloha) in the standard. The proposal does not justify why they are needed in802.15.3. Hence the resolution is unacceptable. LVALs '=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@3)XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@d@wXOyhWD6$`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC044.0942Eg@:%'@wXOyhWD6#`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.101942EI@;%&@2)XOyhWD6"`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.5784EI@9%K@1)XOyhWD6!`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3664950E6@8%-@0)XOyhWD6 `X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3564447E@i@wXOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.2661819E@ i@wXOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.1353839EP@7%@wXOIn a series of three or more terms with I suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalI suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)."In a series of three or more terms with a single conjunction, use a comma after each term except the last. I suggest "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable, and moving devices within or entering a personal operating space."; adding a comma after portable. Refer to the May00, IEEE StI suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)."In a series of three or more terms with a single conjunction, use a comma after each term except the last. I suggest "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable, and moving devices within or entering a personal operating space."; adding a comma after portable. Refer to the May00, IEEEI suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)."In a series of three or more terms with a single conjunction, use a comma after each term except the last. I suggest "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable, and moving dI suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)." LVAL'=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@3)XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@d@wXOyhWD6Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause 4 then they should be found in the draft. Also, I submit that for "DLL" it should be "Dynamic-Link Library" not "Data Link Layer". Finally, if you want to create an acroynm or abbreviation for "Data Link Layer" use "Layer 2" or "L2".Again, change sentence to read "The area of overlapping coverage between the two piconets may vary between congruency with the parent coverage area to mostly non-overlapping."; change "congruent" to "congruency".To minimize the entries into IEEE 100Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage styUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis cUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key toUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis codUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID" LVAL J$D u K  ^ 8 J  A StartUpForm[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that i[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.Same as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.Verification info length(=L2) does not seem to be required since the length of the ACL record field will determine len[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that i[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response com[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedK[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response comman[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7. LVAL  @ @Put back the paragraph that mandated the start of an IE at even position of octets and hence the paddinPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Again, I suggest adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells. Please make the change globally.I suggest "...being updated, Clause 10."; that is if you mean "10" refers to Clause 10. Please make the change globally. Note 1: that this repeats further in the table i.e., column three last row. Note 2: The point being that clauses are called out e.g., "Clause 10" but subclauses e.g., "10.1" are not.I suggest capitalizing columns 2-5, adding "en-dash" (from IEEE FM template (bPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets"Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE wheneverPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end oPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total siPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.LVAL4?x  _G Z e  f " n 8 ?  (CwHV6Same as CID 410 in LB22Original comment:The new field "Num max frame size" is mostly useless. What if all the framesare (aMaxFrameSize-1) octets long? Instead of that, it is useful to includethe total number of octets as sum of number of octets in the payload of all frames sent in the dly-ack-window. this total number of octets is helpfulin buffer management at the receiver which is supposed to hold all theframes (in some corner cases) until a delayed-ack-frame is sent.Suggested Remedy:1. Remove "Num max frame size" from Figure-15 and all its references from the fraft2. Include total number of octets as sum of number of octets in the payload of all frames sent in the delayed-ack-windowResponse:REJECT. Two variables are needed, the total amount that can be sent as well as the number of frames that the destination DEV is able to handle. The number of frames is important because there are physical limitations in the Dly-ACK generation. The other reason is that there are physical limitations in the buffer implemention, e.g. addressing.Commentor's response:The commenter agrees that there are two variables needed and it is evidentby the suggestion. But what is not clear is the intention in providing number of frames of size aMaxFrameSize, instead of providing a direct bound of max on totalnumber of octets that is entertained in the burst. The implementations can makeuse of this information in a useful way while the current info does not given anycluse on the size of the (MAxNumFrames - NumMAxFrameSize) of the frames. How doyou expect the implementations to guess those sizes? If all of them are(aMaxFrameSize-1), they are not indicated to the rx-DEV in this frame and the rx-DEVis supposed to handle them properly. In the worst case if all of the NumMaxFrames areof the size (aMaxFrameSize-1), then NumMAxFrameSize will be indicated as zero althoughthe rx-DEV has the pain of dealing with these mega-burst!! LVAL  [SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KO[CTA/PM] CTR may be refused because destination is in hibernation. Therefore change the error code to reflect both the case were a stream is established but the destination enters hibernation or SPS, and the case where a CTR is made for a DEV in hibernation/KO[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting undiscussed ad-hoc inventions into the draft. If you really want to wake up a sleeping DEV at some unknown time in the future, we could consider having a new command to set the PCTM bit. One way would be to add a DEVID to PS mode change. If (operation == ACTIVE && dev != UNASSOC) set PCTM(dev)./KO[PM] The DEV is not [SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authent[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KO[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Eith[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KO[PM] The requestor cannot hang and wait an indefinite time for a decisio[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KO[PM] The requestor cannot hang and wait an in[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KO[PM] The requestor c[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KO[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting undiscussed ad-hoc inventions into the draft. If you really want to wake up a sleeping DEV at some unknown time in the future, we could consider having a new command[CTA/isoch] support of pseudostatic streams are not mandatory, while support for an isochronous stream (would imply dynamic) is./KOLVAL4?x  _rLh _ P @  : same as CID 414 in LB19Original comment:In this sentence what does "multiple beacons" actually mean? Multiple beacons in the same superframe, similar to fragementing beacon, OR IEbeing present in beacons sent at different TBTT but each time with differentcontents of association info. I think what is intended is to say thatif there are too many assoc/disassoc, the beacon at current TBTT may notbe big enough to carry them all, so the remaining Dev-assoc-IEs will befilled into the next beacon sent at next TBTTSuggested Remedy:If intended, do NOT allow fragementation of beacon. Alter the sentence inln42:43 to mean that the PNC may send IE corresponding to a recent assoc/deassoc in the beacon at next TBTT if the current beacon does nothave space for it.Response:ACCEPT IN PRINCIPLE. Delete the sentence "The PNC may use multiple beacons to broadcast successive DEV association IEs if too many DEVs are associating than will fit in a single beacon.." as it is confusing and does not add any new information. The PNC is able to choose when it sends any IE.Commentor's response (LB22)The response addresses the issue only partially. For interpretations towardsconformance, "The PNC is able to choose when it sends any IE" is not correct The interpretation by vendors can go either way. that is, a group of implementors might expect the Dev-Assoc-IE contianing the recently associated DEVs to appear immediately after assoc while the rest might tolerate it appearing anytime. Hence the inclusion of the suggested remedy is required. I have rephrased the same in thefollowing text for editor's peruse (Applicable after the removal of sentence asin the response)."The the DEV association IE corresponding to an association shall be included in thebeacon sent at the start of immediate next superframe, excepting the case where thatbeacon is already at its maximum allowed size where the inclusion of IE is delayeduntil the space in the beacon permits the same." LVALЗ{tmf_XQJC<5.'  xqjc\UNG@92+$Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command wiUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="ThUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen to system wake beacons and CTAs where its DEVID is indicated as the destination."Please refer to Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channeUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with DUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time requesUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but wUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but wUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key tUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"Delete page 145 line 9-14. Replace with: "The PNC shall deny aUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to beUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with DescrUse same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID" LVALThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resoThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resources" to "Resources available". The reason is that they are in a condition symbol and not in a task symbol, so the condition for approving the request is that resources are available./KOThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate security suites which was not the intention of the BRC when this was accepted.Since the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication.See CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.Table-66. The cell corresponding to "Hibernate in wake superframe" column and "Beacon" row contradicts the text on pp-220, lines36-41 where the hibernating DEVs are allowed the liberty of sleeping through "any" beacon until they themselves change over to ACTIVE state (and it should be within ATP to retain the membership of Piconet)Lines 53-54 on pp-178 with This comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resources" to "Resources available". The reason is that they are in a condition symbol and not in a task symbol, so the condition for approving the request is that resources are available./KOThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resources" to "Resources available". The reason is that they are in a condition symbol and not in a task symbol, so the condition for approving the requThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. DeletThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resources" to "Resources available". The reason is that they are in a condition symbol and not in a task symbol, so the condition for approving the request is that resources are available./KOThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of anThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.'MoƑźCompObj@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.5.10.313339T TBD present_@(XOooaF6^@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.5.10.313448T "frequency" is the wrong term.change "frequency" to period.XOooaF6]@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.5.10.313327T@2@XOooaF6\@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.5.10.313251T(@<@'XOooaF6[@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.5.10.3T@I@XOooaF6Z@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.4.1010810T\@3@&XOooaF6Y@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.4.1010733T6@@@%XOooaF6X@3@@3@  Y Schrader, Markmark.e.schrader@kodak.com585-253-5241Eastman Kodak Co.077.19315T@-B@XOooaF6T@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.7.112338TR@,@$XOseH6K@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.10.313518Td@+Q@#XOseH6J@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 77134TRh@*T@"XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.10.313338TRLine 38 contains a TBD'@!XOseH6H@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.10.3132T line 51D@ XOseH6G@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 75132E1@) add bracketXOseH6F@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 75132TR Width of Stream QoS parameters@XOseH6E@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 75132TUse command number0x0011XOseH6 LVALEEEΪP t  e 3 b j A org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC00001[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot fin[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any o[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The last sentence is what happens with asynchronous data if no CTA arrives before the SDU timeout. In the case of ISOCH-DATA, you do MLME-[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-inter[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval i[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot [CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in [CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KOAre the references to draft standards allowed? I thought IEEE allowed references only to the already existing standards. Please check.Table-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provides a list of PHY parameters in a table, the values have to be searched through in those referred clauses, which can easily be avoided.Are the references to draft standards allowed? I thought IEEE allowed references only to the already existing standards. Please check.Table-120:PLEASE summarise all PHY parameters (aCCADetectTime, aPHYSIFSTime etc.) in a table at one place instead of spreading them all around the PHY clause (something on the lines of Table-64, for MAC, is very desirable from implementors' view). Although Table-65 provAre the references to draft standards allowed? I thought IEEE allowed references only to the already existing standards. Please check.Yc ,7IT`\ivƆ}l|Š @ f`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 11418910Ev@ Please change.XOugH6e`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.118814TR@ >@hXOugH6d`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.118738TR@B@hXOugH6c`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.4.4.218040TRz@{Delete line 40-43 onpage 180.XOugH6b`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.4.4.218038TR@Remove this sentence.XOugH6a`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.3.217522TR@_@ uXOugH6``X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 10217123E/@?@XOugH6_`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 10016923E/@>@XOugH6^`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.2.416814Eleft over Ed Note/KO+@ uXOugH6]`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 9816640TR@$@XOugH6\`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.2.316520TR@FixXOugH6[`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.2.316428EL@=@XOugH6Z`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.7.315720E@fixXOugH6Y`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.6.41559TRe@2k@8XOugH6X`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.5.11513TR3@18@7XOugH6W`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum07Figure 7915051TR+@0S@6XOugH6c$$0N]l{ƌŖħõ @ v`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.520737TRQ@ @XOugH6u`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.539550TR@ @SXOugH6t`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.5.215237TR@9@9XOugH6s`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.32219TR@@XOugH6r`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.32217E`@{ remove!XOugH6q`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121619EN@{&@HXOugH6p`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121542TR@ @XOugH6o`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121549TRB@{a@hXOugH6n`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121139TR)@{@hXOugH6m`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.420636E4@{XOugH6l`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.8.420151EK@{+@hXOugH6k`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.8.320116E$@{rename to "max burst".XOugH6j`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.72004TR@ Delete or clarify.XOugH6i`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.6.219746E-@{XOugH6h`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.219113EH@{Move sentence to 8.5.1.1XOugH6g`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.21919TR@ [@hXOugH6 LVAL k-- N  } (  ;  \  A  [SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of [PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting wi[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation unnecessarily complicated. All this calls for a unified rule for PSPS and SPS: If you miss your wake beacon, listen to the next beacon/KO[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting wit[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation unnecessarily complicated. All this calls for a unified rule for PSPS and SPS: If you miss your wake beacon, listen to the next beacon/KO[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacon[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beaco[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beac[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation utterly co[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons st[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation utterly complicated. All this calls for a unified rule for PSPS and SPS: If you miss your wake [PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation utterly complicated. All this calls for a unified rule for PSPS and SPS: If you miss your wake beacon, listen to the next beacon/KO LVAL @The PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE mode by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to it'The PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE mode by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to it's own DThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE mode by sending the PS Mode change command with the PS Mode field The PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE mode by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to it's own DEVID. A power save DEV that wakes up and finds its bit set in the PCTM shall switch to ACTIVE mode and remain ACTIVE for at least the CTRResponseTime indicated in the beacon. A DEV may request that the PNC sets the PCTM bit for another DEV by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to the DEVID of the peer DEV it wishes to wake up.replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"1) Create a new PNC Scan IE. Parameters: Suspend beacon number[16b], Quiet supThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set tThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set tThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set tThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE mode by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to it's own DEVID. A power save DEV that wakes up and finds its bit set in the PCTM shall switch to ACTIVE mode and remain ACTIVE for at least the CTRResponseTime indicated in the beacon. A DEV may request that the PNC sets the PCTM bit for another DEV by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to the DEVID of the peer DEV it wishes to wake up. LVAL @I suggest that the 802.15.3 Ballot Review Committee (BRC) submit a draft corrPut back the paragraph that mandated the start of an IE at even position of octets and hence the paddinPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)I suggest that Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octetPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the toPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size oPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total sizPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)I suggePut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)I suPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end oPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total siPut back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.c!1BRcsɃȕǥƵ @ @   @ `X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 339036Ek@{#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.24.48534T@%@3XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.24.38510E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 298325T@*@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.18.1717E@@ XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 226914Tq@+#@2XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.18.16841E@@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.712737T@#@=XOugH6~`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.18.16837Tq@*#@1XOugH6}`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.2.714129TP@9@<XOugH6|`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.8.44918TP@9@0XOugH6{`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.2.614112TI@5@;XOugH6z`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.8.34851TI@5@/XOugH6y`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.2.113825Tj@#@:XOugH6x`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.7.14240Tj@ #@.XOugH6w`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.6.419842TR@@XOugH6 LVAL l  @ @ @ @ @ @ @ @ @ @ @ @66]66b66b66k66k66k 68b68b68b68g6:b6:b6<b6<b6<b 6<b 6<Delete pa[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbi[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additions by the TE are [Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additi[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this [Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additions by the TE are abominable. If the TE felt this was a necessary item to address why wasn't it raised as a comment during LB-19? No CID, no discussion, no to its inclusion.[PM/CWB] Delete the Continued wake beacon IE. The use of the CWB IE in the wake beacon [Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that request[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additions by the TE are abominable. If the TE felt this was a necessary item to address why wasn't it raised as a commen[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additions by the TE are abominable. If the TE felt this was a necessary item to address why wasn't it raised as a comment during LB-19? No C[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary addit[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additions by the TE are abominable. If the TE felt this was a necessary item to address why wasn't it raised as a comment during LB-19? No CID, no discussion, no to its inclusion.[PM/CWB] Delete the Continued wake beacon IE. The use of the CWB IE in the wake beacon only works if the sleeping SPS DEV hears the wake beacon and in that case the SPS DEV doesn't need the CWB IE. And in the other case it doesn't matter, because it can't use th[Frag] Delete the "preferred fragment size" sub-field from the DEV capabilities field of the capability information IE. There were no CIDs from LB-19 that requested this addition. Arbitrary additions by the TE are abominable. If the TE felt this was a necessary item to address why wasn't it raised as a comment during LB-19? No CID, no discussion, no to its inclusion.Uc ,>Pas @ `X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.4.4.718526Es@{#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.3.117315T'@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Table 601679T@#@LXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.2.316448Eg@S@KXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.2.216337E@Y@JXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.8.115840T@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.3.117249E@$@IXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.7.515749E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.6.215322E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.5.115017E@Please make the change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.4.614924TRr@j@>XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.1513131TR@Make the requested deletion.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.111298E)@3Please make the change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.1212941TRw@Make the deletion.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum07Table 5112333TR@Make the requested deletion.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum06Table 349116T;@%@hXOugH6 LVAL  @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @@@@Change this sentence frag. <from> "...in the superframe of the CTR status IE announcemeChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported in capability", "PSPS supported in capability", and "Hibernation supported in capability". These modes are Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported in capability", "PSPS supported in capability", and "Hibernation supported in capability"Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this senChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] PleChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." ThChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this sentence fChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communicationsChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."hc 0$1CUEYj{nЅ     @ @ `X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121548E@$@ uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321537TR;@Make the requested change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121246E@ #@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121242E@ #@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121136TRy@Make the indicated change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121133E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1121113TR@+@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.52081E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.420638E@"Please make the rquested change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.320542T@+@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.220529E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 12920525E@#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.719935TR@Make the requested deletion.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.319233T@ %@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.118841El@{#@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.118818E@#@hXOugH6 cLidJOMd`Mdif`dmdid^J]`dmdid^J]`dmdid^J]`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^J`dmdid^JmY`QOd`JYb/mY`QOd`JYb/mY`QOd`JYb/mY`QOd`JYb//mY`QOd`JYb//mY`QOd`JYb//mY`QOd`JYb//mY`QOd`JYb/QOd`JYb/mY`QOd`JYb/QOd`JYb/mY`QOd`JYb/umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`kfQMmio`kfQMmio`kfQMmio`Q`QkfQMmio`Q`QkfQMmio`Q`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`Mmio`umiQ`QkfQMmio`o` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio` (9FUduǃƒťĹ @ @ @ @ @c)i2`pa Option170d5`Za bcLabel171no sortm7`a#b$k%$Additionalr@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1310933TR@@XOugI6q@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum0710933TR@Please clarify.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1310932E9@3@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1358TR@9@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.121091E@@XOugI6p@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1110833TR@w@XOugI6k@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum07Table6410810TR@=@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1010742E[@@XOugI6i@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1010746TRO@h@XOugI6h@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1010743TR@@XOugI6c@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum07Figure3110715TRN@p@XOugI6b@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.101071TR@I@XOugI6_@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum07Figure3010645TR'@>@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.910623T1@X@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.81066T1@ change to eirpXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.81063E"the" missing:@XOugI6@ cumiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio` umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio`umiQ`QkfQMmio` LVAL l 0 G  { X 3  ^ ;  H% @   @ @ @ @ @ @ @ @ @ Please change this sentence frag. <from> "...shall remove the parent BSID IE frPlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...to the channel indicated in the IE at the appropriate time." "...to the channel indicated in the piconet parameter change IE at the appropriate time."[ChnlChng] Change this sentence frPlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...to the channel indicated in the IE at the appropriate time." "...to the channel indicated in the piconet parameter change IE at the appropriate time."[ChnlChng] Change this sentence frag. "..Please change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from itsPlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent Please change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...to the channel indicated in the IE at the appropriate time." "...to the channel indicated in the piconet parameter change IE at the appropriate time."[ChnlChng] Change this sentence frag. "...after it has performed a PNC channel scan,8.9.5, and Please change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentencePlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentencePlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...to the channel indicated in the IE at the appropriate time." "...to the channel indicated in the piconet parameter change IE at the appropriate time."[ChnlChng] Change this sentence frag. "...after it has performed a PNC channel scan,8.9.5, and ..." "...after it has performed either a PNC channel scan,8.9.5, or a remote channel scan, 8.9.4, and..." The original sentence is too restrictive in its scope and implies that aPlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...to the channePlease change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...to the channel indicated in the IE at the appropriate time." "...to the channel indicated in the piconet parameter change IE at the appropriate time."[ChnlChng] Change Please change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."Change this sentence frag. "...shall remove the parent BSID IE from its beacon..." "...shall remove the parent piconet IE from its beacon..."r 2Jf“ @ @ @ @ @JLabel140iKOption141d LLabel142iMOption14{@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America07Fig. 74132TRJ@Remove SFNext fieldXOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America073.1E6@#@XOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America073.1, Table 6098E?@,@XOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America075.10.2, Fig. 73, 74132E^@w@XOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America075.10.113023EJ@1@XOkk]G6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.1010735T@@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.4.71053334T@n@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.2.1.996910E@Comment via Ari Singer.XOugI6i@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.7.612638Ez@N@ XOugI69@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.10.113114EJ@@ XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.10.313245TR@8@ XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.3.511747E+@ Change to Key Request command.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.3.411737T/@ Eliminate PublicKeyProofLengthXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.3.311710T3@Delete PublicChallengeLengthXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum077.5.3.211638T2@!Delete AuthenticationInfoLengthXOugI6w@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum07FIgure 4011430TR@C@ XOugI6 LVAL l 0 G  { X 3  ^ ;  H%tQ.o@ @StartUpFoChange the title of figure 143 <from> "MSC for PS set inquiry command" <to> "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and managemeChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS set configure command. 3) If one is available join an SPS set ia the PS set configure command. 4) and so on.Missing xrefs to PS mode change command in clause 7. First missing xref is in line 41 and the second missing xref regarding disassoc is at the end of line 45.[PM/CWB] Delete item 3 from this clause. The use of the CWB IE in the wake beacon only works if the sleeping SPS DEV hears the wake beacon and in that case the SPS DEV doesn't need the CWB IE. And in the other case it doesn't matter, because it can't use the info in the CWB IE because it didn't hear it. The simpler solution is to implement the following ruChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS Change the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) Change the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: Change the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS set configure command. 3) If one is available join an SPS set ia the PS set configure cChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to movChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS set configure command. 3) If one is available join an SPS set ia the PS set configure command. 4) and so on.!DZw̕˸>Qsœķø @ @ @ @ @*@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.13.3.1117113E exra "a"drop extra "a"XOvhZA6)@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.13.3.1117118TA@ @ XOvhZA6(@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.13.3.216454EC@change allocation to requestXOvhZA6'@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.3.21446ER@Z@XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.2.313830TR@t@XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.213744TR@?@XOvhZA6$@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.2.313830EY@add the xrefsXOvhZA6 @3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.13.3.416645T@y@XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.2.11387TRO@@XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.2.113819E@ 8@XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.1216141TR@ ~@XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain088.1517220E@ -@XOvhZA6^@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America074.3, Fig.22103TR@ 8@XOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America073.1, Table 6098TR]@ <@XOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America075.8.3128T@Please clarifyXOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America07Fig.64127TRV@?@XOkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America075.1013025TR@@XOkk]G6c />M>0=-=/Yăí     @ @ @ @ @@@ @@@`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola093.2237711TR@ @XOzl^D6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola092.623289E@XOzl^D6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola092.2TR@<@XOzl^D6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola091.7TR@@XOzl^D6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola091.6TR@"@XOzl^D6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.439716TRl@Make the requested change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.339211E4@{#@TXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.339251TR@Make the requested deletion.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 14322321E0@$@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.322041E@Please provide correct xrefs.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.321943TR@Make the requested change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.321941Eu@{#@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.22187TR&@C@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.221730E)@z@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.121640E@{#@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.221631E~@{#@ uXOugH6 LVALb N l 0 G  { X 3  ^ ;  H%tQ.oL(h% @ @ @ @ @ @ @ @ @ @ @@@@66]66b66b66k66k66k 68b68b68b68g6:b6:b6<b6<b6<b 6<b 6<b 6<b 6>b6@b 6@b6@b6@g6@g6@g6B]6B]6B]6B]6B]6B]6Bg6Bg6Bg6Bg6Bg6Bg 6Bg 6Bg 6Bg 6Bg 6Bg6Bg6B6B6BOMStartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121242E@ #@1hXOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121136TRy@ ePlease clarify and if need me rewrite to make the intent clearer.please make the requested spelling change to the word interval. Also make the other requested editorial change as well.Please make the requested change.Please make the requested change.Please make the requested changes.Please make the requested change.Please make the requested change.Please make the requested change.Please make one of the requested changes.Please make the requested change.Please make one of the requested changes.Please make the requested change.Please make the requested change.Please make the requested deletion.Please make the indicated change.Please make the requested change.Please make the requested change.Please make the requested change.Please make the requested change.Please make the requested change and excute the requested Find and change search.Please make the requested change so that the sentence is easier to read and understand.Please make the requested change.Please make the requested changes.Please make the requested change.Please make the requested change.Add the missing MLME primitives regarding piconet services or delete all references to piconet services.Please make the requested deletion.Please make the requested change.Please miStartUpForm&StartUpShowDHeberling, AlleThe sentence ending "...isochronous and asynchronous data types and is designed to support addThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle.[PM/CWB] Delete the CWB entry from the table. It is not needed. The use of the CWB IE in the wake beThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 The sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.c!3DUctɅȓǡƲ @ @ @ @ @ @ @ @ @ @ @ @`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321510TR}@U@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.3.417644TR@{@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.4.4.418212TR}@{@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121651TRY@l@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.3221TRe@{@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.22188E%@{n@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum07Figure 1211427E@4B@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum066.3.24.68622TRR@,@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321541TR@0@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321448TR@@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.7.115540TR@ c@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.12126TR@ @XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1020831TR@ @XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.2.31655TR@ @XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Table 6119810TR0@{1@uXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.41231TR@@XOugH6 LVALv1b N 6Yr`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC000010Tz@A{׏XOyhWD6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822MotorolaCC.1.436627E5@%{@)XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.3.5.129647E@@XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.2.22851315TR@@XOzjZB6`X@`XSame as comment 509 in LB19 (Applicable for 8.13.2 also)PS status bit map has an issue and that is, let's say DEV-A and DEV-B aremembers of the same piconet managed by a PNC. If DEV-A sees the PS-status-bit corresponding to DEV-B as set in the beacon from PNC (meaning DEV-Bis in power save mode), but in the same superframe receives a frame (directed or not) from DEV-B, can DEV-A assume that the DEV-B is in AWAKEstate for that superframe? I think that should be allowed. it helps certainBC/MC traffic transactionsSuggested Remedy:1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. TSame as comment 509 in LB19 (Applicable for 8.13.2 also)PS status bit map has an issue and that is, let's say DEV-A and DEV-B aremembers of the same piconet managed by a PNC. If DEV-A sees the PS-status-bit corresponding to DEV-B as set in the beacon from PNC (meaning DEV-Bis in power save mode), but in the same superframe receives a frame (directed or not) from DEV-B, can DEV-A assume that the DEV-B is in AWAKEstate for that superframe? I think that should be allowed. it helps certainBC/MC traffic transactionsSuggested Remedy:1.If a DEV in in PSPS (SPS) mode in a superframe, but transmits a frame theDEV shall consider itself in AWAKE state and hence may enter SLEEPstate only after another succesful transaction of power-save-commands(s)with PNC.AND2. The DEV shall enter SLEEP state only at the start of superframefollowing the succesful transaction of power-save-commands(s) with PNC.Response:ACCEPT IN PRINCIPLE. 1. A DEV in PSPS keeps it s GTS and may transmit in them. This does not imply that the DEV wishes to change power save mode. 2. It is specified in 13.1 that a DEV may enter the SLEEP state only after having received an ACK from PNC on a PS mode change command with the PS Mode set to PSPS.Commentor's response (LB22)The comment exposes an ambiguity in the interpretation of PS-status bits andframe transmissions by a PSPS DEV as read in the draft (D11). But the resolution is justan explantory to the commentor with no clarification in the draft. Hence the ambiguityin the draft is still left remaining. LVAL @ @ @ @ @ @ @ @ @Q]Q]Q]Q]Q]Q]Q] Q] Q]Q]QbQbQbQbQbQbQbQbQb Qb Qb Qb Qb QbQbQbQgQgQgQgQgQgQgQgQgQg Qg Qg Qg Qg QgQgQkQkQk Qk QQQQ Q Q QQQQQQQ QQQQQQQ Q Q Q Q QQQQQQ Q Q QQQQQQQQ Q Q QQQQQQQQ QQ Q m]m]m]m] m] m]mbmmmmmmmmmmmm m mmm m mmmm/m/m/m/mi] mikmikmikmikmikmikmikmik mik mik mikmikmimimimi mi mimimimimimi mi mi mi mimimimimimi mi mi mimimimimimimimimi mi mimimimimi mi mi mi mimimimimimimimimimimi mi mi mimimimimited deletion.Please make the requested change.Please make the requested clarification.Please make the requested change.Please make the requested change.I suggest the Editor delete the entire paragraph or add something relevant to the draft.I suggest ""...isochronous and asynchronous data types.".Change 'should' to 'shall' and note that this is only necessary when commands are not allowed in the CAP.Add text: "A DEV that misses its wake beacon shall listen to the following beacon".Add text: "When a DEV is disassociated, the PNC shall reset its biLeChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DLines 53-54 on pp-178 with lines 1-3 on pp-179 create an unnecessary special case for starting backoff algorithm at the start of CAP. The save is not worth the special case at the lowest level of MAC where Backoff algo is run. Added to that, applicability of this special case getLines 53-54 on pp-178 with lines 1-3 on pp-179 create an unnecessary special case for starting backoff algorithm at the start of CAP. The save is not worth the special case at the lowest level of MAC where Backoff algo is run. Added to that, applicability of this special case gets narrowed by another level by the probability of not-correctly-receiving the beacon and/or the last extended beacon by a DEV. Although this specail case has a "may" in it and hence does not enforce its applicability, it is worth the space in the standard given the above reasoning. LVALv1b N {tmf_XQJC<5.'  xqjc\UNG@92+$ | u n g ` Y R K D = 6 / ( !    y r k d ] V O H A : 3 , %     } v o h a Z S L E > 7 0 ) "    O@7@)XOq]H6E`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CORP112.7.1TR@`@)XOq]H6n.Please make the requested clarification and correction.Please make the requested clarification and change.Please make the indicated change.Rename error code 7 to 'destination in power save mode'Change piconet type codes to: 0 -> Independent or parent piconet 1 -> Dependent piconet 2-255 -> ReservedDelete the sentence "The stream termination field...".Remove 'stream termination', pack all fields to the right and let b7 be reserved.Change Figure 38 and line 24 from 'cycle' to 'number'.Remove "HIBERNATE" from the first sentence.Please make the requested clarification and correction.Please make the requested clarification and change.Please make the indicated change.Remove 'NEW' from PSSetOperation Valid Range column.Change description to: "The number of TUs available to the requesting DEV for allocation"Valid range for AvailableNumTUs is 0-255.Add parameter to MLME-CREATE-ASIE.confirm: "ASIE-index", integer type, range is application specific.Add parameter to MLME-CREATE-ASIE.request: "ASIE-index", integer type, range is application specific.Remove second sentence about ALREADY_STARTEDPlease make the indicated corrections.I suggest "An unsupported data rate...".I suggest adding RFC XXX to Annex F or the Bibliography.Change "There" to "These at beginning of sentence.Remove from table and Challenge.request command.remove the PSSetOperation from the primitive.I suggest either "...allowed to use an access control list (ACLs)..." or "...allowed to use access control lists (ACLs)...".I suggest "affect"; affect: to influence and effect: to cause. Please make the change globally.I suggest the Editor add the period.I suggest "A channel time allocation..."; change allocations to singular.I suggest "A parameter..."; adding a space.I suggest "IETF RFC 2459:..."; drop the stray "1" character.Repair the text to accurately reflect the defined operation of any current or future security suic  ]k k] ]    ] ] ]                      k `Table-66. The cell corresponding to "Hibernate in wake superframe" column and "Beacon" row contradicts the text on pp-220, lines36-41 where the hibernating DEVs are aTable-66. The cell corresponding to "Hibernate in wake superframe" column and "Beacon" row contradicts the text on pp-220, lines36-41 where the hibernating DEVs are allowed the liberty of sleeping through "any" beacon until they themselves change over to ACTIVE state (and it should be within ATP to retain the membership of Piconet) LVALg<Y3 o t Q 5  / ` 6  yV3` j1\srtUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.5.1.118814TR@ >@)XOugH6d`X@`X@orm&StartUpShowDHeberling, Allenaheberling40Delete the last sentence of the paragraph on page 187 line 38-40In the first sentence on line 21-22, replace "probe command" with "piconet services command".remove (or possibly do what it suggests!)Remove this subclause and references to ASIE from the draftChange the referred entry from "AWAKE" to "May sleep"Change "SIFS" to "BIFS" in Lines 53-54 on pp-178 and lines 1-3 on pp-179Insert "In addition, " before "If the DEV sees a shutdown IE ...."Please make the requested clarification and correction.Please make the requested clarification and change.Please make the indicated change.Rename error code 7 to 'destination in power save mode'Change piconet type codes to: 0 -> Independent or parent piconet 1 -> Dependent piconet 2-255 -> ReservedDelete the sentence "The stream termination field...".Remove 'stream termination', pack all fields to the right and let b7 be reserved.Change Figure 38 and line 24 from 'cycle' to 'number'.Remove "HIBERNATE" from the first sentence.Please make the requested clarification and correction.Please make the requested clarification and change.Please make the indicated change.Remove 'NEW' from PSSetOperation Valid Range column.Change description to: "The number of TUs available to the requesting DEV for allocation"Valid range for AvailableNumTUs is 0-255.Add parameter to MLME-CREATE-ASIE.confirm: "ASIE-index", integer type, range is application specific.Add parameter to MLME-CREATE-ASIE.request: "ASIE-index", integer type, range is application specific.Remove second sentence about ALREADY_STARTEDPlease make the indicated corrections.I suggest "An unsupported data rate...".I suggest adding RFC XXX to Annex F or the Bibliography.Change "There" to "These at beginning of sentence.Remove from table and Challenge.request command.remove the PSSetOperation from the primitive.I suggest either "...allowed to use an access control list (ACLs)..." or "...allowed to use access control lists (ACLs)...".I suggest "affect"; affect: to influence and effect: to cause. Please make the change globally.I suggest the Editor add the period.I suggest "A channel time allocation..."; change allocations to singular.I suggest "A parameter..."; adding a space.I suggest "IETF RFC 2459:..."; drop the stray "1" character.Repair the text to accurately reflect the defined operation of any current or future security suite.Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4.4.1, M 13.2 pseudo-static isochronous steam, 8.4.4.1, OChange "The protocols have been reThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resoThis comment concerns Figure 114, Figure 115 and Figure 116. "Evaluate request", "Allocate resources" and "Build beacon" is unnecessary information. Delete all these. Rename "Check resources" to "Resources available". The reason is that they are in a condition symbol and not in a task symbol, so the condition for approving the request is that resources are available./KO LVAL$ $  0 N ]l{v`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.520737TRQ@ @XOugH6u`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.539550TR@@)XOugH6t`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.5.215237TR@9@)XOugH6s`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.32219TR@@ XOugH6r`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.32217E`@5{ remove!XOugH6q`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121619EN@T{&@)XOugH6p`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121542TR@@ XOugH6o`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121549TRB@S{a@)XOugH6n`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.11.121139TR)@R{@)XOugH6m`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.420636E4@Q{XOugH6l`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors t[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting undiscussed ad-hoc inventions into the draft. If you really want to wake up a sleeping DEV at some unknown time in the future, we could consider having a new command to set the PCTM bit. One way would be to add a DEVID to PS mode change. If (operation == ACTIVE && dev != UNASSOC) set PCTM(dev)./KO LVALv1b N  @ @ @ @ @ @ @ @ @Q]Q]Q]Q]Q]Q]Q] Q] Q]Q]QbQbQbQbQbQbQbQbQb Qb Qb Qb Qb QbQbQbQgQgQgQgQgQgQgQgQgQg Qg Qg Qg Qg QgQgQkQkQk Qk QQQQ Q Q QQQQQQQ QQQQQQQ Q Q Q Q QQQQQQ Q Q QQQQQQQQ Q Q QQQQQQQQ QQ Q m]m]m]m] m] m]mbmmmmmmmmmmmm m mmm m mmmm/m/m/m/mi] mikmikmikmikmikmikmikmik mik mik mikmikmimimimi mi mimimimimimi mi mi mi mimimimimimi mi mi mimimimimimimimimi mi mimimimimi mi mi mi mimimimimimimimimimimi mi mi mimimimimiich time all the sleeping DEVs, except those in HIBERNATE mode, are expected to be awake and be able to receive. Wake beacons contains in addition to other fields/elements that can be present in beacons transmitted at other times. The BC/MC traffic in a piconet shall always be in the superframe in which a wake beacon was transmitted by the PNC.[NOTE: If beacon transmission time is defined (BTT), this can be defined as WBTT which makes the text flow naturally since wake beacon referred here is mostly to do with the time of its transmission than its contents]Change the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode c[PNC Scan] Implementation wise it is preferrable to just stop beacon transmission and then start at a later time continuing from where it stopped. The reason we force the PNC to upgrade the timetoken for silent beacons is that a consistent increment is needed for SEC DEVs. On the other hand, if[PNC Scan] Implementation wise it is preferrable to just stop beacon transmission and then start at a later time continuing from where it stopped. The reason we force the PNC to upgrade the timetoken for silent beacons is that a consistent increment is needed for SEC DEVs. On the other hand, if the PNC wants to scan it would be better to have the whole piconet silent. Unfortunately the PNC cannot just remove the CTA since that would cause dependent networks to cease operations on the current channel. A better solution would be to announce when scan starts and how long it will last./KO HLVALU @ @Change pAdd two subrequirements to MLF13. 13.1 dynamic isochronous strAdd two subrequirements to MLF13. 13.1 dynamic isochronous sPlease make the Please make the requested change.Please make the requested change.Add two subrequirementPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochrPlease make the requested change.Add two subrequirements tPlease make the requested change.APlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4.4.1, M 13.2 pseudoPlease make the requested change.Add two suPlease make the requested change.Add two subrePlease make the requested change.Add two subrequPlease make the requested change.Add two subrequiremenPlease make the requested change.Add tPlease make the requested change.AddPlease make the requested change.Add two sPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream,Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream,Please make the requested change.Add twPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochroPlease make the requested change.Add two subrequirPlease make the requested change.Please make the requested change.Add two subrequiPlease make the requested change.Add two subrequiremePlease make the requested change.Please make the requested change.Please make the requested change.Please make the requested change.Add two subrePlease make the requested change.Add two subrequiremePlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamicPlease make the requested change.Add two subrequiremPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4Please make the requested change.Add two subrequiremePlease make the requested change.Please make the requested change.Add two subrequiPlease make the requested change.Add two subrequiremePlease make the requested change.Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4.4.1, M 1Please make the requested change.AdPlease make the requested change.APlease make the requested change.Add two subrequirements to MLF13. 13.1Please make the requested change.Add two sPlease make the requested change.Add two subrequPlease make the requested change.Add two subrequirements to MLF13.Please make the requested change.Add two subrequirements to MLF13.Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic iPlease make the requested change.APlease make the requested change.Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamicPlease make the requested change.Please make the requested change.Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamicPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4Please make the requested change.AdPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamiPlease make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous Please make the requested change.Add two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4.4.1, M 13.2 pseudo-sPlease make the requested change.LVALI suggest: Draft Standard for Information technology- Telecommunications and information exchange between systems- Local and metropolitan area networks Specific requirements- Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs) Please make the change globally. Additionally, and in terms of the LB19 CommentID: #10 rejection, I understand the PAR issue but I think this is a clear editorial issue and we have WG precedents to apply the editorial suggestion. Here are some issues to consider in this rebuttal 1. The 802.15.3 PAR is incorrect and is in conflict with itself and should state the previously mentioned item in the title section i.e., "2. Assigned Project Number [P802.15.3]" or section 4 should state "...Part 15.3...". http://grouper.ieee.org/board/nescom/802-15-3.pdf 2. An example is the 802.15.1 PAR which TG3 copied and is why you have the error in the first place :). When 802.15.1 got to Sponsor Ballot the PE said 15.1 was ok cuz (a) we had a corrigendum: http://ieee802.org/secmail/msg00600.html and (b) implicitly it was necessary to add the dot level based on the 15.2, 15.3, 15.4, etc. approvals. http://ieee802.org/15/par.html 3. Specifically, having the 802.15.1(TM)-2002 published sets a precedent as our PAR says "Part 15..." but we are published with "Part 15.1..." http://grouper.ieee.org/board/nescom/802-15.pdf Note: 802.15.4/D17 is in Sponsor Ballot with "Part 15.4..." 4. If you release the 15.3 Draft to Sponsor Ballot there might be an issue and someone might object BUT I think going forward w/ the title as-is is a bad idea. For example the 3rd of the 802 five criteria "Distinct Identity" will be problematic if the IEEE titles are NOT distinct and/or inconsistent in the WPAN Standards Family: http://ieee802.org/3/rules/rules.html#P72 Note: I applied (Session #20) the latest edit to the 802.15.3a DRAFT PAR because of this very issue and after careful review of other approved A LVAL N  ЅυυυυJ: 4  e ;  N L A +1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC000010Tz@T% ?XOyhWD6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822MotorolaCC.1.436627E5@Q%{@@)XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.3.5.129647E@i@ xXOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola1010.2.22851315TR@@XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.82332122EK@u%@@\)XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.623151T>@t%Change 'should' to 'shall'XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola099.2.423120T@k@[)XOzjZB6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.6.219746E#@q%9@V)XOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola088.2.416814EEditors Note in the text.&@U)XOzjZB6 `X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822Motorola077.5.4.414518E@9@S).Create a summary table of PHY parameters instead of spreading them all over the PHY clause(s).Remove blank between period and last word in sentence ('key').Change 'should' to 'shall' and note that this is only necessary when commands are not allowed in the CAP.Remove this subclause and references to ASIE from the draftChange the referred entry from "AWAKE" to "May sleep"Change "SIFS" to "BIFS" in Lines 53-54 on pp-178 and lines 1-3 on lt PHY Layer Standards and their titles: http://ieee802.org/secmail/msg02824.html In terms of the next step I suggest you ask Jennifer Longman what her opinion is i.e., leave as-is, apply edit, submit a corrigendum to the 802.15.3 PAR, etc. Finally, I think just from a publishing and distribution point of view it will become confusing - make the edit. If the Editor or Chairs need to change the PAR then please do so, however, the approved IEEE Std 802.15.1-2002 states "Part 15.1" and the PAR does not. It was not an issue for RevCom and the StdBD so it should be an easy edit to apply to keep our family of standards consistent. LVAL N 8  K i _ q llH%tQ.oL(h% @ @ @ @ @ @ @ @ @ @ @ @[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that i[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable and moving devices within or entering a personal operating space." is gramatically incorrect.Again, the text "...20 Mb/s is proposed to be the lowest rate..." and the text on the next page, pg 2, ln 14 "...20 Mb/s or more..." are from the PAR but Clause 11, Table 118, pg 313, ln 14 states "...11 Mb/s...". It is very likely that this inconsistancy (PAR vs. Draft) issue will come up in Sponsor Ballot. A parallel PAR change now will add mimimal to no delay to the project BUT RevCom can add 3-6 months!The sentence "Compatibility and coexistence criteria were included in the proposal evaluations." is vague. The IEEE does not mandate the use of CFAs, CFPs, evaluations, and down selections so to say "...included in the proposal evaluations." does not make sense for non-IEEE 802.15 members.Change of GTS into CTA from D11 to D14 in clauses 5, 7 & 8:AT many places in clause-8, this has caused lot of confusion.For example pp-188, ln-17[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard defines t[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate ch[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed [SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.LVALË A Same as comment 513 in LB19Comment:same as comment #536 in LB12ORIGINAL COMMENT (LB12)If SA is broadcast and anybody could start tx, how's collision handled?What is the point in getting devices to collide here instead of makingthis MTS part of CAP and letting devices freely use CAP as alreadydefined. This is useless and adds unnecessary complexityORIGINAL SUGGESTED REMEDY (LB12): Remove lines 8:22 on page 151 and all references to "MTS/GTS with BC/MC-SA"from the draftResponse: REJECT. The slotted aloha access method is used to provide access to theseslots just as CSMA/CA is used in the CAP. The TG has decided to allow bothaccess methods, CSMA/CA in the CAP and slotted aloha in the MTSs so thatthe 802.15.3 MAC is capable of supporting different types of PHYs.REBUTTAL (LB19):The response does not resolve the issue of having COLLISION basedtransmissions under COLLISION FREE PERIOD, instead of making this partof CAP.I do not see 802.15.3 PHY or applications listed in PAR requiring it.I do not see how CSMA/CA mechanism used in CAP and TDM mechanism used inCFP fail in achieving whatever the slotted-aloha cheme is achieving.I do not see any reason or justification to add extra complexityresulting from having one another channel access mechanism. Suggested Remedy:Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Response:ACCEPT IN PRINCIPLE. Add new subclause 11.2.10,  Channel access methods with text  A PNC-capable DEV compliant to this standard shall allow the use of the CAP for contention based access for association, data and commands, {xref 7.3.1} when using the 2.4 GHz PHY. A DEV compliant to this standard shall support the use of the CAP when using the 2.4 GHz PHY. Use 1 bit from the reserved bits to the  Piconet mode field ,  MCTAs used with definitions  The MCTAs used bit shall be set to 1 if the PNC will be using open or association MCTAs. Delete the sentence on page 111, lines 1-2,  LVAL v1b N Цh;h U  c =  v ?  W | T & X-]0mx6ri066]66b66b66k66k66k 68b68b68b68g6:b6:b6<b6<b6<b 6<b 6<b 6<b 6>b6@b 6@b6@b6@gAdd two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4.4.1, M 13.2 pseudo-static isochronous steam, 8.4.4.1, ORename error code 7 to 'destination in power save mode'Delete sentence on page 216 line 19.Change to: "The system wake beacon interval shall not be less than 4 and not greater than 255".Insert text: PNC shall broadcast the piconet parameter change information element, 7.4.6, with the change type set to CHANNEL...Change to: (or new frame if the failed...Always announce CTR-Interval changes. Remove the words "if any DEV is in power save mode"Add "and of all subrate streams" to the sentence on line 14.Delete the last sentence of the paragraph on page 187 line 38-40In the first sentence on line 21-22, replace "probe command" with "piconet services command".remove (or possibly do what it suggests!)Change piconet type codes to: 0 -> Independent or parent piconet 1 -> Dependent piconet 2-255 -> ReservedDelete the sentence "The stream termination field...".Remove 'stream termination', pack all fields to the right and let b7 be reserved.Change Figure 38 and line 24 from 'cycle' to 'number'.Remove "HIBERNATE" from the first sentence.Remove "Otherwise this field shall be ignored upon reception"Remove 'NEW' from PSSetOperation Valid Range column.Change description to: "The number of TUs available to the requesting DEV for allocation"Valid range for AvailableNumTUs is 0-255.Add parameter to MLME-CREATE-ASIE.confirm: "ASIE-index", integer type, range is application specific.Add parameter to MLME-CREATE-ASIE.request: "ASIE-index", integer type, range is application specific.Remove second sentence about ALREADY_STARTEDPlease make the indicated corrections.Change "The protocols have been reviewed by" to "The protocols have been reviewed by (whomever reviewed these protocols)"Create a summary table of PHY parameters instead of spreading them all over the PHY clause(s).Remove blank between period and last word in sentence ('key').Change 'should' to 'shall' and note that  If the CAP end time indicates no available time and no message types are permitted during the CAP, then MTSs are implied. (note this deletion is in response to CID 407).Expand MLF13 in the PICs (note this will become MLF13.1 and MLF13.2 due to another comment.)MLF13.1; Open and association MCTA operations; 8.4.4.4, 8.4.4.5; O.1MLF13.2; Regular MCTA operations; 8.4.4.4; M{ed. note: the CAP stuff is like MLF13.3 now}Commentor's response:Response to this comment do not address the core issue of an additional access mechanism(MTS and slotted aloha) in the standard. The proposal does not justify why they are needed in802.15.3. Hence the resolution is unacceptable. LVAL pZ G  { X 3  ^ ;  H%tI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), acI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) anI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause 4 then they should be found in the draft. Also, I submit that for "DLL" it should be "Dynamic-Link Library" not "Data Link Layer". Finally, if you want to create an acroynm or abbreviation for "Data Link Layer" use "Layer 2" or "L2".Again, change sentence to read "The area of overlapping coverage between the two piconets may vary between congruency with the parent coverage area to mostly non-overlapping."; change "congruent" to "congruency".To minimize the entries into IEEE 100, I suggest that we standardize on the definition of "interoperability". I suggest the Editor use the P802.15.2/D6 definition: "interoperable: The ability of two systems to perform a given task using a singlI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in ClausI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globallI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hypI suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally. LVAL '=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Giff[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed about termination via the NULL CTA, it's informed via the CTR response from the PNC. Ref Fig 120, page 193 and 8.3.4 page 176 line 16-17./KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request Even if not, it's easier to call with an index when you want to remove the IE. /KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request Even if not, it's easier to all with an index when you want to remove the IE. /KO[Assoc] Capability Field is not part of the DEV association IE. Consequently, delete this parm from the MLME-DEV-ASSOCIATION-INFO.indication pri[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list sin[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed about termination via the NULL CTA, it's informed via the CTR response from the PNC. Ref Fig 120, page 193 and 8.3.4 page 176 line 16-17./KO[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed abo[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either ad[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parame[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this paramet[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in th[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list. LVAL 6Yr`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Please make the requested change. Its just an editorial but it will make it easier for Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primitive is used to inform the SrcDEV DME that the MLME has received a channel time response command indicating that the channel time that was previously allocated has been terminated by the PNC or the TrgtDEV. It may also be used to indicate to the TrgtDEV DME that the MLME has seen a null-CTA in the beacon with its DEVID, BcstId or McstID as the destination.Again, I suggest adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells. Please make the change globally.I suggest "...being updated, Clause 10."; that is if you mean "10" refers to Clause 10. Please make the change globally. Note 1: that this repeats further in thePlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primitive is used toPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change senPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the prPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between thPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between tPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel TPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primiPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command. LVALrLN f  ̋̋̋̋̋̋L  \ g % a ~XEiZ(h:lAhowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.5.4.414515E6@~% [Assoc] This should be obvious, but the fact is that a dumb PNC implementation can c[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe requests are listed in Table 57 ." "...probe requests are listed in Table 57."Change the title "MSC [Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe r[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. [Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KO[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe requests are listed in Table 57 ." "...probe requests are listed in Table 57."Change the title "MSC showing requesting information only using probe command" "MSC of DEV requesting information via the probe command"[Frag] [Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe requests are listed in Table 57 ." "...probe requests are listed in Table 57."Change th[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM.[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe [Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe requests are listed in Table 57 ." "...probe requests are listed in Table 57."Change the title "MSC showing requesting information only using probe command" [Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOChange the sentence frag. "...probe requests are listed in Table 57 ." "...probe requests are listed in Table 57."Change the title "MSC showing requesting information only using probe command" "MSC of D[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. L[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS[Assoc] This should be obvious, but the fact is that a dumb PNC implementation can create problems for other DEVs! Examples are PS status and PCTM. Let's plug this one/KOLVAL  a gC Y { { q X n yEZlSame as CID 410 in LB22Original comment:The new field "Num max frame size" is mostly useless. What if all the framesare (aMaxFrameSize-1) octets long? Instead of that, it is useful to includethe total number of octets as sum of number of octets in the payload of all frames sent in the dly-ack-window. this total number of octets is helpfulin buffer management at the receiver which is supposed to hold all theframes (in some corner cases) until a delayed-ack-frame is sent.Suggested Remedy:1. Remove "Num max frame size" from Figure-15 and all its references from the fraft2. Include total number of octets as sum of number of octets in the payload of all frames sent in the delayed-ack-windowResponse:REJECT. Two variables are needed, the total amount that can be sent as well as the number of frames that the destination DEV is able to handle. The number of frames is important because there are physical limitations in the Dly-ACK generation. The other reason is that there are physical limitations in the buffer implemention, e.g. addressing.Commentor's response:The commenter agrees that there are two variables needed and it is evidentby the suggestion. But what is not clear is the intention in providing number of frames of size aMaxFrameSize, instead of providing a direct bound of max on totalnumber of octets that is entertained in the burst. The implementations can makeuse of this information in a useful way while the current info does not given anycluse on the size of the (MAxNumFrames - NumMAxFrameSize) of the frames. How doyou expect the implementations to guess those sizes? If all of them are(aMaxFrameSize-1), they are not indicated to the rx-DEV in this frame and the rx-DEVis supposed to handle them properly. In the worst case if all of the NumMaxFrames areof the size (aMaxFrameSize-1), then NumMAxFrameSize will be indicated as zero althoughthe rx-DEV has the pain of dealing with these mega-burst!! LVAL  @ @ @ @ @ @ @ @Change this sentence frag. <from> "...in the superframe of the CTR status IE announcemeChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/PM] CTR may be refused because destinatChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA StChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. ConsequentlyChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to Change this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLMChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."[ASIE] OUI may be sChange this sentence frag. "...in the superframe of the CTR status IE announcement." "...in the superframe of the CTA status IE announcment, (xref: CTA Status IE)."LVAL  a C ͋ R R/ //////  [ 8 i F # r G $ l I & iF"hE tUpShowDsame as CID 414 in LB19Original comment:In this sentence what does "multiple beacons" actually mean? Multiple beacons in the same superframe, similar to fragementing beacon, OR IEbeing present in beacons sent at different TBTT but each time with differentcontents of association info. I think what is intended is to say thatif there are too many assoc/disassoc, the beacon at current TBTT may notbe big enough to carry them all, so the remaining Dev-assoc-IEs will befilled into the next beacon sent at next TBTTSuggested Remedy:If intended, do NOT allow fragementation of beacon. Alter the sentence inln42:43 to mean that the PNC may send IE corresponding to a recent assoc/deassoc in the beacon at next TBTT if the current beacon does nothave space for it.Response:ACCEPT IN PRINCIPLE. Delete the sentence "The PNC may use multiple beacons to broadcast successive DEV association IEs if too many DEVs are associating than will fit in a single beacon.." as it is confusing and does not add any new information. The PNC is able to choose when it sends any IE.Commentor's response (LB22)The response addresses the issue only partially. For interpretations towardsconformance, "The PNC is able to choose when it sends any IE" is not correct The interpretation by vendors can go either way. that is, a group of implementors might expect the Dev-Assoc-IE contianing the recently associated DEVs to appear immediately after assoc while the rest might tolerate it appearing anytime. Hence the inclusion of the suggested remedy is required. I have rephrased the same in thefollowing text for editor's peruse (Applicable after the removal of sentence asin the response)."The the DEV association IE corresponding to an association shall be included in thebeacon sent at the start of immediate next superframe, excepting the case where thatbeacon is already at its maximum allowed size where the inclusion of IE is delayeduntil the space in the beacon permits the same." LVAL r{tmf_XQJC<5.'  xqjc\UNG@92+$ | u n g ` Y R K D = 6 / ( !    y r k d ] V O H A : 3 , %   Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC sDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen to system wake beacons and CTAs where its DEVID is indicated as the destination."Please referDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen to system wake beacons and CTAs where its DEVID is indDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen toDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen to system wake beacons and CTAs where its DEVID is indicated as the destination."Please refer to example in 02276r13P802-15_TG3-commentsD11_KO.doc page 5 for correct syntax. Replace both association and CTR symbols.Please refer to example in 02276r13P802-15_TG3-commentsD11_KO.doc page 5 for correct synDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen to system wDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first senteDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC sDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC sDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel timeDelete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2) LVAL Ѝ8 V 3  p  n I &  g D ! In figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets iIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command canIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calls toIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same fIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The LenIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculationIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create aIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. TheIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of fIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change. LVAL 6Yr[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The last sentence is what happens with asynchronous data if no CTA arrives before the SDU timeout. In the case of ISOCH-DATA, you do MLME-CREATE-STREAM first./KO[CTA] The last sentence "Channel time requests that are ACKed are valid until the next channel time request is made" is only true for asynchronous data, and only if the TrgtIdList bit is set. In all other cases it's false./KO[PiconetService] The probe isn't used for service response due to its potential length. The fragmentable piconet services command shall be used. /KO[PNC_HndOvr] Old MSC. Please use the correct one in 02/276r13. The Optional ACL handover is not only between MLME and DME. Besides the symbol for sub-MSC is wrong. The text referring to the ACL handover is missing. There is no MSC for cancellation./KO[PNC_HndOvr] The two sentences on line 20-22 belongs in 8.2.6, where they are missing. The first sentence should be changed to "handover announcement" and be kept here./KOSee CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.Table-66. The cell corresponding to "Hibernate in wake superframe" column and "Beacon" row contradicts the text on pp-220, lines36-41 where the hibernating [CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The last sentence is what happens with asynchronous data if no CTA arrives before the SDU timeout. In the case of ISOCH-DATA, you do MLME-CREATE-STREAM first./KO[CTA] The last sentence "Channel time requests that are ACKed are valid until the next channel time request is made" is only true for asynchronous[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The last sentence is what happens with asynchronous data if no CTA arrives befor[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find t[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval i[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot [CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in [CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO LVAL [Assoc] Please change this sentence frag. <from> "...,accept the DEVID as its address for all future communications." <to> "...accept the DEVID fo[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported in capability",[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the se[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." T[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all f[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported in capability", "PSPS supported in capability", and "Hibernation supported in capability". These modes are no longer indicated in the capability fields.Change this sentence frag. "...SPS sets to transfer." "...PS sets to transfer." The reason for the requested change is because the power managem[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported in capability", "PSPS supported in capability", and "Hibernation supported in capability". These modes are no longer indicated in the capability fields.Change this sentence frag. "...SPS sets to transfer." "...PS sets t[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported in capability", "PSPS suppor[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all fu[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communicatio[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment.[PM] Remove from the table all the entries for "SPS supported [Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence les[Assoc] Please change this sentence frag. "...,accept the DEVID as its address for all future communications." "...accept the DEVID for all future communications." This change will make the sentence less confusing. Address implies a 48bit MAC address and not the 8 bit assignment. LVALl{ @ @ @ @ @ @StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.9.520737TRQ@ @XOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-121The PNC may request that a DEV in power save Add sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE modeAdd sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode change, probe or other command to the PNC before its ATP expires."8.13.1 page 216 line 22. (for PSPS) 8.13.2.2 page 217 line 39. (for SPS) 8.13.3 page 221 line 2. (for HIBERNATION) Add "with the PS Mode field set to ACTIVE and the TrgtID set to its own DEVID" Change Figure 146, page 224. Add param TrgtID=SrcID to MLME-PS-MODE-CHANGE.req and to PS mode change commandThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE mode by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to it's own DEVID. A power save DEV that wakes up and finds its bit set in the PCTM shall switch to ACTIVE mode and remain ACTIVE for at least the CTRResponseTime indicated in the beacon. A DEV may request that the PNC sets the PCTM bit for another DEV by sending the PS Mode change command with the PS Mode field set to ACTIVE and the TrgtID field set to the DEVID of the peer DEV it wiAdd sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode change, probe or other command to the PNC before its ATP expires."8.13.1 page 216Add sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode Add sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode Add sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode Add sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode change, probe or other command to the PNC before its ATP expires."8.13.1 page 216 line 22. (for PSPS) 8.13.2.2 page 217 line 39. (for SPS) 8.13.3 page 221 line 2. (for HIBERNATION) Add "with the PS Mode field set to ACTIVE and the TrgtID set to its own DEVID" Change Figure 146, page 224. Add param TrgtID=SrcID to MLME-PS-MODE-CHANGE.req and to PS mode change commandThe PNC may request that a DEV in power save mode switches to ACTIVE mode after its next wake beacon. In this case, the PNC shall set the bit for the DEV it wants to wake up in the PCTM IE. The bit shall be set to 1 until the power save DEV informs the PNC that it's switching to ACTIVE modAdd sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode change, probe or other command to the PNC before its ATP expires."8.13.1 page 216 line 22. (for PSPS) 8.13.2.2 page 217 line 39. (for SPS) 8.13.3 page 221 line 2. (fAdd sentence: "The PNC shall provide enough assigned MCTA or open MCTA for the DEV in HIBERNATE mode that it is able to send a PS Mode change, probe or other command to the PNC before its ATP expires." LVALz%%%%%%%%%%%%%%%%[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake supe[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no space for all MCTA, or the PNC may use another predictable cyclic allocation scheme in which case the PSPS DEVs will know when the next MCTA occurs/KO[PM] Small changes to support new TrgtID field in the PS Mode change command. Editorial: Switching to ACTIVE is th[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so t[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so t[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no space for all MCTA, or the PNC may use another predictable cyclic allocation scheme in which case the PSPS DEVs will know when the next MCTA occurs/KO[PM] Small changes to support new TrgtID field in the PS Mode change command. Editorial: Switching to ACTIVE is the same procedure regardless of PS mode. Maybe lift out to the general clause?/KO[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simpl[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no space for all MCTA, [PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no space for all MCTA, or the PNC may use another predictable cyclic allocation scheme in which case the PSPS DEVs will know when the next MCTA occurs/KO[PM] Small changes to support [PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no [PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the syste[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in [PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload i[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no space for all MCTA, or the PNC may use another predictable cyclic[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no s[PM/MCTA] Just like with SPS, PSPS DEVs needs an MCTA to change modes when they wake up. I chose the wording "should" because there may be overload in the system wake superframe so there is no space for all MCTA, or the PNC may use another predictable cyclic allocation scheme in which case the PSPS DEVs will know when the next MCTA occurs/KO LVALaz%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%  q 6 j E " | C Change the title of figure 143 <from> "MSC for PS set inquiry command" <to> "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and managemeChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS set configure command. 3) If one is available join an SPS set ia the PS set configure command. 4) and so on.Missing xrefs to PS mode change command in clause 7. First missing xref is in line 41 and the second missing xref regarding disassoc is at the end of line 45.[PM/CWB] Delete item 3 from this clause. The use of the CWB IE in the wake beacon only works if the sleeping SPS DEV hears the wake beacon and in that case the SPS DEV doesn't need the CWB IE. And in the other case it doesn't matter, because it can't use the info in the CWB IE because it didn't hear it. The simpler solution is to implement the following ruChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS Change the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) Change the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: Change the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS set configure command. 3) If one is available join an SPS set ia the PS set configure cChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to movChange the title of figure 143 "MSC for PS set inquiry command" "MSC for PS set information request command" Also it would make more sense to move Figure 143 to just before Figure 140, since the text in Clause 8.13.2.1 &2 describes the SPS set creation and management as being: 1) query PNC as to whether there are existing SPS sets via the PS set information request command 2) If one isn't available create/join an SPS set via the PS set configure command. 3) If one is available join an SPS set ia the PS set configure command. 4) and so on. LVAL ДΡf-  u R - s :  g D  T  u R - nK(!f @StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321510TR}@ U@hXOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.3.417644TR@ {@hXOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "folloreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Completely remove the NTRUEncrypt security suite from the draft specification until such time that the evolving NTRUEncrypt scheme is stable enough for relaible commercial delopyment.The text must be modified to address the correct issue. That issue is the bindinreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Completely remreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Completely remove the NTRUEncrypt security suite from the draft specification until such time that the evolving NTRUEncrypt scheme is stable enough for relaible replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Completely remove the NTRUEncrypt security suite from the draft specification until such time that the evolving NTRUEncrypt scheme is stable enough for relaible commercial delopyment.The text must be modified to address the correct issue. That issue is the binding of a DEV's identity to its public key, then the subsequent addition of the DEV's public key, or other representation into the ACL to control future group membership in the piconet.The PNC or another DEV shall request that each DEV with which it has authenticated (previously authentreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wakreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons witreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replacreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon" LVAL Ѕ0000000000000000000000000000000000000000000 vS)   n  m J '  v S (  qM*J'daheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.121548E@$@3hXOugH6StartUpForm&StartUpShowDHeberlThe sentence ending "...isochronous and asynchronous data types and is designed to support addThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support uThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making HiThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out oThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV The sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we onlThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be speciThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be spThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle.[PM/CWB] Delete the CWB entry from the table. It is not needed. The use of the CWB IE in the wake beThe sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 The sentence ending "...isochronous and asynchronous data types and is designed to support addtional physical layers as might be specified at a later time." is out of scope based on the PAR. LVALThe SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. The SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed with respect to the operation and establishment of data keys. It needs to be able to establish a required bit level of security in a system.The previous draft was changed to specify a "new" encryption scheme for NTRUEncrypt, referencing EESS #1, ees251ep3. The current draft specification isThe SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed with respect to the operation and establishment of data keys. It needs to be able to establish a required bit level of security in a system.The previous draft was changed to specify a "new" encryption scheme for NTRUEncrypt, referencing EESS #1, ees251ep3. The current draft specification isThe SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed with respect to the operation and establishment of data keys. It needs to be able to establish a required bit level of security in a system.The previous draft was changed to specify a "new" encryption scheme for NTRUEThe SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies The SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed with respect to the operation and establishment of data keys. It needs to be able to establish a required bit level of security in a system.The previous draft was changed to specify a "new" encryption scheme for NTRUEncrypt, referencing EESS #1, ees251ep3. The current draft specification is supposed to represent a guide to implementers that will stand the test of time as a standard if approved. It is a fact that the eThe SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed with respect to the operation and establishment of data keys. It needs to be able to establish a required bit level of security in a system.The previous draft was chaThe SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed with respect to the operation and establishment of data keys. It needs to be able to establish a required bit level of security in a system.The previous draft was changed to specify a "new" encryption scheme for NTRUEncrypt, referencing EESS #1, ees251ep3. The current draft specification is supposed to represent a guide to implementers that will stand the test of time as a standard if approved. It is a fact that the evolving NTRUEncrypt scheme has been proven vulnerable to attacks that completely render the encryption useless. Additionally, the immature, relatively untested and unreviewed nature of this cryptographic scheme exposes the proposed standard to early obsolescence in this unproven element.6c$Cef`ULC<2G^^RTd @ @ @ @ @ @`X@`X@orm&StartUpShowDShvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Figure 32319E~@{%@hXOugI6`X@`X@orm&StartUpShowDShvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum04111130E7@Change to Rx and Tx.XOugI6`X@`X@orm&StartUpShowDShvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.25616E|@{"Clarify the definition of frame.XOugI6`X@`X@orm&StartUpShowDShvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.9526E,@Change awake to AWAKEXOugI6`X@`X@orm&StartUpShowDShvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.7521E@@XOugI6`X@`X@orm&StartUpShowDShvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum00Ez@{ See commentXOugI6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrumETable E.439716TR_@Make the requested deletion.XO}qeH6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrum088.1321537TR>@Make the requested deletion.XO}qeH6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrum088.13.2.321943TR@Make the requested change.XO}qeH6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrum077.4.1513131TR1@Make the requested deletion.XO}qeH6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrum07Table 5112333TR,@Make the requested deletion.XO}qeH6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrum088.719935TRa@Make the requested deletion.XO}qeH6`X@`X@   Roberts, Richardrroberts@xtremespectrum.com70326930433016135016XtremeSpectrum077.4.1212941TRA@Make the deletion.XO}qeH6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola0992442425TRc@v@XOzl^D6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola104.1.130015TR>@@XOzl^D6`X@`X@orm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola09423748TR@ f@uXOzl^D6 LVAL  @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "folloreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.I suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)."In a series of three or more terms with a single conjunction, use a comma after each term except the last. I suggest "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable, and moving devices within or entering a personal operating space."; adding a comma after portable. Refer to the May00, IEEE Standards Sreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the totalreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph thatreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandatreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.I suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)."In a series of replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.I suggest "9 RSA publications are available from (http://www.rsasecurity.com/rsalabs/pkcs/pkcs-1)." "10 SECG publications are available from (http://www.secg.org)."In a series replace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated the start of an IE at even position of octets and hence the padding of a zero at the tx-DEV at the end of an IE whenever the total size of that IE is odd number of octets.I suggest "9 RSA publications are available from (http://www.rsasecureplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that manreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"Put back the paragraph that mandated the start of an IE at even positioreplace aMaxLostBeacons with aMinBeaconInfoRepeat and change "following that system wake beacon" to "including that system wake beacon"LVAL׏I suggest: Draft Standard for Information technology- Telecommunications and information exchange between systems- Local and metropolitan area networks Specific requirements- Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs) Please make the change globally. Additionally, and in terms of the LB19 CommentID: #10 rejection, I understand the PAR issue but I think this is a clear editorial issue and we have WG precedents to apply the editorial suggestion. Here are some issues to consider in this rebuttal 1. The 802.15.3 PAR is incorrect and is in conflict with itself and should state the previously mentioned item in the title section i.e., "2. Assigned Project Number [P802.15.3]" or section 4 should state "...Part 15.3...". http://grouper.ieee.org/board/nescom/802-15-3.pdf 2. An example is the 802.15.1 PAR which TG3 copied and is why you have the error in the first place :). When 802.15.1 got to Sponsor Ballot the PE said 15.1 was ok cuz (a) we had a corrigendum: http://ieee802.org/secmail/msg00600.html and (b) implicitly it was necessary to add the dot level based on the 15.2, 15.3, 15.4, etc. approvals. http://ieee802.org/15/par.html 3. Specifically, having the 802.15.1(TM)-2002 published sets a precedent as our PAR says "Part 15..." but we are published with "Part 15.1..." http://grouper.ieee.org/board/nescom/802-15.pdf Note: 802.15.4/D17 is in Sponsor Ballot with "Part 15.4..." 4. If you release the 15.3 Draft to Sponsor Ballot there might be an issue and someone might object BUT I think going forward w/ the title as-is is a bad idea. For example the 3rd of the 802 five criteria "Distinct Identity" will be problematic if the IEEE titles are NOT distinct and/or inconsistent in the WPAN Standards Family: http://ieee802.org/3/rules/rules.html#P72 Note: I applied (Session #20) the latest edit to the 802.15.3a DRAFT PAR because of this very issue and after careful review of other approved A LVAL N  Цh;h U  4 G  z M   h/j-a#p0U703-269-3022571-220-1211XtremeSpectrum077.5.4.414515E6@% pick one.XOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum077.4.11129Eu@%8@)XOugOAdd two subrequirements to MLF13. 13.1 dynamic isochronous stream, 8.4.4.1, M 13.2 pseudo-static isochronous steam, 8.4.4.1, OChange "The protocols have been reviewed by" to "The protocols have been reviewed by (whomever reviewed these protocols)"Create a summary table of PHY parameters instead of spreading them all over the PHY clause(s).Remove blank between period and last word in sentence ('key').Please make the requested changes.Delete sentence on page 216 line 19.Change to: "The system wake beacon interval shall not be less than 4 and not greater than 255".Insert text: PNdiOStartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.439716TRl@Make the requested change.XOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.339211E4@@{#@)XOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.339251TR@Make the requested deletion.XOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 14322321E0@$@dhXOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.322041E@Please provide correct xrefs.XOugH6StartUpForm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.321943TR@lt PHY Layer Standards and their titles: http://ieee802.org/secmail/msg02824.html In terms of the next step I suggest you ask Jennifer Longman what her opinion is i.e., leave as-is, apply edit, submit a corrigendum to the 802.15.3 PAR, etc. Finally, I think just from a publishing and distribution point of view it will become confusing - make the edit. If the Editor or Chairs need to change the PAR then please do so, however, the approved IEEE Std 802.15.1-2002 states "Part 15.1" and the PAR does not. It was not an issue for RevCom and the StdBD so it should be an easy edit to apply to keep our family of standards consistent. LVAL W4F  G $  [PM] The DEV is not forced to be in the AWAKE state during the entire wake s[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A DEV shall support concurrent reception of fragments of at least three MSDU/MCDUs" means. Is it per stream or totally? Where did this sentence come from?/KO[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable and moving devices within or entering a personal operating space." is gramatically incorrect.Again, the text "...20 Mb/s is proposed to be the lowest rate..." and the text on the next page, pg 2, ln 14 "...20 Mb/s or more..." are from the PAR but Clause 11, Table 118, pg 313, ln 14 states "...11 Mb/s...". It is very likely that this inconsistancy (PAR vs. Draft) issue will come up in Sponsor Ballot. A parallel PAR change now will add mimimal to no delay to the project BUT RevCom can add 3-6 months!The sentence "Compatibility and coexistence criteria were included in the proposal evaluations." is vag[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A DEV shall support concurrent reception of fragments of at least three MSDU/MCDUs" means. Is it per stream or totally? Where did this sentence come from?/KO[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is h[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A DEV shall support concurrent reception of fragments of at least three MSDU/MCDUs" means. Is it per stream or tota[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A DEV shall support concurrent reception of fragments of at least three MSDU/MCDUs" means. Is it per stream or totally? Where did this sentence come from?/KO[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.respo[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A DEV shall support concurrent reception of fr[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct tex[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A DEV shall support concurrent reception of fragments of at least three MSDU/MCDUs" means. Is it per stream or totally? Where did this sentence come fr[PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KO[Frag] Unclear what "A [PM] The DEV is not forced to be in the AWAKE state during the entire wake superframe, only as described in 8.13. Use the correct text from 02/276r13./KOLVAL׏ Same as comment 513 in LB19Comment:same as comment #536 in LB12ORIGINAL COMMENT (LB12)If SA is broadcast and anybody could start tx, how's collision handled?What is the point in getting devices to collide here instead of makingthis MTS part of CAP and letting devices freely use CAP as alreadydefined. This is useless and adds unnecessary complexityORIGINAL SUGGESTED REMEDY (LB12): Remove lines 8:22 on page 151 and all references to "MTS/GTS with BC/MC-SA"from the draftResponse: REJECT. The slotted aloha access method is used to provide access to theseslots just as CSMA/CA is used in the CAP. The TG has decided to allow bothaccess methods, CSMA/CA in the CAP and slotted aloha in the MTSs so thatthe 802.15.3 MAC is capable of supporting different types of PHYs.REBUTTAL (LB19):The response does not resolve the issue of having COLLISION basedtransmissions under COLLISION FREE PERIOD, instead of making this partof CAP.I do not see 802.15.3 PHY or applications listed in PAR requiring it.I do not see how CSMA/CA mechanism used in CAP and TDM mechanism used inCFP fail in achieving whatever the slotted-aloha cheme is achieving.I do not see any reason or justification to add extra complexityresulting from having one another channel access mechanism. Suggested Remedy:Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Response:ACCEPT IN PRINCIPLE. Add new subclause 11.2.10,  Channel access methods with text  A PNC-capable DEV compliant to this standard shall allow the use of the CAP for contention based access for association, data and commands, {xref 7.3.1} when using the 2.4 GHz PHY. A DEV compliant to this standard shall support the use of the CAP when using the 2.4 GHz PHY. Use 1 bit from the reserved bits to the  Piconet mode field ,  MCTAs used with definitions  The MCTAs used bit shall be set to 1 if the PNC will be using open or association MCTAs. Delete the sentence on page 111, lines 1-2,  LVAL v1b N '=O>{tmf_&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@|)XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@@XOyhWD6$`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC044.0942Eg@%'@XOyhWD6#`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.101942EI@%&@{)XOyhWD6"`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.5784EI@%K@z)XOyhWD6!`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3664950E6@%-@y)XOyhWD6 `X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3564447E@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.2661819E@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.1353839EP@%@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3511Ed@%@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC022.045354ED@%@XOyhWD6`X@`X@orm&StartUpShowDG If the CAP end time indicates no available time and no message types are permitted during the CAP, then MTSs are implied. (note this deletion is in response to CID 407).Expand MLF13 in the PICs (note this will become MLF13.1 and MLF13.2 due to another comment.)MLF13.1; Open and association MCTA operations; 8.4.4.4, 8.4.4.5; O.1MLF13.2; Regular MCTA operations; 8.4.4.4; M{ed. note: the CAP stuff is like MLF13.3 now}Commentor's response:Response to this comment do not address the core issue of an additional access mechanism(MTS and slotted aloha) in the standard. The proposal does not justify why they are needed in802.15.3. Hence the resolution is unacceptable./!6KGXi|ȍǠƦŽ_`3@`3@  Y NoName11EXOHHHFDDDDBBBB>>>>>6C?@3@3@  3@ Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.3.419245TRMissing Figure reference0@ AOseH6&@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.3.319126E-@1@ XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 77191E6@!Supply left brackets as needed.XOseH6=@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.31903TR5@K@ XOseH6 @3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.21881T@X@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.6.318923E editorial,@XOseH67@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.518844T@n@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.318818TR@j@XOseH64@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.318818T]@ @XOseH62@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.318818TR9@ `@XOseH61@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.218812TRO@ @XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.2.11887TAdd the following text.;@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.118727T,@ @XOseH6e@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 89211T@ _@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 75188TR@C@XOseH6Q@3@@3@  Y Kleindl, Guenterguenter.kleindl@siemens.at43 51707 35738Siemens1111.3.41924546Emissing figure number?@XO}ttdH6 LVAL '=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@|)Remove "max frames" from Figure-17 and instead include a two-octet wide "total numbeRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause 4 then they should be found in the draft. Also, I submit that for "DLL" it should be "Dynamic-Link Library" not "Data Link Layer". Finally, if you want to create an acroynRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defiRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of tRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definitioRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collectioRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload ofRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burst LVAL {tmf_XQJC<5.'  xqjc\UNG@92+$ [SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed about termination via the NULL CTA, it's informed via the CTR response from the PNC. Ref Fig 120, page 193 and 8.3.4 page 176 line 16-17./KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request Even if not, it's easier to call with an index when you want to remove the IE. /KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request Even if not, it's easier to all with an index when you want to remove the IE. /KO[Assoc] Capability Field is not part of the DEV association IE. Consequently, delete this parm from the MLME-DEV-ASSOCIATION-INFO.indication pri[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list sin[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed about termination via the NULL CTA, it's informed via the CTR response from the PNC. Ref Fig 120, page 193 and 8.3.4 page 176 line 16-17./KO[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed abo[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either ad[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parame[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this paramet[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in th[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list. LVAL 6Yr`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Please make the requested change. Its just an editorial but it will make it easier for Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primitive is used to inform the SrcDEV DME that the MLME has received a channel time response command indicating that the channel time that was previously allocated has been terminated by the PNC or the TrgtDEV. It may also be used to indicate to the TrgtDEV DME that the MLME has seen a null-CTA in the beacon with its DEVID, BcstId or McstID as the destination.Again, I suggest adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells. Please make the change globally.I suggest "...being updated, Clause 10."; that is if you mean "10" refers to Clause 10. Please make the change globally. Note 1: that this repeats further in thePlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primitive is used toPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change senPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the prPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between thPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between tPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel TPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primiPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command. LVAL[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The Des[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoc[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS m[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] Th[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it nee[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The original purpose of this IE got lost! All subrates shall also be announced, regardless if [CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any othe[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Iso[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The original purpose of this IE [CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The or[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if i[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KO[CTA/Isoch] The original purpose[CTA/Isoch] All changed subrates shall also be announced, regardless if the DEV is in PS mode. The DestDEV cannot find the CTR-interval in any other way and it needs it if it wants to go into a PS mode./KOLVAL؏  a L 1 M  ` ! # ~ Y w9.q@Same as CID 410 in LB22Original comment:The new field "Num max frame size" is mostly useless. What if all the framesare (aMaxFrameSize-1) octets long? Instead of that, it is useful to includethe total number of octets as sum of number of octets in the payload of all frames sent in the dly-ack-window. this total number of octets is helpfulin buffer management at the receiver which is supposed to hold all theframes (in some corner cases) until a delayed-ack-frame is sent.Suggested Remedy:1. Remove "Num max frame size" from Figure-15 and all its references from the fraft2. Include total number of octets as sum of number of octets in the payload of all frames sent in the delayed-ack-windowResponse:REJECT. Two variables are needed, the total amount that can be sent as well as the number of frames that the destination DEV is able to handle. The number of frames is important because there are physical limitations in the Dly-ACK generation. The other reason is that there are physical limitations in the buffer implemention, e.g. addressing.Commentor's response:The commenter agrees that there are two variables needed and it is evidentby the suggestion. But what is not clear is the intention in providing number of frames of size aMaxFrameSize, instead of providing a direct bound of max on totalnumber of octets that is entertained in the burst. The implementations can makeuse of this information in a useful way while the current info does not given anycluse on the size of the (MAxNumFrames - NumMAxFrameSize) of the frames. How doyou expect the implementations to guess those sizes? If all of them are(aMaxFrameSize-1), they are not indicated to the rx-DEV in this frame and the rx-DEVis supposed to handle them properly. In the worst case if all of the NumMaxFrames areof the size (aMaxFrameSize-1), then NumMAxFrameSize will be indicated as zero althoughthe rx-DEV has the pain of dealing with these mega-burst!! LVAL N  @ @ @ @ @ @ @ @ @F`X@`X@orm&StSee CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the aSee CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/PM] CTR may be refused because destination is in hibernation.See CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether tSee CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUISee CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary See CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/See CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.rSee CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/See CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.[ASIE] OUI may be same for several calls See CID-446, 477, 478 and 479 in LB19Use of Vendor specific command is the answer to the issue that is intended to be solved through this app-specific IE.LVAL؏v1b N  @same as CID 414 in LB19Original comment:In this sentence what does "multiple beacons" actually mean? Multiple beacons in the same superframe, similar to fragementing beacon, OR IEbeing present in beacons sent at different TBTT but each time with differentcontents of association info. I think what is intended is to say thatif there are too many assoc/disassoc, the beacon at current TBTT may notbe big enough to carry them all, so the remaining Dev-assoc-IEs will befilled into the next beacon sent at next TBTTSuggested Remedy:If intended, do NOT allow fragementation of beacon. Alter the sentence inln42:43 to mean that the PNC may send IE corresponding to a recent assoc/deassoc in the beacon at next TBTT if the current beacon does nothave space for it.Response:ACCEPT IN PRINCIPLE. Delete the sentence "The PNC may use multiple beacons to broadcast successive DEV association IEs if too many DEVs are associating than will fit in a single beacon.." as it is confusing and does not add any new information. The PNC is able to choose when it sends any IE.Commentor's response (LB22)The response addresses the issue only partially. For interpretations towardsconformance, "The PNC is able to choose when it sends any IE" is not correct The interpretation by vendors can go either way. that is, a group of implementors might expect the Dev-Assoc-IE contianing the recently associated DEVs to appear immediately after assoc while the rest might tolerate it appearing anytime. Hence the inclusion of the suggested remedy is required. I have rephrased the same in thefollowing text for editor's peruse (Applicable after the removal of sentence asin the response)."The the DEV association IE corresponding to an association shall be included in thebeacon sent at the start of immediate next superframe, excepting the case where thatbeacon is already at its maximum allowed size where the inclusion of IE is delayeduntil the space in the beacon permits the same." LVAL {tmf_XQJC<5.'  xqjcIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the annoIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in powerIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with thIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC In rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeaIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall return a channel time response command with the error code set to 'destination in power save mode' (rename error code 7 in 7.5.5.2)Change first sentence to: "In the PSPS mode the DEV is only required to listen to system wake beacons and CTAs where its DEVID is indicated as the destination."PleaIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC shall deny a channel time request if the destination is in HIBERNATE mode. The PNC shall retIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC shall deny a channelIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in In rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in In rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subseIn rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.Delete page 145 line 9-14. Replace with: "The PNC In rules for individual DEV, combine second and third rule to: - If the DEV is in PSPS or SPS mode, the announcement shall be made in aMinBeaconInfoRepeat subsequent beacons starting with the system or SPS wake beacon.i2Bd̆ːʪ0cśěݝr@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.2.117544Erewrite as shown below.@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.2.117543Eremove stray commaN@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.217539Eremove stray comma7@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.117531TRTBD to be resolved3@XOseH6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp09TR@@XO{kk]H6o@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent0991751T@j@XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent099.117531T@Change "TBD" to "16 bits"XO}yn`RC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0900175E@3@XO|xtaaSC6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola099.117531T3@ Change TBD to 8.XOvhZB6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain099.01751T@ @XOvhZA6|@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America086.1, & Fig.88, 89153T@ .@XOkk]G6z@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America0813.2163TR`@ Remove this mode in draftXOkk]G6y@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America082.514122TR@ b@XOkk]G6x@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America082.614228TR:@P@XOkk]G6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.2.21382728ET@#@ XOugI6y@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum08TR@A@ XOugI6x@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum08Th@Please clarifyXOugI6 LVAL In figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets iIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command canIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calls toIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same fIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The LenIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculationIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change.[PM] Some attempts have been made to create aIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. TheIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of fIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculIn figure 92, each structure is noted as 37 octets in length. In figure 93, the DEVID bitmap is 1 to 32 octets in length so the each structure may take on values of from 8 to 37 octets. The Length calculation requires change./h|ɠCh˺CLwƘ;d0;58 CLw4;0;@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1010.3.1.318048T@@XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1010.11774E @$@XO}yn`RC6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self1010.3.3.118312E@@XOyhWD6 @3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self1010.1.117730E{@@XOyhWD6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola10NA00T.@t@XOvhZB6T@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola1010.3.4.2.218620EBad Grammar.?@XOvhZB6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola1010.3.4.2.1185TRN@@XOvhZB6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola1010.3.4.2.11850TRR@@XOvhZB6Q@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola1010.3.2.218222E(@L@XOvhZB6S@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola1010.1.117727T5@'@XOvhZB6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum099.117529T]@B@ XOugI6@3@@3@  Y Seals, Michaelmseals@intersil.com(321) 724-7172Intersil091753Tk@<@ XO~yyukk[F6o@3@@3@  Y Seals, Michaelmseals@intersil.com(321) 724-7172Intersil09117531TR9@6@ XO{yukk[F6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.2.217612Eremove American English idiom4@ XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.2.21767E!Rewrite sentence as shown below@ XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.2.21767Erewrite as shown below-@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum099.2.117546E1@.@XOseH6 LVAL @ @ @ @ @ v`X@`X@ormDelete the first sentence at the top of this page, it is redundant with the second sentencDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Change this sentence frag. " ThePNC may optionally allocate the CFP such that there is ..." "The PNC may optioanlly allocate channel time in the CFP so that there is..."[ChnlStatus] ThisDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we Delete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: RedundaDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Change this sentence frag. " ThePNC may optionally allocate the CFP such that there is ..." "The PNC may optioanlly allocate channel time in the CFP so that theDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Change this sentence frag. " ThePNC may optionally allocate the CFP such that there is ..." "TheDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy iDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Change this sentence frag. " ThePNC may optionally allocate the CFP such that there is ..." "The PNC may optioanlly allocate channel time in the CFP so that there is..."[ChnlStatus] This senteDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Change this sentence frag. " ThePNC may optionally allocate the CFP such that there is ..." "The PNC may optioanlly allocate channel time in the CFP so that there is..."[ChnlStatus] This sentence is too excDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And aDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the firDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Change this sentence frag. " ThePNC may optionally allocate the CFP such that there is ..." "The PNC may optioanlly allocate channel time in the CFP so that there is..."[ChnlStatus] This sentence is too exclusive: "Thus, the command should only be used for DEVDelete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad.Delete the first sentence at the top of this page, it is redundant with the second sentence which is more informative than the first sentence. And as we all know: Redundancy is bad. LVAL N n[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." <and ends with th[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command and a channel time request command with 4 isochronous CTRBs." Why 4 isoch CTRBs?Change this sentence frag. "...inteval, the PNC shall terminate those streams,..." "...interval, the PNC shall..." Also change this sentence frag. on p217,line 40: "...as in the ACTIVE mode regardless if the command ..." "...as in the ACTIVE mode whether the command..."Change this sentence frag. "...every beacon i[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command an[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command and a channel time request command with 4 isochronous CTRBs." Why 4 isoch CTRBs?Change this sentence frag. "...inteval, the PNC shall terminate those stre[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a [PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "..[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command and a channel time request command with 4 isochronous CTRBs." Why 4 isoch CTRBs?Change this sentence frag. "...inteval, the PNC shall terminate those streams,..." "...interval, the PNC shall..." Also change this sentence frag. on p217,line 40: "...as in the ACTIVE mode regardless if the command ..." "...as in the ACTIVE mode whether the command..."Change this sentence frag. "...every beacon is a system wake beacons..." "...every beacon is a system wake beacon ..." Also change this sentence frag. on page 216, line 22: "Once this command is sent the DEV shall..." "Once this command is sent, the DEV shall..." And this sentence frag. on page 216, line 23: "...ACTIVE mode regardless if the command was ack..." "...ACTIVE mode whether the command was ack..."[PM/SPS-4] Delete this sentence frag. [PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command and a channel time request command with 4 isochronous CTRBs." Why 4 isoch CTRBs?Change this sentence frag. "...inteval, the PNC shall terminate those streams,..." "...interval, the PNC shall..." Also change this sentence fr[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command and a channel time request command with 4 isochronous CTRBs." Why 4 isoch CTRBs?C[PM] Please clarify the intent of this sentence which starts with these words: "In the SPS DEV DEV's next wake superframe, ..." "...that is long enough to handle a PS change command and a channel time request command with 4 isochronous CTRBs." Why 4 isoch CTRBs? LVAL 3 s 8 n K &  ] $ X 5  X 2 `=a>c@21548E@$@^hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321537TR;@Make the requestedSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this tSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication.[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation utterly complicated. All this calls for a unified rule for PSPS and SPS: IfSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication.[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead of just N subsequent beacons starting with the wake beacon, makes PNC implementation utterly complicated. All this calls for a unified rule for PSPS and SPS: If you miss your wake bSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands iSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands Since the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commandsSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication.[PM/CWB] PCTM and CWB don't work if the DEV Since the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs fSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication.[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N Since the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then theSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication.[PM/CWB] PCTM and CWB don't work if the DEV missed its wake beacon. The rule in SPS that beacon announcements shall be done in N subsequent wake beacons, in stead ofSince the new PNC must authenticate with all of the DEVs in the piconet. It must allocate time for this to happen. If the PNC does not allow commands in the CAP, then the PNC SHALL set up CTAs for authentication. LVALt  @ @ @ @ @ @ @ @ @`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.1321510TR}@U@ihXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.3.417644TR@ {@hhXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.4.4.418212TR}@>{@XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703Data integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance that data came frData integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance that data came from a party with the cryptographic key. Integrity may be provided using a key shared by all piconet DEVs or using a key shared between two or more DEVs. All secure data frames that fail integrity checks are discarded.Delete section 9.1.6 and insert the following text: Data encryption uses a symmetric cipher to protect data from being read by parties without the cryptographic key. Data may be encrypted either by using a key shared by all piconet DEVs or by using a key shared between two or more DEVs.New text, continuing on "When MCTA are used...": "The PNC shall allocaData integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance that data came from a party with the cryptographic key. Integrity may be provided using a key shared Data integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance tData integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance that data came from a party with the cryptographic key. Integrity may be provided using a key shared by all piconet DEVs or using a key shared between two or more DEVs. All secure data frames that fail integrity checks are discarded.Delete section 9.1.6 and insert the following text: Data encryption uses a symmetric cipher to protect Data integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance that data came from a party with the cryptographic key. Integrity may be provided usingData integrity uses an integrity code, often referred to as a message authentication code, to protect data from being modified by parties without the cryptographic key. It further provides assurance that data came from a party with the cryptographic key. Integrity may be provided using a key shared by all piconet DEVs or using a key shared between two or more DEVs. All secure data frames that fail integrity checks are discarded.<#0258jg8@3@@3@  Y Shellhammer, Steveshell@symbol.com(631) 738-4302Symbol Technologies10TRX@=@ XOll\J6o@3@5@ 5@5@5@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.318631T2@Q@@ KACseH6v@3@5@ 5@5@5@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.218620Ts@^@(@ KACseH6v@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.218620E grammatical1@'XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.218618TR?@w@&XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.11861TR=@ @%XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.11861TR(@ @XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.118553T@ Refer to security committee.XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.118546TRp@ n@$XOseH6@3@5@ 5@5@5@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.118544TR@ f@#@ KACseH6v@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.118541TRu@W@"XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.2.11859TRM@@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.218450TRo@:@!XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.4.118426Eremove stray word "the"2@ XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.3.31841T@"Question for security committee.XOseH6M@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1010.3.3.118228Ty@Refer to security commmittee.XOseH6 LVAL kH%k r O | : 3  _ <  } Z 7  S*CyhWD6`X@`X@orm&StartUpShowDBarr, JohnJohn.Barr@Motorola.com(847) 576-8706(847) 651-6822MotorolaCC.1.436627E5@%{@)XOThe MLME commands and frame formats imply that ChallengeResponse is defined with aThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate security suites which was not the intention of the BRC when this was accepted.The SRF - Security requirements field, defined as being included in the authenticaThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate security suites which was not the intention of the BRC when this was accepted.The SRF - Security requirements field, defined as being included in the authenticaThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate security suites which was not the intention of the BRC when this was accepted.The SRFThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left oThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate security suites which was not the intention of the BRC when this was accepted.The SRF - Security requirements field, defined as being included in the authentication response command used to indicate the authentication policies of the security manager. This should be more fully discussed wThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate security suites which was not the inThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remaining security mode is required. This sentence limits the suites to the non-certificate securityThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105.When mode 2 was removed, implementation of any of the defined security suites for the remThe MLME commands and frame formats imply that ChallengeResponse is defined with a fixed length for all security suites. ChallengeResponse was left out of Table 105. LVAL /Y @ @ @ @ @ @ @ @ @StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola093.2237711TR@ @XOzl^D6StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola092.623289EI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Remove open/association MTS/MCTA mechanism and slotted aloha mechanism and all references to them from the draft (Applicable to 8.4.4.4 and 8.4.4.5 in LB22/D14)Reserve a group of stream indices in 7.2.5 for future enhancements likethe slotted aloha so that it can be added if and when it is really neededComplI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.Revert back to the use of GTS when referring to time slot in super frame and CTA being limI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacon that is used to allocate a GTS to a DEV.Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Remove open/association MTS/MCTA mechanism and slotted aloha mechanism and all references to them from the draft (Applicable to 8.4.4.4 and 8.4.4.5 in LB22/D14)Reserve a group of stream indices in 7.2.5 for future enhancements likethe slotted aloha so that it can be added if and when it is really neededCompletely remove the NTRUEncrypt security suite from the draftI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the cI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.Revert bacI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.Revert back to the use of GTS when referring to time slot in super frame and CTA being limited to the component present in the beacI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the cI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment.RI suggest "Consequently, the..."; adding the comma. Note that on pg 2, ln 2 the sentence beginning the same way is gramatically correct but inconsistent with the comment. LVAL kH%k r O Delete this sentence: "A dEV indicates its preferred fragment size for reception in the preferred frament size field in the capabilities IE,..." There were no CIDs from LB-19Delete this sentence: "A dEV indicates its preferred fragment size for reception in the preferred frament size field in the capabilities IE,..." There were no CIDs from LB-19 that requested this addition. If the TE felt this was a necessary item to address why wasn't it raised as a comment during LB-19? No CID, no Delete this sentence: "A dEV indicates its preferred fragment size for reception in the preferred frament size field in the capabilities IE,..." There were no CIDs from LB-19 that requested this addition. If the TE felt this was a necessary item to address why wasn't it raised as a comment during LB-19? No CID, no discussion, no to its inclusion.[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle.[PM/CWB] Delete the CWB entry from the table. It is not needed. The use of the CWB IE in the wake beacon only works if the sleeping SPS DEV hears the wake beacon and in that case the SPS DEV doesn't need the[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle.[PM/CWB] Delete the CWB entry from the table. It is not needed. The use of the CWB IE in the wake beacon only works if the sleeping SPS DEV hears the wake beacon and in that case[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle.[PM/CWB] Delete the CWB entry from the tab[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn wh[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle.[PM/CWB] Delete the CWB entry from the table. It is not needed. The use of the CWB IE in the wake beacon only works if the sleeping SPS DEV hears the wake beacon and in that case the SPS DEV doesn't need the CWB IE. And in the other case it doesn't matter, because it can't use the info in t[PM/SPS-4] Delete MLF23.3 I don't have a problem with making Hibernate, PSPS and 1 SPS set mandatory. However, I do get heartburn when 4 SPS sets are mandated. A 15.3 DEV can support up to 252 streams yet we only mandate that a DEV support at least 1 isochronous stream. We leave it optional as to how many more streams a DEV or a PNC capable DEV may handle. nLVALBDelete this sentence frag. "... when thA DEV Market suitability criterMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and CTAs.SUB MMarket suitability criteria seems to be incomplete.A DEV must asMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned Market suitability criteria seems to be incomplete.A DEV must associate in oMarket suitability criteria seems to be incomplete.Market suitability criteria seems to be incomplete.A DEV must associaMarket suitability criteria seems to be inMarket suitability criteria seems to be incomplete.Market suitability criteria seems to be incomplete.A DEVMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID andMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and Market suitability criteria seems to be incomplete.A DEV must associaMarket suitability criteria seems to be incomplete.A DEV must associate inMarket suitability criteria seems to be incomplete.A DEV must associate inMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assignMarket suitability criteria seems to be incomplete.A DEMarket suitability criteria seems to be incompMarket suitability criteria seems to be incomMarket suitability criteria seems to be incomplete.A DEV must assoMarket suitability criteria seems to be incompleteMarket suitability criteria seems to be incomplete.A DEV must assocMarket suitability criteria seems to be incomplete.A DEV Market suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and CTAMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEMarket suitability criteria seems to be incomplete.A DEV must associate in order tMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and CTAMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and CTAMarket suitability criteria seems to be incomplete.A DEV must associate in ordMarket suitability criteria seems to be incomplete.AMarket suitability criteria seems to be incomplete.A DEMarket suitability criteria seems to be incomplMarket suitability criteria seems to be iMarket suitability criteria seems to be incompletMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DMarket suitability criteria seems to beMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and CTAs.SUB MSC doeMarket suitability criteria seems to be incomplete.A DEV must associate in order toMarket suitability criteria seems to be incMarket suitability criteria seems to be incoMarket suitability criteria seems to be incomplete.A DEV must assoMarket suitability criteria seems to be incomplete.A DEV must associate in orMarket suitability criteria seems to be incomplete.A DEV must aMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID andMarket suitability criteria seems to be incomplete.A DEV must associate in order to be assigned DEVID and CTAs.SUB MSMarket suitability criteria seems to be incomplete.A DEV must associate Market suitability criteria seems to be incomMarket suitability criteria seems to be incomMarket suitability criteria seems to be incomplete.A DEV mMarket suitability criteria seems to be incomplete.LVALC5I suggest: Draft Standard for Information technology- Telecommunications and information exchange between systems- Local and metropolitan area networks Specific requirements- Part 15.3: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for High Rate Wireless Personal Area Networks (WPANs) Please make the change globally. Additionally, and in terms of the LB19 CommentID: #10 rejection, I understand the PAR issue but I think this is a clear editorial issue and we have WG precedents to apply the editorial suggestion. Here are some issues to consider in this rebuttal 1. The 802.15.3 PAR is incorrect and is in conflict with itself and should state the previously mentioned item in the title section i.e., "2. Assigned Project Number [P802.15.3]" or section 4 should state "...Part 15.3...". http://grouper.ieee.org/board/nescom/802-15-3.pdf 2. An example is the 802.15.1 PAR which TG3 copied and is why you have the error in the first place :). When 802.15.1 got to Sponsor Ballot the PE said 15.1 was ok cuz (a) we had a corrigendum: http://ieee802.org/secmail/msg00600.html and (b) implicitly it was necessary to add the dot level based on the 15.2, 15.3, 15.4, etc. approvals. http://ieee802.org/15/par.html 3. Specifically, having the 802.15.1(TM)-2002 published sets a precedent as our PAR says "Part 15..." but we are published with "Part 15.1..." http://grouper.ieee.org/board/nescom/802-15.pdf Note: 802.15.4/D17 is in Sponsor Ballot with "Part 15.4..." 4. If you release the 15.3 Draft to Sponsor Ballot there might be an issue and someone might object BUT I think going forward w/ the title as-is is a bad idea. For example the 3rd of the 802 five criteria "Distinct Identity" will be problematic if the IEEE titles are NOT distinct and/or inconsistent in the WPAN Standards Family: http://ieee802.org/3/rules/rules.html#P72 Note: I applied (Session #20) the latest edit to the 802.15.3a DRAFT PAR because of this very issue and after careful review of other approved Az(Ù̫0]gǒƽHl @ @ @ @ @= ?M0~x`o۷~@3@@3@  Y Akahane, Masaakahane@wcs.sony.co.jp81-3-6409-3238Sony11TR@Z@ XO{wwwwsmm]E6o@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics1111.2.31882027TR@@ XO|jj\B6g@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.6.421251T4@2@ XO}yn`RC6d@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.5.921051TQ@6@ XO}yn`RC6c@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.5.220927T4@4@ XO}yn`RC6a@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.4.720744T!The BPSK mode no longer exists.B@XO}yn`RC6e@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.4.720634T@ @XO}yn`RC6_@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.4.520418T^@ 6@XO}yn`RC6\@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.4.320235T!The MAC header includes the HCS\@XO}yn`RC6[@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.4.22013T7@ @XO}yn`RC6X@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.4.12006T@ @XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.3.419847E)@ d@XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.318949E*@@XO}yn`RC6<@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.2.6.11898T#@e@XO}yn`RC65@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.2.318827T@i@XO}yn`RC6@3@3@  3@ Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent1111.118742Tc@'@RC}yn`RC6&@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self1111.5.921119E@Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self1111.4.520413EF@Add the period.XOyhWD6 LVAL N  StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola093.2237711TR@ @XOzl^D6StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola092.623289E@XOzl^D6StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola092.2TR@<@XOzl^D6StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola091.7TR@@XOzl^D6StartUpForm&StartUpShowDRasor, GreggGregg.Rasor@motorola.com561-739-2952561-453-7800Motorola091.6TR@"@XOzl^D6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.439716TRl@ Make the requested change.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.339211E4@%#@)XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrumETable E.339251TR@Make the requested deletion.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum08Figure 14322321E0@$@hXOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.322041E@Please provide correct xrefs.XOugH6`X@`X@orm&StartUpShowDHeberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum088.13.2.321943TR@lt PHY Layer Standards and their titles: http://ieee802.org/secmail/msg02824.html In terms of the next step I suggest you ask Jennifer Longman what her opinion is i.e., leave as-is, apply edit, submit a corrigendum to the 802.15.3 PAR, etc. Finally, I think just from a publishing and distribution point of view it will become confusing - make the edit. If the Editor or Chairs need to change the PAR then please do so, however, the approved IEEE Std 802.15.1-2002 states "Part 15.1" and the PAR does not. It was not an issue for RevCom and the StdBD so it should be an easy edit to apply to keep our family of standards consistent.6.AV0&;NJ]ZVQd|k@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.721336TRY@n@XOseH6i@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.721336Th@PHY committee to supply.XOseH6j@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.721336Taddition to clause 11.7@XOseH6m@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 93214TRAddition to Table 93S@XOseH6n@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 93214TR@@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.6.121125EReplace "an" with "a"(@XOseH6b@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.5.220914T@E@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 86208E<@8@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.4.720631ERefomatting of math scriptss@XOseH6`@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.4.720631Tremove the phrase "2 and 3"... higher order bits, ...XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.4.72057E)@,@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.4.620450EQ@/@XOseH6^@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Table 82203TR@&@XOseH6X@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Equation 720321TR@@XOseH6]@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum11Figure 110203T)@O@XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.3.419247El@Reformat math symbols.XOseH6 LVALЦ`6% u n K (  w T )  r N +  K(e~)~[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that i[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard defines the PHY and MAC specifications for high data rate wireless connectivity with fixed, portable and moving devices within or entering a personal operating space." is gramatically incorrect.Again, the text "...20 Mb/s is proposed to be the lowest rate..." and the text on the next page, pg 2, ln 14 "...20 Mb/s or more..." are from the PAR but Clause 11, Table 118, pg 313, ln 14 states "...11 Mb/s...". It is very likely that this inconsistancy (PAR vs. Draft) issue will come up in Sponsor Ballot. A parallel PAR change now will add mimimal to no delay to the project BUT RevCom can add 3-6 months!The sentence "Compatibility and coexistence criteria were included in the proposal evaluations." is vague. The IEEE does not mandate the use of CFAs, CFPs, evaluations, and down selections so to say "...included in the proposal evaluations." does not make sense for non-IEEE 802.15 members.Change of GTS into CTA from D11 to D14 in clauses 5, 7 & 8:AT many places in clause-8, this has caused lot of confusion.For example pp-188, ln-17[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15.2/D6. D6 uses "interoperable and interworking"The sentence "This standard defines t[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate ch[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.The definition of "interoperability" is correct but sort of inconsistent with P802.15[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed [SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.;)N^PVPexDžƐż';k@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706AppairentAA.2.22195T-@@XO{yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706AppairentAA.221712EEditorial comment left in.u@XO{yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706AppairentAA21540T^@H@XO}{yn`RC6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182SelfAA.22171213EO@Delete the Editor notes.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182SelfAA.1.12168E6@0@XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182SelfAA.12151E@@XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182SelfAFigure A.121535EC@ Change to "PHY Layer".XOyhWD6"@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time DomainAA.02151T@ Add xrefs as appropriate.XOvhZA6Z@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum1111.4.12011TO@ @ XOugI6Y@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum1111.4.1201T@ ,@XOugI6:@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum1111.2.818937TL@ Add CRC details here.XOugI6U@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum1111.2.6.323E(@unhyphenate.XOugI6;@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum11Table 761895TRJ@Specify if SIFS is a range.XOugI66@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum11Table7518828TT@)@XOugI6f@3@@3@  Y Shellhammer, Steveshell@symbol.com(631) 738-4302Symbol Technologies1111.6.4212TR@H@XOll\J6@3@@3@  Y Seals, Michaelmseals@intersil.com(321) 724-7172Intersil116.521313TRp@Y@XO~yukk[F6h@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum1111.7213T Additional note to clause 11.74@XOseH6LVALM5 Same as comment 513 in LB19Comment:same as comment #536 in LB12ORIGINAL COMMENT (LB12)If SA is broadcast and anybody could start tx, how's collision handled?What is the point in getting devices to collide here instead of makingthis MTS part of CAP and letting devices freely use CAP as alreadydefined. This is useless and adds unnecessary complexityORIGINAL SUGGESTED REMEDY (LB12): Remove lines 8:22 on page 151 and all references to "MTS/GTS with BC/MC-SA"from the draftResponse: REJECT. The slotted aloha access method is used to provide access to theseslots just as CSMA/CA is used in the CAP. The TG has decided to allow bothaccess methods, CSMA/CA in the CAP and slotted aloha in the MTSs so thatthe 802.15.3 MAC is capable of supporting different types of PHYs.REBUTTAL (LB19):The response does not resolve the issue of having COLLISION basedtransmissions under COLLISION FREE PERIOD, instead of making this partof CAP.I do not see 802.15.3 PHY or applications listed in PAR requiring it.I do not see how CSMA/CA mechanism used in CAP and TDM mechanism used inCFP fail in achieving whatever the slotted-aloha cheme is achieving.I do not see any reason or justification to add extra complexityresulting from having one another channel access mechanism. Suggested Remedy:Remove MTS mechanism and slotted aloha mechanism and all references to them from the draft. (This is applicable to section 8.4.4.4 and 8.4.4.5 in the current draft)Response:ACCEPT IN PRINCIPLE. Add new subclause 11.2.10,  Channel access methods with text  A PNC-capable DEV compliant to this standard shall allow the use of the CAP for contention based access for association, data and commands, {xref 7.3.1} when using the 2.4 GHz PHY. A DEV compliant to this standard shall support the use of the CAP when using the 2.4 GHz PHY. Use 1 bit from the reserved bits to the  Piconet mode field ,  MCTAs used with definitions  The MCTAs used bit shall be set to 1 if the PNC will be using open or association MCTAs. Delete the sentence on page 111, lines 1-2,  LVAL v1b N '=O>{tmf_&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@)XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@@XOyhWD6$`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC044.0942Eg@%'@XOyhWD6#`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.101942EI@%&@)XOyhWD6"`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.5784EI@%K@)XOyhWD6!`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3664950E6@%-@)XOyhWD6 `X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3564447E@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.2661819E@@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.1353839EP@%@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC033.3511Ed@%@XOyhWD6`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC022.045354ED@%@XOyhWD6`X@`X@orm&StartUpShowDG If the CAP end time indicates no available time and no message types are permitted during the CAP, then MTSs are implied. (note this deletion is in response to CID 407).Expand MLF13 in the PICs (note this will become MLF13.1 and MLF13.2 due to another comment.)MLF13.1; Open and association MCTA operations; 8.4.4.4, 8.4.4.5; O.1MLF13.2; Regular MCTA operations; 8.4.4.4; M{ed. note: the CAP stuff is like MLF13.3 now}Commentor's response:Response to this comment do not address the core issue of an additional access mechanism(MTS and slotted aloha) in the standard. The proposal does not justify why they are needed in802.15.3. Hence the resolution is unacceptable. LVAL '=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@)XOyhWD6%`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.11489E@@XOyhWD6$`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 25Add one octet to PS ModChange the headers in figure 92 to be "8 to 37" in two places. Change the LeChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DEV wants to inform the PNC that it's switching to the ACTIVE MODE. If the TrgtID is set to the DEVID of another member DEV, the PNC will set the bit for this DEV in the PCTM IE. If the PS Mode field is set to Hibernate or PS, this field shall be ignored upon reception.Add new IE: PNC Scan IChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DEV wants to inform the PNC that it's switching to the ACTIVE MODE. If the TrgtID is set to the DEVID of another member DEV, the PNC will set the bit for this DEV in the PCTM IE. If the PS Mode field is set to Hibernate or PS, this field shall be ignored upon reception.Add new IE: PNC ScaChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DEV wants to inform the PNC that it's switching to the ACTIVE MODE. If the TrgtID is set to the DEVID of another member DEV, the PNC will set the bit for this DEV in the PCTM IE. Change the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octetChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DEV wants to inform the PNC that it's switching to the ACTIVE MODE. If the TrgtID is set to the DEVID of another member DEV, the PNC will set the bit for this DEV in the PCTM IE. If the PS Mode field is set tChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DEV wants to inform the PNC that it's switching to the ACTIVE MODE. If the TrgtID is set to the DEVID of another member DEV, the PNC will set the bit for this DEV in tChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). Add one octet to PS Mode change command: TrgtID TrgtID is set to the SrcId if the DEV wants to inform the PNC that it's switching to the ACTIVE MODE. If the TrgtID is set to the DEVID of another meChange the headers in figure 92 to be "8 to 37" in two places. Change the Length formula to (1 + sum of PS set structure 1 through PS set structure n)). LVAL '=O>&`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182I. Gifford Consulting LLC055.3.2.11539E!The word "effect" is incorrect.b@)Remove "max frames" from Figure-17 and instead include a two-octet wide "total numbeRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SECID"I suggest changing the sentence to "...while the 11, 33, 44 and 55 Mb/s use trellis coded modulation (TCM), 11.3." for consistency (Clause 4>5), accuracy (no hyphen) and first (after Clause 4) usage style rules. Refer to the May00, IEEE Standards Style Manual. Please make the change globally.I suggest "A piconet is formed when an 802.15.3 DEV, that is capable of acting as the PNC, begins transmitting beacons. Thus, even..."; adding three (3) commas.For starters if you are going to call out terms in Clause 4 then they should be found in the draft. Also, I submit that for "DLL" it should be "Dynamic-Link Library" not "Data Link Layer". Finally, if you want to create an acroynRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defined by the security suite, 10.2", but with Description="The key to be used as defined for the associated SRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition in clause 3 (or 5)Use same fields as defined in Table 12: Type="Octet string", Valid Range="Any valid key as defiRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of tRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definitioRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame." as the definition Remove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burstAdd that "A burst is the collectioRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload ofRemove "max frames" from Figure-17 and instead include a two-octet wide "total number of octets" as sum of number of octets in the payload of all frames sent in the burst LVAL {tmf_XQJC<5.'  xqjc\UNG@92+$ [SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed about termination via the NULL CTA, it's informed via the CTR response from the PNC. Ref Fig 120, page 193 and 8.3.4 page 176 line 16-17./KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request Even if not, it's easier to call with an index when you want to remove the IE. /KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request Even if not, it's easier to all with an index when you want to remove the IE. /KO[Assoc] Capability Field is not part of the DEV association IE. Consequently, delete this parm from the MLME-DEV-ASSOCIATION-INFO.indication pri[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list sin[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed about termination via the NULL CTA, it's informed via the CTR response from the PNC. Ref Fig 120, page 193 and 8.3.4 page 176 line 16-17./KO[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/Term] The source is not informed abo[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either ad[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parame[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this paramet[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in th[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list. LVAL 6Yr`X@`X@orm&StartUpShowDGifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Please make the requested change. Its just an editorial but it will make it easier for Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primitive is used to inform the SrcDEV DME that the MLME has received a channel time response command indicating that the channel time that was previously allocated has been terminated by the PNC or the TrgtDEV. It may also be used to indicate to the TrgtDEV DME that the MLME has seen a null-CTA in the beacon with its DEVID, BcstId or McstID as the destination.Again, I suggest adding "en-dash" (from IEEE FM template (basically a long hyphen character)) to all the blank table cells. Please make the change globally.I suggest "...being updated, Clause 10."; that is if you mean "10" refers to Clause 10. Please make the change globally. Note 1: that this repeats further in thePlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primitive is used toPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change senPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the prPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between thPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between tPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel TPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Change sentence to: This primiPlease make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command.Please make the requested change. Its just an editorial but it will make it easier for people to correlate the parms between the primitive and the Channel Time request command. LVAL e-7 m ) k @ a  Y U zo$O%h{E"]Q]Q]Q]Q]Q] Q] Q]Q]QbQbQbQbQbQbQbQbQb Qb Qb Qb Qb QbQbQbQgQgQgQgQgQgQgQgQgQg Qg Qg Qg Qg e.Please make the indicated change.Remove 'NEW' from PSSetOperation Valid Range column.Change description to: "The number of TUs available to the requesting DEV for allocation"Valid range for AvailableNumTUs is 0-255.Add parameter to MLME-CREATE-ASIE.confirm: "ASIE-index", integer type, range is application specific.Add parameter to MLME-CREATE-ASIE.request: "ASIE-index", integer type, range is application specific.Remove second sentence about ALREADY_STARTEDPlease make the indicated corrections.I suggest "An unsupported data rate...".I suggest adding RFC XXX to Annex F or the Bibliography.Change "There" to "These at beginning of sentence.Remove from table and Challenge.request command.remove the PSSetOperation from the primitive.I suggest either "...allowed to use an access control list (ACLs)..." or "...aSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that areSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.Verification info length(=L2) does not seem to be required since the length of the ACL record field will determine leSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.Same as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarificatSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commenSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.Verification info length(=L2) does not seem to be required since the length of the ACL record field will determine length of the Verification info.[PM] Delete these three parms: MACPIB_PSPSSupported, MACPIB_SPSSupported, MACPIB_HibernateSupporSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what thSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.Verification info length(=L2) does not seem to be required since the length of the ACL record fiSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK fSame as 409 in LB19, the response wasACCEPT IN PRINCIPLE. A burst is the collection of the frames that are pending acknowledgement via a Dly-ACK frame.But what the commentor wants is the clarification in the draft.LVAL5  a >_ p L  b  A W b 2 +(Same as CID 410 in LB22Original comment:The new field "Num max frame size" is mostly useless. What if all the framesare (aMaxFrameSize-1) octets long? Instead of that, it is useful to includethe total number of octets as sum of number of octets in the payload of all frames sent in the dly-ack-window. this total number of octets is helpfulin buffer management at the receiver which is supposed to hold all theframes (in some corner cases) until a delayed-ack-frame is sent.Suggested Remedy:1. Remove "Num max frame size" from Figure-15 and all its references from the fraft2. Include total number of octets as sum of number of octets in the payload of all frames sent in the delayed-ack-windowResponse:REJECT. Two variables are needed, the total amount that can be sent as well as the number of frames that the destination DEV is able to handle. The number of frames is important because there are physical limitations in the Dly-ACK generation. The other reason is that there are physical limitations in the buffer implemention, e.g. addressing.Commentor's response:The commenter agrees that there are two variables needed and it is evidentby the suggestion. But what is not clear is the intention in providing number of frames of size aMaxFrameSize, instead of providing a direct bound of max on totalnumber of octets that is entertained in the burst. The implementations can makeuse of this information in a useful way while the current info does not given anycluse on the size of the (MAxNumFrames - NumMAxFrameSize) of the frames. How doyou expect the implementations to guess those sizes? If all of them are(aMaxFrameSize-1), they are not indicated to the rx-DEV in this frame and the rx-DEVis supposed to handle them properly. In the worst case if all of the NumMaxFrames areof the size (aMaxFrameSize-1), then NumMAxFrameSize will be indicated as zero althoughthe rx-DEV has the pain of dealing with these mega-burst!! LVALГ N  @ @ @ @ @ @ @ @ @ @F`X@`X@orm&StartUpShowDgubbi, RAJUGOPALrgubbi@broadcom.com011-91-80-207-4069011-91-98440-13144BROADCOM, CO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be nece[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the distribute key request command, 7.5.2.7. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-REQUEST-KEY.response/confirm primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the request key response command, 7.5.2.6. Please clarify which name is correct and make the appropriate change in either clause 6 or clause 7.[SEC/Auth] Not clear whether PublicKeyObjectLength parm is required in the MLME-AUTHENTICATE.request/indication primitive's parm list since this parameter does not get used in the Authentication request command,7.5.2.1. Either add the parameter to the Authentication request command or delete the parm from the MLME-AUTHENTICATE.request primitive's parm list.[CTA/PM] CTR may be refused because destination is in hibernation. Therefore change the error code to reflect both the case were a stream is established but the destination enters hibernation or SPS, and the case where a C[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since that is how it is named in the[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-A[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be listed as "EncryptedKey" since[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to [ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives.[SEC/Auth] It is not clear whether the "Key" parm in the MLME-DISTRIBUTE-KEY.request/indication primitive's parm list needs to be list[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to both the ASIE and to the MLME-CREATE-ASIE.request/confirm primitives. @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @              9n      !"#$%&'() *+,-./01234 5 6 789 : ; < =>?@ABCDEFGH I J KLMNOPQR STUVWXYZ[\ ] ^ _ ` abcdefghijkl m n o p qrstu vwxyz{|} ~                                      pqrst u v w x yz{|}~                 @IIIIIIIIII I I I I IIIIKKKKKKKKKK K K K K KKKKMM- -'099 '9 | |||||~~~~~~~~~~ ~ ~ ~ ~ ~~~~~'              ! "#$% &M'M(M)M*M+M,M-M .M /M 0M 1M 2M3M4M5N6N7N8N9N:N;N<N=N>N ?N @N AN BN CNDNE%F%G%H%I%J%K%L%M%N% O% P% Q% R% S%TQUQVQWQXQYQZQLVAL5  a Csame as CID 414 in LB19Original comment:In this sentence what does "multiple beacons" actually mean? Multiple beacons in the same superframe, similar to fragementing beacon, OR IEbeing present in beacons sent at different TBTT but each time with differentcontents of association info. I think what is intended is to say thatif there are too many assoc/disassoc, the beacon at current TBTT may notbe big enough to carry them all, so the remaining Dev-assoc-IEs will befilled into the next beacon sent at next TBTTSuggested Remedy:If intended, do NOT allow fragementation of beacon. Alter the sentence inln42:43 to mean that the PNC may send IE corresponding to a recent assoc/deassoc in the beacon at next TBTT if the current beacon does nothave space for it.Response:ACCEPT IN PRINCIPLE. Delete the sentence "The PNC may use multiple beacons to broadcast successive DEV association IEs if too many DEVs are associating than will fit in a single beacon.." as it is confusing and does not add any new information. The PNC is able to choose when it sends any IE.Commentor's response (LB22)The response addresses the issue only partially. For interpretations towardsconformance, "The PNC is able to choose when it sends any IE" is not correct The interpretation by vendors can go either way. that is, a group of implementors might expect the Dev-Assoc-IE contianing the recently associated DEVs to appear immediately after assoc while the rest might tolerate it appearing anytime. Hence the inclusion of the suggested remedy is required. I have rephrased the same in thefollowing text for editor's peruse (Applicable after the removal of sentence asin the response)."The the DEV association IE corresponding to an association shall be included in thebeacon sent at the start of immediate next superframe, excepting the case where thatbeacon is already at its maximum allowed size where the inclusion of IE is delayeduntil the space in the beacon permits the same." LVAL [PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simp[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to the Vendor specific command just after the Vendor OUI field.The octet field sizes for the PS set structure are incorrect. Please chan[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to the Vendor specific command just after the Vendor OUI field.The octet field sizes for the PS set structure are incorrect. Please change fr[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel scan in 8.9.5. This IE informs the piconet that the beacon will be suspended for a certain time./KO[ASIE] OUI may be same for several calls to MLME-CREATE-ASIE.request. Consequently, it may be necessary to add an ASIE index to the Vendor specific command just after the Vendor OUI field.The octet field sizes for the PS set structure are incorrect[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleepi[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PN[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO[PNC/Scan] A new IE is needed to support comment about PNC channel [PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sl[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to se[PM] Some attempts have been made to create a wakeup signal from a DEV to a sleeping peer DEV. A simple addition to the PS mode change command can cause the PNC to set the PCTM bit for a sleeping DEV./KO LVAL N [PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors t[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urg[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting undiscussed ad-hoc inventions into the draft. If you really want to wake up a sleeping DEV at some unknown time in the future, we could consider having a new command to set the PCTM b[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting undiscussed ad-hoc inventions into the draft. If you really want to wake up a sleeping DEV at some unknown time in the future, we could consider having a new command to set the PCTM bit. O[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know abou[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting u[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DE[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any C[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination[PM] The requestor cannot hang and wait an indefinite time for a decision from the PNC. Either you get your channel time or you don't. If the destination is in hibernation, any CTR shall be denied. If a DEV wants to know about traffic it can select PSPS or SPS. In Hibernation it just wants to sleep. I would kindly urge all editors to please try to refrain from putting undiscussed ad-hoc inventions into the draft. If you really want to wake up a sleeping DEV at some unknown time in the future, we could consider having a new command to set the PCTM bit. One way would be to add a DEVID to PS mode change. If (operation == ACTIVE && dev != UNASSOC) set PCTM(dev)./KO _YNY  Y  Y  Y d Y d Y d Y  Y d Y   Y    Y   Y  Y  Y  Y   Y  Y dY Y  Y Y Y $Y , Y mCommentIDCommenterNameCommenterEmailCommenterPhoneCommenterFaxCommenterCo ClauseSubclausePageLineCommentTypeCommentSuggestedRemedyResponseCommentStatusResponseStatus TopicCreateDateLastModDateDispatchDateWrittenDate"Accept_RejectDate&Closed_UnsatisfDateVoterStatusЁYCommentID    &ɰM@$ &0Id0sb1?& Ml$ &I"I!07Ͽ;$I6I I$IL#wI$IJD`$I0M$g6E@ $Il!g a$I2@L$$I6I`qI2M@d$IB @$ ȟ< ?qI@$d$I2 @ |?6HMl$$I@ $;?} @e$I2@ @$$;>}@@$&IH`${>@d$ 6H D$H{>D$& 2HL$~dd$I6HH$ dd$Y& 2Ld$Ld$ 6HL$I&IĀdI&2Hd$ 1d&IIL$ 2c$&2M $$@2K$I&6I LdI&Hcd 6I!Id&2HY$16IL$&2C I12Md &2H?|&ILd"H?~p &MlK$2Ic???8!@l d!&I$M?8& Al)& "ILϽ& l@$$&0Ms?Ǽ6Ld&$Il7?<6IBed$6I&Id?>2R d Id7?IdM@$'?M@ @D%$?2I dA@$$ $@2@`$O~3 d$@M@$?d$2M@$$'ē [$H H$3Ġ$I&@2Ld$Op?d $ Il$ &O 62Md$I& 6IL$ &3$ &MdY$ 6O36I M$IH3&I0Md&6I30$IL $ & O0)I2Md &ɀIpY2ILd &H>6s v1b Ml$12A4MlA$!&$M9 $MAl)$ "IL32l`$&& A cM@$$$$&IBlg0M`$%& Md@dd$$IRd|dd$$ɴMA$~`d$$$IBm$?>0e$$I6BMH$!??H$d$IHL@$?<$ILg?> ~$$$6M$?1?$$I2L@??$$ MHd??? d&ABLH$?$$Y&MH``??? $&I2HM@$??$6HAH$$?g?6I6@ d$1?? $I&I m`?&H I!L$'?_?I6ILAd&'H|`$ I%e$H'$6IId&w Id$ 6w?6Im$Y7! &@Mm[d6H70IMd & 7;02Hl$6I3p?3w?L0Cl$6A3p?fws@ $&I3p?d)& M3p?9FMc$#&IC3p?DfH!& I3p?2$&Mp= $6"Mp? $6I6M@L@Y&IBlO?@4MH?B$I@e ??"I2JM@d 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^^++OYkfJmMWYbOQu`JYb`kvkJMQk`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkJMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQO &@ @`$H@?pD$ Hd "@d0`$ $@@$$ @??$ $ 2@@ "@D?$$ @@$ @$?$$2@D$@d?O$ "@@$ $@2Hd??O$&HHD$HD$?o&2HD$$H$ ??oI$H$$ "HH$?o$H 6HLd&HHdI ??g 6Hd$&HD$??gH6ID$$H$$H?_g"HI$2IL$??OgI$ IH IggIH$$ID$"H7?g@l$ H I;gMIL$I?gL$ I L$ LMg@$$I $Il'L I H I?f7LdI ID$I@??s?7 $ I  H?y7$  $I"$IG} I"@@ H$s| $ I@` I0~O $$II I?'?I@ I L$ YNdY Y DataIDdmnCYAOIndex @@@$q&@@D$ 2@@ ?1? d$I$ @$1H $$ "H@$??@2HLd&HH$ ? d$HD$$$H2@$ $@HM$$HL$ 0@$"I@$ "@9Hx$Hd$ 6HgImy$&Ld&H7xMd3 $ "IL$2H~d$I L$ IHq?ld$ I $$ Hl$ "I H$$IHdA& I0d$Hd?d$ & L$$L$!&$I2L$ I L{$$2M  M$q?$&2I  I0d1?$$I6A@$ I$ &6I@L`$I2L$4p OY$&2BL@$ I$ /?&I@`$I@$'$I6@ @$I&I@ |I6Jɒ@L$I@ C?ILL@$I&@$$Ȁ?I&@Mi$I2@` $?1?`I2H $ &@H$Y ?b@ Md$ HD H?aId$ $ @$ $W??Im$$2ID$I0? ???H$l$ &Hd &Id $&Hd$ &@e &IL$ $I@ ?Ld  2ID$ "@x8_fl$"M$&H 2@|x1/䐃$6Id$ &H?q?!ld Id $H~$ L$I $q? 6ɐ@$ I$1~$0L @I0L$` I6d $I Id pI&I`$I2L$p1ILd "I$? M@d$$I2@@$ 1B18?2I2BMd4I$`$!P1?0@IH$I@` I0a0yHd$$@$ ,? s~x@@$ 2@L$ 3(?O~zHLY&HHd$C O~@d$ &Hd$ $ d &H L$ $ 0'&hd 2Id$ 2HG!d$&L$$ DC Q$$6I$$&H@;  ad$ IId$H`d&2Id$&H$` ??$&I L$$2HHp>A?d&I L$&IH Hxp?$!&Md&I?& I $&I LP>q?$ & M$&$Id89Ac @ @ @ @ @ @ @$3"I2L$ &I0L 0{a &ɰM@$ &0Id0sb1?& Ml$ &I"I!07Ͽ;$I6I I$IL#wI$IJD`$I0M$g6E@ $Il!g a$I2@L$$I6I`qI2M@d$IB @$ ȟ< ?qI@$d$I2 @ |?6HMl$$I@ $;?} @e$I2@ @$$;>}@@$&IH`${>@d$ 6H D$H{>D$& 2HL$~dd$I6HH$ dd$Y& 2Ld$Ld$ 6HL$I&IĀdI&2Hd$ 1d&IIL$ 2c$&2M $$@2K$I&6I LdI&Hcd 6I!Id&2HY$16IL$&2C I12Md &2H?|&ILd"H?~p &MlK$2Ic???8!@l d!&I$M?8& Al)& "ILϽ& l@$$&0Ms?Ǽ6Ld&$Il7?<6IBed$6I&Id?>2R d Id7?IdM@$'?M@ @D%$?2I dA@$$ $@2@`$O~3 d$@M@$?d$2M@$$'ē [$H H$3Ġ$I&@2Ld$Op?d $ Il$ &O 62Md$I& 6IL$ &3$ &MdY$ 6O36I M$IH3&I0Md&6I30$IL $ & O0)I2Md &ɀIpY2ILd &H>6Ml$12A4MlA$!&$M9 $MAl)$ "IL32l`$&& A cM@$$$$&IBlg0M`$%& Md@dd$$IRd|dd$$ɴMA$~`d$$$IBm$?>0e$$I6BMH$!??H$d$IHL@$?  93QlC  6 O   )*Root Entry;&VBANS  VBAProject NS VBANS   7  #m 7&6) 2 =1/-o?n $\89( 2pkGHIJKLMPx;QRSTUXYZ[]t^_`abcdefghijm"q Root Entry0^Wy;&VBANS  VBAProject NS VBANS YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE:PROJECTPROJECTwmaAcessVBAData   7  #m 7!&6,) 2 =1/-Bo?n 3$>\89( @B2DpVkGHIJKLMPxQRSTUXWlYZ[]t^_`abcdefghijm"nqr suvwyz{}~Forms d@#NS0^Wy0G@#NS@#NSBlob bPropDataFHkdirR AcessVBAData BlobDelta]"PROJECTwmK[^ @ @ @ @ @ @ @,aTypeInfoIlPropDataCopyo1EOL@#NSX4Blob  ܚ 15=$NS0^WyBlob 4ʧPropDataaTypeInfob7PropDataKMpTypeInfoqZPropDataCopy2Q@#NS< Form_fPIcture9P/3 Sub gofFinalReports_"Cor 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<bcefkMsgB@D xphAttribute VB_Name = "Report_Big-Font Committee rd" Basn0{B16FB71B-B4F9-11D1-AF4D-00C0F0090F24} |Global|SpacIFalse dCreatablTru PredeclaId"Expose_TemplateDerivCustomizD$Opt(ionp@ D3T  ?@AB  GHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~/&H00000000 DocClass=Form_fHoundDogging/&H00000000 DocClass=Form_START/&H00000000 DocClass=Form_fRough/&H00000000 Module=Common utilities DocClass=Form_fInput/&H00000000 DocClass=Form_fFinalReports/&H00000000 DocClass=Report_Committee report/&H00000000 DocClass=Report_Big-Font Committee report/&H00000000 DocClass=Form_fPicture1/&H00000000 DocClass=Form_fPicture2/&H00000000 DocClass=Form_fPicture3/&H00000000 DocClass=Form_fPicture4/&H00000000 DocClass=Form_fPicture5/&H00000000 DocClass=Form_fPicture6/&H00000000 DocClass=Form_fPicture7/&H00000000 DocClass=Form_fPicture10/&H00000000 DocClass=Form_fPicture11/&H00000000 DocClass=Form_fPicture12/&H00000000 DocClass=Form_fPicture13/&H00000000 DocClass=Form_fPicture14/&H00000000 DocClass=Form_fPicture8/&H00000000 DocClass=Form_fPIcture9/&H00K[000000 Name="802_3z.mdb" HelpContextID="0" VersionCompatible32="393222000" CMG="2725396447AC6AB06AB06AB06AB0" DPB="4E4C504D50537654765476" GC="75776BB2B5D8B6D8B627" [Host Extender Info] &H00000001={3832D640-CF90-11CF-8E43-00A0C911005A};VBE;&H00000000 [Workspace] Form_fMain=38, 10, 803, 596, Form_fHoundDogging=22, 22, 792, 517, Form_START=154, 154, 950, 784, Form_fRough=-20, 82, 776, 712, Common utilities=46, 9, 820, 606, C Form_fInput=3, 17, 818, 537, Form_fFinalReports=0, 66, 826, 491, Report_Committee report=0, 0, 606, 440, Report_Big-Font Committee report=220, 220, 826, 660, Form_fPicture1=66, 66, 862, 696, Form_fPicture2=88, 88, 884, 718, Form_fPicture3=110, 110, 906, 740,DirData*PropDataReports(NS0(NS(NS Form_fPicture4=132, 132, 928, 762, Form_fPicture5=154, 154, 950, 784, Z Form_fPicture6=176, 176, 972, 806, C Form_fPicture7=198, 198, 994, 828, C Form_fPicture10=44, 44, 840, 674, C Form_fPicture11=66, 66, 862, 696, C Form_fPicture12=88, 88, 884, 718, C Form_fPicture13=132, 132, 928, 762, C Form_fPicture14=154, 154, 950, 784, C Form_fPicture8=176, 176, 972, 806, C Form_fPIcture9=198, 198, 994, 828, C ]X fFinalReports'Form_fMainForm_fMainForm_fHoundDoggingForm_fHoundDoggingForm_STARTForm_STARTForm_fRoughForm_fRoughCommon utilitiesCommon utilitiesForm_fInputForm_fInputForm_fFinalReportsForm_fFinalReportsReport_Committee reportReport_Committee reportReport_Big-Font Committee reportReport_Big-Font Committee reportForm_fPicture1Form_fPicture1Form_fPicture2Form_fPicture2Form_fPicture3Form_fPicture3Form_fPicture4Form_fPicture4Form_fPicture5Form_fPicture5Form_fPicture6Form_fPicture6Form_fPicture7Form_fPicture7Form_fPicture10Form_fPicture10Form_fPicture11Form_fPicture11Form_fPicture12Form_fPicture12Form_fPicture13Form_fPicture13Form_fPicture14Form_fPicture14Form_fPicture8Form_fPicture8Form_fPIcture9                          ! " # $ % & ' ( ) * + , - . / 0 5 C 4 8 59 : ; < = > ? @ D V E F G H I J K L M N O P Q R S T U W t X Y Z [ \ ] ^ _ ` a b c d e f g h i j k l r %o p q s u v w x y z { | } ~ Blob tY PropDataPRTypeInfot3J[U@#NS@#NSBlob ; PropDataK[v1 @ @ @ @ @ @ @TypeInfoL11P*NSP0j4(NS ĀBlob |PropDataTypeInfo    !"#$%&'()*+-./0123456789:;<=Blob  PropDataTVTypeInfot4Y@#NS< 2(NS>uBlob   PropDataOTypeInfoPForms d@#NS0G@#NS@#NSBlob bPropDataFHkPROJECT PropDataCopyBlobCopyTypeInfoCopyPropDataCopyBlobCopyTypeInfoCopyPropDataCopyBlob K[^PropDataXZTypeInfo5W_@#NSBlobCopyTypeInfoCopyARQNHGLZKZPEZ_ZRQDDLKZNLJRTE:: BAVTZP_THMGYWDNAOWKEINOKJKHI:X|>?ͬ;@Detaild Label0eBox2h gofHoundDoggingd Label23d Label24d Label25h gofMainh gofRoughh gofDispatchh gofStatusPopUph gofInputd Label31h gofFinalReportsgImage32?}Blob PropDataXZTypeInfo