Standard Jet DBnb` Ugr@?~1y0̝cßFNj7՜]('`{6n߱eCT>3y[ $|*J|C1 f_Љ$g'DeFx -bT4.0YgN%%`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 to print Clause(s) Summary Report [Clause] In p YY0S hh 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\alSgY 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{|}~ Y{SY  Y Y Y  Y  Y Y  Y AttributeExpressionFlagLvExtra Name1 Name2ObjectId Ordernzf edY"ObjectIdAttributeRoot EntrysM @&VBA@QYVBAProjectCA@pCLtVBA@pCLt 2   !=u /01CD6789:;<=>?@BIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghiS wxyz{|}~Root EntryGS @&VBA@QYVBAProjectCA@pCLtVBA@pCLt 2  E=C D6789:;<=>?@BjIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghilS mnpqrstuwxyz{|}~YXXBIQKLMZPEZ_ZRQDDLKZNLJRTE: PROJECTB/PROJECTwmOaAcessVBADataaDirData*PropDataReports@ϗ(0                          ! " # $ % & ' ( ) * + 0 > / 3 = 4 5 6 7 8 9 : ; < ? G Q @ A B C D E F H P I J K L M N O R \ o S T U V W X Y Z [ f h ^ _ ` a b c d e  -YSY Y Y  Y  Y  Y  Y  Y ccolumn grbiticolumnszColumnszObject$szReferencedColumn$szReferencedObjectszRelationship@ ;;;; ;;;; ;YYYszObject$szReferencedObjectszRelationshiph1`pabcicmd_prop_accept"ACCEPT""[Event Procedure](ڭ ڭ лڠ лڭ ڭHk5`ab>cfi$"Option_ViewWindow1"[Event Procedure]i2` aOption177d5`abWceLabel178Commenti2`aOption179d5`pabdceLabel180SuggRemedyi2`\aOption181d5`BabceLabel182Responsek125`abci($option_status_mode2i2W`ha(Option194d5`Na bVcLabel195proposaCustomGroupsDataAccessPages 12pX(pe(Blob  Main.ClauseMain.SubclausePageLineMain.CommentTypeSuggestedRemedyResponseCommentStatusResponseStatusTopicCreateDateLastModDateDispatchDateWrittenDateAccept_RejectDate Closed_UnsatisfDate!VoterStatusResponse_LabelRe087:<=Babc$e gMain.CommentID@νt3@_GetAllComments_GetA A 2   i % 0:=Babc;e gRh<ij+kD([CommentType] In("TR", "T", "E"))+e@MainMainTable Arial8l|)h Brother HL-1440 seriesH CdX=bN   : k & O ; l ' X# $ % & ' ( ) , - . / 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%  !ppxpp pv5 @  @    @  @  @  @@@ @ @ SOYkfJmMWSSYbJ^iQfdimkSWdobOOdUUYbUSYbfomS`JYbSfYMmoiQ8SfYMmoiQ86SfYMmoiQ88SfYMmoiQ8:SfYMmoiQ8<SfYMmoiQ8>SfYMmoiQ:SfYMmoiQ<SfYMmoiQ>SfYMmoiQ@SfYMmoiQB SfYMmoiQD!SfYMmoiQF"SfYMmoiQH#SidoUW$SkmJmokfdfof%kmJim&Md``dbomY^YmYQk'+UQmJ^^Md``Qbmk(+UQmJ^^Md``Qbmk8)LYUSdbmMd``YmmQQiQfdim*Md``QbmQiSo^^++Md``YmmQQiQfdim,WdmYmQ`k-iQfdimLvMd``QbmYO.idoUWY`fdimMWQM\iQfdim/kYUbJmoiQiQfdimkmJmokiQfdimko``JivmiMd``QbmQiqdmQibJ`QkqdmQikmJmok`Md``YmmQQiQfdimJO`YbOJmJJMMQkkfJUQkOJmJLJkQkSdi`k `dOo^Qk iQ^JmYdbkWYfkiQfdimk kMiYfmk kvkiQ^ mJL^Qk+UQmJ^^Md``Qbmk+kh+MSSYbJ^iQfdimk+kh+MM^JokQ^Ykm +kh+MSSYbJ^iQfdimk+kh+MmvfQ^Ykm +kh+MSWdobOOdUUYbU+kh+MMdbSYi`JmYdb^Ykm +kh+MSWdobOOdUUYbU+kh+MmvfQ^Ykm +kh+SSOYkfJmMW +kh+SS`JYby +kh+SSidoUW+kh+iLYUSdbmMd``YmmQQiQfdim'+kh+iMd``YmmQQiQfdim+kh+iWdmYmQ`k+kh+iiQfdimLvMd``QbmYO+kh+iidoUWY`fdimMWQM\iQfdim+kh+ikYUbJmoiQiQfdim+kh+ikmJmokiQfdim+kh+iko``Jiv+kh+iqdmQibJ`Qk+kh+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``JivYbSdokQiOQSYbQO1m45n2o2`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%Ey 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|>EEEE|/|0|1|2|&|'|(|3|4|5|6|7|8| |||||||||||D|)D|*D|+|| |!|"|#|$|%_|,_|-_|.c|9c|:c|;h|?h|@hlllppptttt tt tttt!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 DEKEMENELWKR 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\@$@.@SummaryInfom>@wDDD88888886 @)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 = 9K ʚJ IB >IGA=G?Ee^GB EE4@L4@~sq_ffMainm>4MR2KeepLocal Tvvv66666664 y @s\@V4@AccessLayoutm>4MR2KeepLocal Tzz:::::::8 @p~Nh@zDJT|@VoterStatusm>@DDD88888886 @l@Eh@'0Np@VoterNamesm>@BBB66666664 @ yDy@y@TR Commenterm>@w@zRFF:::::::8 @ckC]@r3@Roughm> @888,,,,,,,* @_g\@g\@MSysIMEXSpecsm><<<<<<<<<<: Dg\@ԂZ_@MSysIMEXColumnsm>@@@@@@@@@@> =s{3@gw{3@MSysAccessObjectsm>DDDDDDDDDDB ʲw@1ސk 1@MainOutputm>nCBBB66666664 @JN^@ a 1@Mainm>~nC666*******( @gb~b@:5^ @Indexm>E@}888,,,,,,,* @^*ue@f@Dispatchm>h@}>>>22222220 @yBln@ ln@0CloseEandTcommentsm>@w@z^RRFFFFFFFD @LG0f@-@ClauseListm>M@wBBB66666664 @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>4MR2KeepLocal Tpppppppn @2ݨ @ݨ @~sq_cfFinalReports~sq_cTypeListm> @u4MR2KeepLocal 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 8G  N  Y   Y d Y d Y XdY Y Y Y Y Y  DoneClauseList Editor Email Owner ChiefNoWrittenNoAction NoSigTRproblemY ConnectDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeIiimmmiCmEmYYIdParentIdName        45FpGqHrIsJtKuLvA G@VoterNames%%% @  G@ @ G?Main ?  G? ? G>Cj{{3@|{3@ClauseList44444444444 Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@ -----CHECK ALL ="A","B","C","D","E"James Gilbjgilb@mobilian.comK7+ N"10"Gregg RasorGregg.Rasor@motorola.comC) "08"Jay Bainjay.bain@timedomain.com?& "06","09"Allen Heberlingaheberling@xtremespectrum.comQ2! k"00","01","02","03","04","05","07","11"James Gilbjgilb@mobilian.com_K?LVAL ( @ @ @ @ @ @ @ @ @ @ @00000000 0  0  0  01 111 2222333334444555 56!6#6$6"7%7'7(7&8)8+8,8*9-9/909.:1:3:4:2;5;7;8;6<9<;<<<:===?=@=A=>>B>D>E>C?F?H?I?G@J@L@M@KANAPAQAOBRBTBUBVBS  !"#$%&()*+,-./012345789:;<=>?@ABCDEGHIJKLMNOPQRSUVWXYZ[\]_`abcdefghijklmnoqrstuvwxyz{|}~0* pHd 802_3z.mdb4@j = r ̗; J< ADAO>BDAO *\G{00025E01-u0C  0046}#5.0#0#C:\PROGRAM FILES\COMMON MICROSOFT SHA0RED\w350.DLL#Microsoft  3.5 Object LibraryHTstdole>fstdole]f\]043[V-]2]WINNT\System32\12.tlb#OLE Automation/VBIDE>VBIDECaCE157C5.3Program Files\CommonHShared\VBA6E6E@XT.OLBRVisual Basic for @Applic1s Extensibility +  @Report_Big@-Font %i@ttee rBGUR`pbrd_Cig-FE@n@ C@mPmi@t eEr BAVTZP_THMGYWDNAOWKEINOKJKHI28A@VTZP_HMGYW_NO@KbINOhKJHgADH@1^B,<"B(B+BxForm_fMainGEA6r3_f@ a 5n0GRVBZIDXNOFUZDSYCZPKJWZAFNYB(((Main.CommenterName)=[Input Commenter Name]) AND ((Main.CommentType)="TR"))(((Main.CommenterName)=[Input Commenter Name]))(((Main.CommentType) In ("E","T")) AND ((Main.CommentStatus) In ("A","R")) AND ((Main.ResponseStatus) In ("W")))} OO%sM b ( F ˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩˩ˋ m O ) Y  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 5EMain E  GE E GD Main.CommentID- 'D@ 'D Main.Response, gD Main.SuggestedRemedy3 gDMain.Comment+ gD Main.Line( gD Main.Page( gDMain.Subclause- gD Main.Clause* gDMain.CommentID- gDMain.CommentType/ gDMain.CommenterName1 gDMain D GD GD D GC d Main.CommentID- 'Cd ^@ 'Cd Main.Response, gCd Main.SuggestedRemedy3 gCd Main.Comment+ g[Y Settings\alN Y d Y  Y Y  EmailMessageSubjectMsgBodyFull YY Email           !"#$%&' (!)"*#+$,%-&.'/()*+,-./01 2 3 4 5 6789:;<=>?@AB```YY```````]Y``````]``````YY````````]Y```````````````Y```````````````Y``````G:X``````XY112243#&]263'*]3;32Y"Y]Y*YY&12]Y]*/28D]21Y236?W``````Y(````Y``]````````YY``````````````````````````````````]``````````````Y````````]````````Y```````Y`````````Y````]YYY````]``P'YYF%YY+`P/YD7`G!129R(YY`````````]```Y````YYY]```````````]Y`````````````````````````````````YY````````YY`````````````````````````Y`````````````YYY```````Y````````Y``````Y````'Y````````Y````````````````Y````````````]Y```````Y````````]````````Y```````Y``````]Y`]Y`````YY``````YY```````]Y````````Y```````]````````````YY``````YY``Y```Y`Y````` ]``````Y`YY````Y```Y```````YY`````````YY``````]`````````````````````````````````````YY````````````````````````````````YY```````]Y`````YY`]Y````]Y``]``````````YY```;YY``````YYY``````````]````````Y```````YY``````YY`````````]````````Y```````Y``````]``````````]````````````````Y`````````````````````````````````````````YY```]Y````YYY`````YY`]```]Y````Y`````````Y`]YY`]Y```````````````````````````````````````````````]``````````````Y````````]`````````Y```````]`]``YY`]Y````````]Y`````````Y``YY` DD2```]Y````````````]Y````````]Y`YYY``````````YY``````````````````````````YY``````Y``````````]Y`````````````````````````Y````````````]Y``]``````````````YY``````Y``]]YYY`Y``````]Y`````````YY``````````````Y```````Y``````````]````````Y```````Y``````]Y```]``````YY``````YY````````Y`````````YY`````]Y```````````````YYYY````Y``]Y`````, YYD8````YY``````Y```Y`````````Y``````````````]YY```````````````````````````````````````Y``````````````````````````````````]````````````````Y``````````````````````]``DD``````````YY``````````Y````````````]Y`````````````````Y````````]Y``````]Y``````]````````````]`````````````````]``````````YY````YY````````````YY````YY``YYY]````````Y5``Y```Y``````YY`YY```````]```````````````]Y``````````````````````````````````````` LvExtraMSysQueriesLvExtraLL>((n FlagMSysQueriesFlag@@8""n  ExpressionMSysQueriesExpressionXXD..n  Name2MSysQueriesName2DD:$$n  Name1MSysQueriesName1DD:$$n AttributeMSysQueriesAttributeTTB,,nv1  h  c  0 p3&t p R ,  n P * nP* nP( M/gA#y[' 4 l.G eCd  Main.Line( gCd  Main.Page( gCd Main.Subclause- gCd  Main.Clause* gCd Main.CommentID- gCd Main.CommentType/ gCd Main.CommenterName1 gCd Main Cd  GCd  GCd  Cd  GBd @ 'Bd Main.ResponseStatus"C"H7 wBd Main Bd  GBd  GBd  Bd  GAVoterStatus''' A  GA A G@VoterNames%%% @  G@C|{3@|{3@Commenter--Full>>>>>>>>>>> B|{3@|{3@0CloseEandTcommentsDDDDDDDDDDD j{{3@|{3@ClauseList44444444444 Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@@@@@@@@ - {{3@ {{3@VoterStatus66666666666 , {{3@ {{3@VoterNames4444444444 SOYkfJmMWSSYbJ^iQfdimkSWdobOOdUUYbUSYbfomS`JYbSfYMmoiQ8SfYMmoiQ86SfYMmoiQ88SfYMmoiQ8:SfYMmoiQ8<SfYMmoiQ8>SfYMmoiQ:SfYMmoiQ<SfYMmoiQ>SfYMmoiQ@SfYMmoiQB SfYMmoiQD!SfYMmoiQF"SfYMmoiQH#SidoUW$SkmJmokfdfof%kmJim&Md``dbomY^YmYQk'+UQmJ^^Md``Qbmk(+UQmJ^^Md``Qbmk8)LYUSdbmMd``YmmQQiQfdim*Md``QbmQiSo^^++Md``YmmQQiQfdim,WdmYmQ`k-iQfdimLvMd``QbmYO.idoUWY`fdimMWQM\iQfdim/kYUbJmoiQiQfdimkmJmokiQfdimko``JivmiMd``QbmQiqdmQibJ`QkqdmQikmJmok`Md``YmmQQiQfdimJO`YbOJmJJMMQkkfJUQkOJmJLJkQkSdi`k `dOo^Qk iQ^JmYdbkWYfkiQfdimk kMiYfmk kvkiQ^ mJL^Qk+UQmJ^^Md``Qbmk+kh+MSSYbJ^iQfdimk+kh+MM^JokQ^Ykm +kh+MSSYbJ^iQfdimk+kh+MmvfQ^Ykm +kh+MSWdobOOdUUYbU+kh+MMdbSYi`JmYdb^Ykm +kh+MSWdobOOdUUYbU+kh+MmvfQ^Ykm +kh+SSOYkfJmMW +kh+SS`JYb+kh+SSidoUW+kh+iLYUSdbmMd``YmmQQiQfdim'+kh+iMd``YmmQQiQfdim+kh+iWdmYmQ`k+kh+iiQfdimLvMd``QbmYO+kh+iidoUWY`fdimMWQM\iQfdim+kh+ikYUbJmoiQiQfdim+kh+ikmJmokiQfdim+kh+iko``Jiv+kh+iqdmQibJ`Qk+kh+iqdmQikmJmokM^JokQ^YkmM^dkQQJbOmMd``QbmkMd``QbmQiSo^^++`kvkJMQk`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkJMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQOaCbCcCdCC C CZcmd_prop_reject box_commentcmd_prop_accept_in_principlebox_suggested_remedy box_responsecmd_prop_accept Option177 Option179 Option181 Option194 Option196HC7?Option_Filter1Option_Filter2AdditionalCriteriaOption_OrderByBox173Box172Box66TopicAccept_RejectDate CommentStatus LastModDate CommentTypeResponseStatusOption_ViewWindow ViewWindowoption_status_mode WrittenDatecmd_SetDefaultsLabel54Label56cmd_comm_accept CommentIDcmd_comm_rejectLabel62cmd_reac_closedcmd_reac_withdrawnText98cmd_reac_unsat cmd_QuickFindcmd_applyfiltersortClosed_UnsatisfDate Option135 Option137 DispatchDateAdditionalCriteria_DblClickcmd_applyfiltersort_Clickcmd_comm_accept_Clickcmd_comm_reject_Clickcmd_prop_accept_Click "cmd_prop_accept_in_principle_Clickcmd_prop_reject_Clickcmd_QuickFind_AfterUpdatecmd_QuickFind_DblClickcmd_reac_closed_Clickcmd_reac_unsat_Clickcmd_reac_withdrawn_Click cmd_Fun_Clickcmd_SetDefaults_ClickCommentStatus_AfterUpdateCommentTKYNY Y NextCommentIDOldCommentIDYY0LastIndexNumberIHaveUsedOldCommentIDr output file nameZ`LJ7h& ,c:\mydocs\WEBascii.txt General >Editor's Ascii report generator 4c:\mydocs\EDITORSascii.txt Tilde :Editor's Tilde-file generator 4c:\mydocs\EDITORStilde.til ^Error in module cASCIIReport. Invalid argument.i)VG C։}wxgrCp Tjh lA valid filename is required. Use OK to accept default zWarning! Output file already exists. Do you wish to continue? "Output file error$ "04","05","06","22","30","30A","30B","34","35","36","36A","37","38", PageHeaderaC7? L RPreparing to print report for all clauses SELECT *  WHERE ,ORDER BY Main.Clause,  JMain.Subclause, Main.Page, Main.Line; 4Committee Report By Clause *WHERE Main.Clause In( )  AND WC7?Reportz? PageFooter tORDER BY Main.Clause, Main.Subclause, Main.Page, Main.Line  2SELECT * FROM MainOutput; Subclause :MainOutput Export with Tildes MainOutput report complete Y 04.B2դOhW0ńUW@դOhWwhDESTLfa8DXr5cmdClearDispatchTablecmdClearMainTablecmdUnlockDangerousButtonscmdAllToEditorsseSummaryReportsseGeneralReportsseCreateTildeFilescmdNewToEditorssnSummaryReportsBox76Box77snCreateTildeFilessnSendConfirms snSetStatussnGeneralReports cmdSendEmailLabel69ConfirmationListLabel68Label70cmdRequestChangeBox74Box75 cmdAllToChiefscCreateTildeFilesscSummaryReportscmdRequestChange_ClickcmdClearDispatchTable_ClickcmdAllToChief_ClickcmdAllToEditors_ClickcmdClearMainTable_ClickcmdNewToEditors_ClickcmdSendEmail_Click cPrepareMail cSendSummary cSendGeneralcSendConfirmations cSetStatusXD cSendTildecmdUnlockDangerousButtons_ClickscSummaryReports_ClickscCreateTildeFiles_ClickseCreateTildeFiles_ClickseGeneralReports_ClickseSummaryReports_ClicksnCreateTildeFiles_ClicksnGeneralReports_ClicksnSendConfirms_ClicksnSetStatus_ClicksnSummaryReports_Click cmdAllToEditors seSummaryReports seGeneralReports $seCreateTildeFiles cmdNewToEditors snSummaryReports CommentType: snGeneralReports $snCreateTildeFiles snv1SendConfirms snSetStatus cmdSendEmail "cmdClearMainTable *cmdClearDispatchTable*=H87kpNv,LaE6/LB  Email XSummary of all comments to date, by editor ( Comment:  0SELECT * FROM ClauseList ) AND  8All summary reports complete File Datafile  exists. 2Do you wish to overwrite? cSendSummary &SELECT * FROM Main  Subject:  NThe following records were produced on lL<"AFY :The selection criteria were:  jCommentStatus has been changed to "D" for this report  2Summary report complete ( D CL:  Type: / SC:   # .SELECT * FROM Dispatch WHERE Email = " WrittenDate:  0" AND MessageSubject = " " AND Full= MessageSubject @- - - - - < message > - - - - -  MsgBody Full XPlease enter prefix for NEW records report: ,scSummaryReports_Click c:\mydocs\ DispatchDate:  Line: 2 A filename prefix is required. It should include the directory pathname. Use OK to accept default XDetails of all comments to date, by editor ( _ _readable.til Warning: File _ 0 exists. Overwrite file? ,scGeneralReports_Click NAll general (readable) reports complete vORDER BY Main.Clause, Main.Subclause, Main.Page, Main.Line  FGeneral (readable) report complete( CommentStatus: "ResponseStatus:  Topic:  CreateDate: LastModDate: `q]Is (Accept_RejectDate: ,Closed_UnsatisfDate:  VoterStatus:  ----------- CommentID: CommenterName: "CommenterEmail: "CommenterPhone: CommenterFax: CommenterCo:  Clause:  Subclause:  Page:  CommentEnd: $SuggestedRemedy:  RemedyEnd:  Response: ResponseEnd:  PPlease enter prefix for Summary report:  to_ _tilde.til 4All tilde reports complete 6The dispatch table is emptyI qO\Uw}FJc p  NY Y OldCommentIDNextCommentID1\VBA\VBA6\VBE6.DLLVBA  10J_N? 3C:\Program Files\Microsoft Office\Office\MSACC9.OLBAccess  1@^F=C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO\DAO350.DLLDAO QP0FgofHoundDoggingC:\WINNT\System32\stdole2.tlbstdole  Q`WFCC:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLBVBIDE y pJդOhWLդOhW;@KդOhWEC7?gofFinalReportsAC7?Label3131?FormSC7?DetailLabel0BC7?Box2Label2B|{3@B|{3@Index*********** |{3@B|{3@Dispatch00000000000 C|{3@|{3@Commenter--Full>>>>>>>>>>> B|{3@|{3@0CloseEandTcommentsDDDDDDDDDDD j{{3@|{3@ClauseList44444444444 Aj{{3@j{{3@~sq_rVoterStatus@@@@@@@@@@@ @j{{3@j{{3@~sq_rVoterNames>>>>>>>>>>> ?j{{3@j{{3@~sq_rSummary88888888888 >j{{3@j{{3@~sq_rStatusReportBBBBBBBBBBB =j{{3@j{{3@~sq_rSignatureReportHHHHHHHHHHH <G{{3@j{{3@~sq_rRough import check report\\\\\\\\\\\ ;G{{3@G{{3@~sq_rReportByCommentIDLLLLLLLLLLL :G{{3@G{{3@~sq_rHotItems::::::::::: 9G{{3@G{{3@~sq_rCommittee reportJJJJJJJJJJJ 8G{{3@G{{3@~sq_rBig-Font Committee report\\\\\\\\\\\ 7G{{3@G{{3@~sq_ffRough66666666666 6G{{3@G{{3@~sq_ffMain44444444444 5#J{{3@#J{{3@~sq_ffDispatch<<<<<<<<<<< 4#J{{3@#J{{3@~sq_cfHoundDogging~sq_cTypeList^^^^^^^^^^^ 3#J{{3@#J{{3@~sq_cfHoundDogging~sq_cConfirmationListnnnnnnnnnnn 2#J{{3@#J{{3@~sq_cfFinalReports~sq_cTypeList^^^^^^^^^^^ 1#J{{3@#J{{3@~sq_cfFinalReports~sq_cClauseListbbbbbbbbbbb 0 {{3@#J{{3@_GetAllComments>>>>>>>>>>> / {{3@ {{3@Admin*********** . {{3@ {{3@mCommitteeReport@@@@@@@@@@@ - {{3@ {{3@VoterStatus66666666666 , {{3@ {{3@VoterNames44444444444 + {{3@ {{3@TR Commenter88888888888 * {{3@ {{3@Summary........... ) {{3@ {{3@StatusReport88888888888 ( {{3@ {{3@SignatureReport>>>>>>>>>66 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 _Y5NY  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  g] 6 ; 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_ _ti@ B @ A@" A!ĀA .BD"!"$DQ"2D%E@)xfjֺ\TҺgLũf*Zi* xLVAL6X.d<  ` ( | F  w =  `*F ,vKZModify the clause heading with adjectives that are more appModify the clause heading with adjectives that are more appropiate or merge the clauses together, if they are the same.Replace "voice and data" in Absract with "multi-media and data" or just "multimedia".add after data types. "and is designed to support addtional physical layers as might be specified at a later time."Please change the first sentence in this clause to: "The DEV MLME, upon receiving this primitive, sends a DISASSOCIATION-REQUEST command frame to the PNC, sets the MAC to its initial conditions and clears all of its internal variables to their default values."Please change the text to: The primitive is sent by the DME to its MLME to reset the MAC to its initial conditions.Please remove MLME-Disassociate.confirm and its subclauses.Please remove ReasonCode from Table 11.Please change DeviceID to DeviceAID; data type to: Integer; valid range to: 1-255; description to: " Specifies the DEVAID of the peer device with which the association relationship is terminated.Please remove ReasonCode as a parameter for this primitive.Please change DeviceID to DeviceAID.Please remove ReasonCode from Table 10.Please remove ReasonCode as a parameter.Please change DeviceID to DeviceAID and change the data type from MAC address to Integer with range 1-255.Povide Annex D content, PICS for voter comment and reviewPovide Annex C content, SDL for voter comment and reviewPlease address the coexistence issue/mechanism clearly.Please address the coexistence issue/mechanism clearly.Please address the coexistence issue/mechanism clearly.Please address the coexistence issue/mechanism clearly.Use the 802.11b CCA detection template in the standard.Finish the first paragraph by saying "if necessary".Refer to the remedy indicated by Rick RobertsPlease provide the details and the cipher suite clearly.Please provide the details and the cipher suite clearly.Please provide the details and the cipher suite clearly.Please provide the details and the cipher suite clearly.Refer to the remedy indicated by Rick RobertsPlease address the QoS policy clearly.Please address the QoS policy clearly.Please address the QoS policy clearly.Please address the QoS policy clearly.Provide necessary detail to implement the QoS policyAdditional work to provide the details needed to support QoS.Refer to the remedy indicated by Bill ShvodianOtherwise the PSAVE bit ... (Consistency with previous row)Allocate more bits for the fraction part of the range.I suggest that CCA threshold values should be defined depending on TX power levels similar to 802.11b standard.The 5 GHz and UWB should not be mentioned in this table to avoid confusion.I suggest that a subclause be added to Clause 5, explicitly describing how paragraph 6 of the PAR ("A goal of the WPAN-HR Task Group will be to achieve a level of interoperability or coexistence with other 802.15 Task Groups . . . it is also the intent of this project to work toward a level of coexistence with other wireless devices . . .") is satisfied.EPSSet (Consistency with previous acros)Please address the compatibility/relationship issue clearly.Please fill in the appropriate values.Please fill in the appropriate values.Please fill in the appropriate values.Define ReasonCode in Table 14;15;15;16Define ReasonCode in Table 14;15;15;16Define ReasonCode in Table 14;15;15;16Define ReasonCode in Table 14;15;15;16Change type of ReasonCode to EnumerationChange type of ReasonCode to EnumerationChange type of ReasonCode to EnumerationChange type of ReasonCode to EnumerationChange type of ReasonCode to EnumerationChange type of ReasonCode to EnumerationLVAL-f2 J ^ T g % # }E &^!, k*CR4 :$.%4D 4 0/Q o 045m :$.%4D 4 0/l@ XOrrZB6o@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.0017531TRThere are TBDs.(@ XOrrZB6o@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.0013339TRThere are TBDs.(@ XOrrZB6o@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.0010736TRThere are TBDs.(@ XOrrZB6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.00448E:@ !(@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.004210E:@!(@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.00435E:@!(@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.003932E:@!(@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.006850EM@!*@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.00597EM@!*@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.005520EM@!*@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.004922EM@!*@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.003218EM@!*@ XOuu]H6o@3@@3@  Y Maa, Yeong-Changycmaa@inprocomm.com+886-3-5165106 ext 201InProComm, Inc.002937EM@!*@ XOuu]H6o<;T{   5FCcBBDn"/@3@@3@  Y Chen, Hung-Kunhkchen@inprocomm.com+886-3-516-5106 ext 661InProComm, Inc.09175E8@!(@ XOuu\F6o@3@@3@  Y Chen, Kwang-Chengkc@inprocomm.com+886-3-5165106 ext 668InProComm, Inc.09175E8@!(@ XOss[I6o@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.099.01751T6@!6@ XO{kk]H6@3@@3@  Y Liang, Jiejliang@ieee.org214 480 4105Texas Instruments09T@!?@ XOzxxxxtaaSB6o@3@@3@  Y Rofheart, MartinMartin@xtremespectrum.com703-269-3007240-463-3306XtremeSpectrum08TR:@!0@ XOqcH6@3@@3@  Y Carmeli, Boazboazc@il.ibm.com972-4-8296504IBM077.4.31049EOtherwise the PS bit ...=@ XO}{vokffWE6@3@@3@  Y Carmeli, Boazboazc@il.ibm.com972-4-8296504IBM077.4.810544E Length (=2) Length (=3)XO{vokffWE6@3@@3@  Y Chen, Hung-Kunhkchen@inprocomm.com+886-3-516-5106 ext 661InProComm, Inc.077.4.1010734E(@!!set to 1 if they are in EPS ...XOuu\F6@3@@3@  Y Chen, Hung-Kunhkchen@inprocomm.com+886-3-516-5106 ext 661InProComm, Inc.077.4.310349EB@!b0-b4, b5-b9XOuu\F6@3@@3@  Y Chen, Kwang-Chengkc@inprocomm.com+886-3-5165106 ext 661InProComm, Inc.077.5.10.313244ET@!23XOss[I6@3@@3@  Y Chen, Kwang-Chengkc@inprocomm.com+886-3-5165106 ext 661InProComm, Inc.077.5.10.213222Eb16-b9 (typo) b16-b19XOss[I6@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.066.6.97919T@!8@ XO{kk]H6@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.066.6.8795T@!q@ XO{kk]H6@3@@3@  Y Karaoguz, Jeyhanjeyhan@broadcom.com949 585 6168Broadcom Corp.066.6.17641T@!M@ XO{kk]H6@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.055.3.71541EPINDPNIDXOrrZB6@3@@3@  Y Callaway, Eded.callaway@motorola.com+1-954-723-8341+1-954-557-7187Motorola0513EL@ !f@ XOo^D6@3@@3@  Y Carmeli, Boazboazc@il.ibm.com972-4-8296504IBM055.3.71543E%@ !".... handled within the child...XO~zvokffWE6@3@@3@  Y Carmeli, Boazboazc@il.ibm.com972-4-8296504IBM04942E EPS set*@ XOwuqookffWE6oH*W{ DImHED D+CNBez# 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@)!:@' XOwiK6L@3@@3@  Y Liu, Shawnshawnliu@inprocomm.com+886-3-5165106 ext 865InProComm, Inc.1111.2.3188TRA@(!9@& XOrrZB6W@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\F6V@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]H6M@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[I6o@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`M K HFDC|BS@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.1.24638Tu@&@2 XOugH6R@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.1.14633ER@&u@1 XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 184619T:@&Please remove.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.14610T=@&Please remove.XOugH6q@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.33413TR@&=@0 XOugH6N@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 113410TReasonCode is unnecessary.)@/ XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 11345TW@&@. XOugH6L@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.23342TReasonCode is unneccesary.=@- XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.23341T"DeviceID parm name is incorrect.&@, XOugH6J@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.23337EH@&Please provide missing xref.XOugH6I@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.1.23329EM@&"Please provide appropriate xref.XOugH6p@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 103319TReasonCode is unneccesary.)@+ XOugH6G@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.1337TReasonCode is unneccesary.*@* XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.5.1336TRN@,!l@) XOugH6E@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.53243E6@+!Please provide missing xref.XOugH6 LVALkW V  = =ɫVQ^`)tP'dt! pDt d 4t5dThe use of term "contention access period": There is already 3. (E) Page 184, line 27: replace 're-initial3. (E) Page 184, line 27: replace 're-initialization' by 're-initialization of the device'.The use of term "contention access period": There is already a term "contention period" for the same concept that is well known in 802-wireless community term.R_ALFVIN-NOTE: THIS COMMENT WAS SUBMITTED INCOMPLETE/BLANK AS SHOWN. R_ALFVIN-NOTE: THE COMMENT TYPE WAS NOT SELECTED BY THE SUBMITTER.Are the use of shall/should/may/can/will/must throughout the document in accordance with IEEE's style?The the term "IEEE" is reserved for approved standards only.It was very hard to determine exactly what text changed from D08 to D09 based on the Editor-in-Chief's usage of the FrameMaker change bar feature inside the draft i.e., Format/Document/Change Bars.Add the current date to the runningheads by the draft number for additional clarity.The 802.15.3 D09 does not uses uniformity of structure or of style when it comes to lists. For example subclause 5.1.1. has a dashed list, 6.1 uses a alpabetical listing, and 7.2.8 uses a numeric listing, etc.The terms "sub-layer" and/or "sub-clause", used throughout 802.15.3//D09, are spelled wrong.The Table of Contents and Bookmark Annex Titles are incorrectly used. E.g., "(normative)Service Specific Convergence Sub layer." should read "Annex A (normative) Service Specific Convergence Sub layer."The editor comment "ED Note: The standard description of the 802 family of networking protocols will go here." brings up the question how will the 802.15 WG depict the 802 Family as they introduce a 2nd (and 3rd) MAC sublayer to the traditional figure (see 802.15.1/D1.0.1 Figure 1)? It is important that the WG communicate their Projects and their distinct identities, one solution per problem, etc. This frontmatter subclause should be short but concise such that the 802.15.xx designations are clear to the public. The titles are clear now the figure 1 and resultant description of Fig 1 should be modified to communicate our mutiplicity of projects.Multiple clause headings with the same name. For example Overview, Scope, Child piconet, and Neighbor piconet.Clause heading do not follow IEEE Standards Sytle Manual. Only the first word is to be capitalized.The repeater service implements an overly complex scheme to increase the number of devices that are allowed to communicate in a piconet. This service does not seem to be necessary nor desired for personal operating space devices that can be repositioned to provide communication capability. In addition, the inclusion of the 11Mbps data rate ensures that any DEV that can communicate with the PNC using the default 22Mbps data rate should also be able to communicate with any other devices that can also communicate with the PNC. The ability to communicate between all devices in a piconet with the POS of the PNC can be provided without the complex repeater service.The type of equipment 802.15.3 supports is more than "voice and data".Abstract lacks mention that the standard is extensible to include alternate physical layersText describing the effect reception of the MLME-RESET.request primitive has on the local MAC entity is incomplete.Text describing when the MLME-RESET.request is generated is partially incorrect.DeviceID is an unnecessary entry in the parameter table.DeviceID is an unnecessary parameter left over from 802.11.Clauses 6.3.5.3, 6.3.5.3.1 and 2 along with Table 12 are not needed to satisfy the requirments of the disassociation protocol.DeviceID parameter name, data type, Valid range and description fields are incorrect.Missing xref to DISASSOCIATION-REQUEST command sub clause in clause 7.Missing xref to DISASSOCIATION-REQUEST command frame subclause in clause 7.Y0YM  GKw /]/isLPDHd @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@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self000000Th@&@)XOyhWD6@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 XOvhZA64LVAL ur7L0s=p)\$5 *1`^`M,@lh$$M< @ld\\ML @ l\=dl$=h:%h ()\$5 *1`^`M,@lh$$M< @ld\\ML @ l\=dl$=h:%h (Replace the current purpose witReplace the current purpose with the text from the original PARMatch the scope text with the text of the original PARRemove this statement from the document.Remove this statement from the document.Change "for a low complexity" to for low complexity"Change the Scope section of the Draft to reflect the wording of the Scope section of the PAR.MAC clauses add functions for piconets becoming overlap, considering piconets will be movingDo a global change from "group addressed frame" to "broadcast or multicast frame"Specify that a uniqueue seed is required, not a unique random number algorithm.Always use Destination Address followed by Source Address Change CTA to Destination Address followed by Source AddressClarify in Clause 5 all connection time issues. Review impact of security to see if connect time is attainable.See detailed resolution in doc 02/037r0Replace all occurrences of "contention access period" with "contention period"R_ALFVIN-NOTE: NO REMEDY WAS SUBMITTED WITH THIS COMMENT.Remove "IEEE" from the designation "IEEE Draft P802.15.3/D09" in the runningheads.Please produce D10 with the current date. Note that this commenter can provide a frontmatter and body template to TG3 that uses the PC System Clock automatically date stampiong the draft when the PDF is produced.I suggest the Editor-in-Chief review the IEEE Standards Style Manual and then entire document should be edited for uniformity. Also, note that a colon is used to introduce a list only when the words "following" or "follows" are used in the introductory sentence, or if the sentence is complete grammatically. If the introduction is an incomplete sentence, then a colon is not used.Change to "sublayer" and/or "subclause" throughout 802.15.3/D09, dropping the hyphen.The Editor needs to review the PDF creation function while in FrameMaker.I suggest that the Editor add the 'standard description' and submit a modified Figure 1 so that the WG can review and comment. If the Project 802.15.3 Editors need help e.g., Fig1.eps, etc. please advise.Requirements needed to meet the intent of the PAR.Follow the IEEE Standards Style Manual for Clause headings. Partial list of where corrections need to be made (5.3.7, 5.3.8, 6.3.8, 6.3.9, 6.3.16, 6.5.3, 10.3.2, 11.2-11.2.6, 11.2.8, 11.3.2-11.3.4, 11.4, 11.5.2, 11.5.3, A.1.1, B.3.1, B.3.2)Remove all references to repeater service: 7.2.1.10 Repeater field section on page 96 lines 12-16. Remove repeater field in Figure 12 on page 94. In section 7.2.1, change "...SECurity and repeater." to "...and SECurity." on page 94 line 26. Remove Repeater lines from Tables 61 and 62 on page 99. Remove three repeater service commands from Table 65 on page 110. Change "... SEC and Repeater ..." to "... and SEC ..." in line 50 on page 111. Remove Repeater memory from Figure 37 on page 112. Remove lines 22-23 on page 112 describing repeater memory. Change "...SEC and Repeater ..." to "...SEC ..." in line 42 on page 113. Change "...SEC and Repeater ..." to "...SEC ..." in line 38 on page 114. Change "...SEC and Repeater ..." to "...SEC ..." in lines 1-2 on page 116. Remove all of section 7.5.6, 7.5.6.1, 7.5.6.2, 7.5.6.3, Figure 55 and Figure 56 on pages 122 and 123. Remove first two sentences of the fourth paragraph of section 8.1 on page 137, lines 27-28 describing when repeater service can be used. Remove Repeater Memory line from Table 68 on page 139. Remove "including those additional streams needed to support the repeater service" from lines 2-3 on page 153 in section 8.6. Remove last two sentences in section 8.8.6 on page 159, lines 10-12. Remove all of section 8.11 and Figure 92. Remove section 8.13.3.12 on page 171 lines 20-28.LVALr E k>P3] Yp$ Tp $< )p<(`%p! p pp!  p p p! | p |p p!  p |p p!  p |padd definition for device-ID: Specifies theadd definition for device-ID: Specifies the MAC address of the DEV under consideration.have power management sub-group rewrite this sentenceAdd the definition of Super frameI suggest the term "sublayer" be used or "MLME MAC sublayer management entity".Clarify that this is true for only .15.3 systemsNeed to provide categories of services that are provided by the coordinator.also be available for sending or receiving operations "based on beacon information."change "excluding the beacon" to "when contention free period slots are not allocated to the device"change "alternate" to "neighbor piconet"change from "alternate" to "child piconet"change from "enhances" to "enhanced"after "an enhanced power save" device joints the piconet.Find an new acronym. Maybe Personal Access Space (PAS) Do a global change.Change the wording to be essentially the same as what is found in the PAR.Please use the framemaker6_body.fm template and force the running title to be used.Change AD-AD to AID - Association ID. Use "MAC Address" or "Address" for 48 bit 802 address. Get rid of DEVAddress, AssociDEVAddress, DevID Use AID for all 8 bit addresses - Source AID, Destination AID, etc. Also, SA8, and DA8 would be the AIDs, and SA48 or DA48 would be the 48 bit MAC addresses. Make this change throughout the docIf the two terms mean the same thing then use only one throughout the standard. I would recommend WPAN since it is the one most often used within the IEEE. Drop the term piconet with the standard and use only WPAN.A clause on coexistence needs to be added to the 802.15.3 standard. The clause should include, at a minimum, the following sub-clauses: 1. A sub-clause listing which wireless 802 networks are approved for operation in the same location as an 802.15.3 WPAN, and which are not approved for operation in the same location as an 802.15.3 WPAN. 2. A sub-clause quantifying the performance of an 802.15.3 WPAN that a user can expect, in the presence of the various approved wireless 802 networks. 3. A sub-clause quantifying the performance of the various approved wireless 802 networks that a user can expect, in the presence of an 802.15.3 network.Change sentence to: "Only the DEV that is receiving a unicast stream addressed to it swith ACK Policy set to delayed ACK shall send a delayed-ACK command."First of all, the referred to primitive, MLME-POWERMANGEMENT.request, is sent by the SME, it is not received by the SME. Next, Please translate this to English. It is unreadable.this draft has about 6 use of "what" and a couple of "how many" used in colloquial sense. Please change those sentences appropriately. an example is line 16, page 151.Review the use of shall/should/may/can/will/must throughout the document to be sure they are used in accordance with IEEE's style.When the D10 is produced I require that when all edits are applied and the *.book file is open the FM File/Utilities/Compare Books feature be used to compare the D09 Book to the D10 Book (all the *.fm files should be open too). The D10 should be released in a clean and compared version; a change bar version can also be released too but again it is hard for this Balloter, and maybe others, to determine exactly what text changes were made. The default for the FM compare utility is that editing marks are shown in color and with a change bar on the left side of the page. The color editing marks are used to indicate delete and insert actions to the draft. The editing marks specifies the location of the change and describes what is being changed either by using red strikethrough (to remove old material) or green underscore (to add new material)." More info: http://ieee802.org/15/pub/SB2/SB2-info.html]LVALa _ K  VI@ T aThe term coexistence is defined, yet is is not listed in clause 3. Clause 1.1 is not an appropThe term coexistence is defined, yet is is not listed in clause 3. Clause 1.1 is not an appropriate place to define terms, nor is this an appropiate document to define the term coexistence.The term interoperability is defined, yet it is not the one defined in IEEE 100, nor is this definition include in clause 3 (definitions). Clause 1.1 is not an appropriate place to define terms.The list of example devices do not include some of the key devices targeted for 802.15.3 applications: TVs, imaging kiosks, and set top boxes.The Scope section of the Draft should reflect essentially the same wording as the Scope section of the PAR.No mechanism to deal with the possible overlap of two or more piconets on the same physical channel. This would cause self interference among WPAN devices. Following scenario should be considered: 1. Two piconet initially established on the same channel when they are far away from each other. 2. How will devices detect presence of other piconet if piconets come within proximity of each other. 3. If it's possible to detect another piconet, there are several options: a. One piconet switches to another channel if available. b. Two piconets merge and become one c. Both piconet want to keep operating independently, however device in one piconet is able to communncate with device in another piconet"TM" is not needed in "WPAN(TM)s" as the first use in the title.I have concentrated on tech issues in clauses 6, 7, 8, and 11, plus general "typo patrol" throughout the document."group addressed frame" should be changed globally to "broadcast or multicast frame" since we never define group addressed frame."The method for choosing the random integer should be unique for each DEV and use the random number generator resident on the DEV." What does this mean? We need to choose a unique random number generator for each DEEV? Or do we just need to choose an unique seed.Slots have both fixed start time and durationWe agreed to change Kus to ms throughout the document. Looks like only half of the instances got update. Half still have Kus.Half the time we use "an MLME..." and half the time we use "a MLME..." Should be "an MLME." This comment applies to ALL acronyms in the draft.Source Addreess and Destination Address order is inconsistent. 6.8.1 MAC_DATA.request( DA, SA ) 7.2 Header: [... DA, SA ] 7.4.10 CTA [ SA, DA ]48 bit and 8 bit address names are confusing and inconsistent. AD-AD sounds like something that kids take Ritalin for. Address is usually reserved in 802 standards for 48 bit MAC address.The terms piconet and WPAN both seem to mean the same thing. The term piconet is not defined in clause 3 and wireless personal area network is also not defined, so it is difficult to be sure if this is the case.The standard does not address the issue of wireless coexistence sufficiently."Only the DEV that is receiving a unicast stream addressed to it shall send a delayed-ACK command." This should specify that the stream must be on with ACK Policy of Delayed ACK.What language is this in? "The current beacon number when that primitive is received by the SME is used to calculate the beacon number for the next EPSTime event and inserts that beacon number as EPSNext when building the EPS action request command."Many points in the MAC sections refer to 2.4 GHz. These would need to be changed if another PHY is implementedIt is not clear that <= 1 second connect time is achievable (especially with existing security clauses).The text between lines 36 and 41 is an incorrect description of the PNC information broadcasting function.use of "what" and "how many" in colloquial sense-NO LKJ I.IEEE 100, The Authoritative Dictionary of Standards Terms should be referenced for terms not defined in this clause."Delete the references beginning with ISO/IEC 8824-1:1995(E) on line 16 through ISO/IEC 8825-2:1996(E) on line 37. Also delete ITU-T Recommendation Z.105 on page 4, line 1.Co-existance has, in recent years, moved from a nice to have item to a must have item. Co-existance is even more important in unlicensed bands, as consumer electronics manufacturers have learned through the years, any defect in performance (for what ever reason) will result in a returned product. A returned product is worse than 'no sale' becuase there are cost involved plus a negative product image established in the consumer's mind.The later is found in Clause 4 but I suggest the Editor-in-Chief use words consistently. Also, the find and replace feature in FrameMaker makes it easy to do and more importantly it will be easier for the reader in the end.This current description would exclude stationary objects that are not located on a person, such as a projector. Make this definition the same as the previous definition.Add the following in place of "and printers" "printers, kiosks, set top boxes, TVs and other stationary items that mobile devices may wish to use."Change to "During the CFP, the PNC controls the channel access by assigning time slots to individual DEVs with each time slot having a fixed start time and duration."Change to "an MLME." Also, change all other uses of "an" and "a" before acronyms to follow the rules based on the first sound, not whether the first letter is a vowel or a consonant. From http://webster.commnet.edu/grammar/abbreviations.htm Using articles with abbreviations and acronyms: One of the most often asked questions about grammar has to do with the choice of articles  a, an, the  to precede an abbreviation or acronym. Do we say an FBI agent or a FBI agent? Although "F" is obviously a consonant and we would precede any word that begins with "F" with "a," we precede FBI with "an" because the first sound we make when we say FBI is not an "f-sound," it is an "eff-sound." Thus we say we're going to a PTO meeting where an NCO will address us. We say we saw a UFO because, although the abbreviation begins with a 'U," we pronounce the "U" as if it were spelled "yoo." Whether we say a URL or an URL depends on whether we pronounce it as "earl" or as "u*r*l."J6OlNMLLC X HGDCDV|@@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.11533E@ .,@ )XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.8525Eenhanced is correct&@ )XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.258Ef@ .;@ )XOvhZA6@3@@3@  Y Kleindl, Guenterguenter.kleindl@siemens.at43 51707 35738Siemens0234T&@ .!Include reference to IEEE P1363XO}ttdH6o@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent022316T9@ .@,XO}yn`RC6z@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum011.2210E"such" should be "such as"Comment via Ari Singer.XOugI6X@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum011.1140E1@ .M@ )XOugI6X@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum011.2210E-@.networked, such as comput-XOseH6T@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics011.114648TR@.@,XO|jj\B6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent011.1138T@.L@ )XO}yn`RC6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self011.0141E@.@,XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self011.2213E,@.Change "&" to "and".XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self010011E@.U@)XOyhWD6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments01229T@.@,XO~|zxtaaSC6@3@@3@  Y CYPHER, DAVIDdavid.cypher@nist.gov1 301 975 4855NIST011.223TR3@.A@(XO}{vrll\E6@3@@3@  Y CYPHER, DAVIDdavid.cypher@nist.gov1 301 975 4855NIST011.1137TR4@.8@(XO}{vrll\E6@3@@3@  Y CYPHER, DAVIDdavid.cypher@nist.gov1 301 975 4855NIST011.1147TR@**@(XO}{vrll\E6@3@@3@  Y CYPHER, DAVIDdavid.cypher@nist.gov1 301 975 4855NIST011.1144TR@**@(XO}{vrll\E6LVAL! " z c = D  |Yneu% (t d t  x X L4 The definition sentence does not end in a period: been modThe definition sentence does not end in a period: been modified and that the owner of the private key signed the dataThe definition sentence does not end in a period: and key distributionThe definition sentence does not end in a period: 3.49 random number generator: a device that provides a sequence of bits that is unpredictableThe definition sentence does not end in a period: the integrity of the data being associatedThe definition sentence does not end in a period: 3.45 public-key pair: a related pair of data elements including a public key and a private keyThe definition sentence does not end in a period: encryption or key establishment procedures depending on the type of key pairThe definition sentence does not end in a period: given seed that has the statistical properties of a random sequence of bits when the seed is not knownThe definition sentence does not end in a period: decryption or key establishment procedures depending on the type of key pairThe definition sentence does not end in a period: 3.36 mutual entity authentication: a process by which two entities authenticate each otherThe definition sentence does not end in a period: 3.29 key transport: a process by which an entity sends a key to another entityThe definition sentence does not end in a period: is known only by the participating entitiesThe definition sentence does not end in a period: in order to provide data integrity and source authenticationThe definition sentence does not end in a period: additional information through the creation of a public-key certificate"in a wireless personal area network" - does this definition of quality of service strictness apply to all WPAN systems or just 802.15.3."other services" - this description does not provide any information about how the piconet coordinator is different from other devices in the piconet.an eps dev will only look past the beacon on a wake superframe if there is indication in the beacon that it transmit or receive operations are to be performed.the wording that mentions "excluding the beacon" should be changed as noted below since in reduced power save, most elements (beacon, CAP, MTS) shall be listened to.the term "alternate coordinator" might be confusinguse of the term units is not consistent with terminology for the standardIt might be a bit confusing using the term "alternate coordinator." Although it is perhaps technically an AC, we should avoid confusion on namingsince active is used in power managment, there should be additional text to mention this connection.Subclause 7.4.7 refers to IEEE P1363The ASN.1 references are not relevant to this standard.POS has bad connotations and should be avoided.Missing the word "as" at the end of line 10In this text, co-existance is a stated goal of 802.15.3. However, further text can not be found to guide designers in anyway.The Scope sub-clause is required to be essentially the wording that is found in the PAR. The wording in this clause was carried over from 802.15.1 and never updated.The 802.15.1 D09 uses words inconsistently e.g., here "10 meters" and subclause 3.39, page 7, line 4 "10 m", etc. Also, TX, transmit or transmitter, (RX receive or receiver too) are used inconsistently too.I recommend not using "&" in the standard.The Editor used the wrong FrameMaker Template i.e., framemaker6_frontmatter.fm vs. framemaker6_body.fm therefore causing the running title to be omitted."Devices included in the definition are those that are carried, worn or located near the body." This description is not consistent with the definition on page 7, which states that objects within 10 m of device or person.The Purpose does not match the purpose in the PARThe scope does not match the one listed in the PAR  % KLqKJ -F_xd X:''':D $T:,4 6 T40 lhd(@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.46726E^@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.45722E@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.44720E@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.42714E@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.41711E@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.36647E@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.29629E@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.28627E_@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.17552Ep@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.9528E{@.Add the period.XOyhWD6c@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0348730E@.2@)XO~|xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments034077T@.N@)XO~|xtaaSC6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.61818T@.V@)XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.50739T@.f@)XOvhZA6 @3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.37650E5@.*@)XOvhZA6 @3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.16548Ethe word "and" is a typochange "and" to "an"XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain033.13540EK@.change "units" to "devices"XOvhZA62K d } (FsDB@ @\:$+]4+''':$kN44 64\4 64@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum033.22612TRemove second sentence:@ ,XOseH6]@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum033.2168E too wordyremove the word "very"XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum033.2064TToo wordy ...@ ,XOseH6[@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum033.1961TX@ 19@ ,XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum03550Tmissing a definitionY@)XOseH6Y@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum033.8524TH@17@)XOseH6@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics033.50739E4@1@,XO|jj\B6@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics033.8525E)@1Make singular.XO|jj\B6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp03E#@1#@)XO{kk]H6o$@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self0300534E@1@,XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self03001014E@1Q@)XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.5889E@1Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.55754Ex@1Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.54752EP@1Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.53749Ew@ .Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.51743EH@.Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self033.49737E@.Add the period.XOyhWD6ALVAL#8  K 9  q :  WxH*5?U:M @HM@L\ D  D  @ X+''':?N(( 6(0@ (lL\H@D<0 TL(I thought that we dropped the "data window." If wI thought that we dropped the "data window." If we did, we should change the text in this subclause.a covering comment should be located at the first instance of CAP to cover MTS operationpower management status is not part of join. power management is negotiated between peers so is not part of join between DEV and PNC. The text is in error. We could replace this with the ability of a DEV to support power management.It is noted that WPAN and piconet may be used with the same meaning in clause 5. Should we consistent with one or the other? Suggested is piconet although no strong preference except that piconet seems to be general term thoughout the document.There is no mention of MTS at this level and at least a brief mention should be present in the overview of operation.1. use reserved or another term rather than private 2. add clarification as to what assoc, auth, sec and acks are related tomultiple comments 1. suggest changing "private" GTS to better convey the idea. 2. need to add "for the child" in line 43 3. missing word in sentence.the second "using" seems to be extraFigure 1 starting on line 38 includes MTS1 and MTS2 elements but the text does not reflect thisWhy do we have RNG specified? Should be PRNG.There are acroynyms for both FER and PER. I do not see a distiction between a frame and a packet, so FER and PER seem to be the same.Remove 'EPS CTA', because 'EPS' and 'CTA' are already there. Otherwise you need to include also other combinations like 'EPS CTR' that can be found in the document.The term "sub-layer", used in SSCS service specific convergence sub-layer, is spelled wrong.The term "sub-layer", used in PCS packet convergence sub-layer, is spelled wrong.The term "sub-layer", used in CPS common part sub-layer, is spelled wrong.The "ACTIVE CTA" entry is to long (10char) for the standard tab setting for the acronym list clause entry.RPS - too similar to revolutions per sec.PCS - common term used in the wireless telecom arena.Imm-ACK - to provide a short term try using ImAck. This would make it consistent with my suggestion in comment 7 (DlyAck).Del-ACK - 802.11e had used DlyAck for this term. To allow new readers to easily determine functionality similarities between different standards, like terms should be the same.The first version of SDL was issued in 1976. Anything 25 years old should not be called modern.reduced power save - sounds like it saves less powerDidn't we change random number generator to pseudorandom number generator?Q in Quality of sevvice is capitalized, but not S"device" should not be used in the definition of "device"definition for enhanced power save seems incomplete. Does differentiate EPS from RPS.unclear sentence structure ... not sure what is the correct definitionNot clear when referening mto a radio transmitter.The word 'enhances' should be singular.Add the definition of Super frameThe sentence "For the purposes of this standard, the following terms and definitions apply. IEEE 100, The Authoritative Dictionary of Standards Terms should be referenced for terms not defined in this clause." needs to be italicized.The acronym "MLME MAC layer management entity" uses incorrect definition. The Medium Access Control refers to a sublayer of the Data Link Layer and is not a layer.The definition sentence does not end in a period: tion/decryption and/or integrity protection/integrity verification depending on its intended useThe definition sentence does not end in a period: 3.55 source authentication: authentication of the sender of the dataThe definition sentence does not end in a period: and the source of the signer* @ \ } 2`Y(**9qaAɥ a6! #@3@@3@  Y Kleindl, Guenterguenter.kleindl@siemens.at43 51707 35738Siemens04943E@1Remove 'EPS CTA'XO}ttdH6o@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics0441021ENeed definition of OIDOID object identifierXO|jj\B6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self0400119E^@1,@,XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self04001023ES@1,@,XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self0400921EL@1,@,XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self040098El@1@,XOyhWD6i@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments04E!Add SFNext to the acronym list.DefineXOzxxxxtaaSC6oh@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments041049E+@1Find another TLA.XO|xxtaaSC6og@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments041023E7@1 Find another TLA. Maybe PCSL.XO|xxtaaSC6of@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments04954E}@1 Use ImAckXO~zxxtaaSC6oe@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments04931E@1 Use DlyAck.XO~zxxtaaSC6od@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0494EAD-AD is a strange acronymV@,XO~|zxxtaaSC6o]@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.56Eb@1,@,XOugI6\@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.50739E6@ 1W@,XOugI6[@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.49737EL@ 1A@ ,XOugI6Z@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.47E3@ 1Change to Quality of ServiceXOugI6Y@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum033.15545E;@ 1+@ ,XOugI6 !M! D g HFIQD{ @ @:$%4$ T4 $ L $ Qo ')4 5+''':$(N 6*:$X +A@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.3.2144849E@@5t@ 4XOvhZB6@@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.3.1143436E@5@ 4XOvhZB6?@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.31423E@56@ 4XOvhZB6>@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola055.2142EC@5[@4XOvhZB6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.5.4174Tf@"1remove "data window of the"XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.0EZ@!1@4XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.5.21642TR@ 1@4XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.013E@12@4XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.41611Ew@1@4XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.3.81554T~@1W@4XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.3.71542E@1z@4XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.3.31512E&@1R@4XOvhZA6 @3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain055.3.11434Ea@1E@4XOvhZA6 @3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum04E0@1"Delete RNG and replace with PRNGXOugI6@3@@3@  Y Shellhammer, Steveshell@symbol.com(631) 738-4302Symbol Technologies04910TR@1@,XOll\J6o_@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum041041EAdd term "OID"OID = object identifierXOseH6$@3@@3@  Y Kleindl, Guenterguenter.kleindl@siemens.at43 51707 35738Siemens0410Emissing: OID, PSRC, SFNextadd OID, PSRC, SFNextXO}ttdH6oLVAL(i , t  n 4 i*vN*CS!kC nEtmIAi!IqYq  9!!A""change DEV to device (DEV) Is there some to tochange DEV to device (DEV) Is there some to to automatically check the first use of acronyms?Power is removed from all the DEVsIt is possible, for many reasons, that the PNC function will be transferred.... from the PNC during the CAP or MTS.change to ... Data is sent using either by a streamless asynchronous exchange, or by ...add "ssh" to clause 4 ... off-hand I do not know what ssh means.Contention Free Period (CFP), which is composed of ...add additional text to clarify meaningadd verbage or mechanism to include authorization from a higher layer?Change 'parent piconet' to 'parent PNC'.merge the two blocks in CAP to one with the content "Command/Data"Add "MAN metropolitan area network" to Clause 4.I suggest a figure be created and added that depicts the components of the IEEE 802.15.3 WPAN.I suggest the sentence be changed to "Additionally, WPANs have the expected wireless medium differences as found in the following paragraphs."Add the period and change the lists to be consistent i.e., all ordered or all unordered.Change the term to "GTS 2" (adding a space) to match GTS 1, GTS N, etc.Explain why this possible operation? Explain why it is necessary.Add disassociation command to 5.4.Provide consistency in document terms.More explanation needed here to determine benefit of this functionality.If this term is going to be used, define it in the acronyms.Clarify figure and explain in the section.Please explain what the point being driven in this paragraph.Remove the paragraph or drive a point.Delete the paragraph or add some content.Change "... removed removing power ..." to "... removed by removing power ..."Replace this section with: "Asyncrhonous or synchronous data streams are established for use in the CFP by the allocation of GTSs. The PNC manages allocation of GTSs based on the DEVs requirements and the DEVs then use the GTSs as needed. These streams are established by a connection process."Change "is sent using either by" to "is sent either by".Change "... with the PNC and then with any other DEV with which communication is required." to "... with the PNC."Change the two lines to: - Connection Access Period (CAP) when allocated. - Connection Free Period (CFP) when allocated. followed by: The superframe will always have a Beacon and at least one CAP or CFP, and may have a Beacon, CAP, and CFP in that order.Remove sentence on line 23. If desired to include a statement about QoS, include as an additional bullet the following: A proceedure to allocate bandwidth and fixed time slots to support establishment of data streams that can guarantee repetitive allocation of bandwidth required for isochronous connections.Change "quality of service (Q0S)" to "quality of service (QoS), security, and power save"Don't know exactly where but add "Throughout this clause, when CAP is referenced, the capabilities that CAP would provide may be alternatively provided by Management Time slots (MTS)change the text to "its ability to support power management " and remove "it power management status (whether it needs to power management or not"change multiple instances of "WPAN" to "piconet"add 5.4.3 MTS operation The stanard provides an alternative to CAP through the use of management time slots (MTS). Management time slots are located within the CFP.1. change "private" to "reserved" 2. after acknowledgments, insert "for the neighbor"1. change "private" to "reserved" 2. after acknowledgments, insert "for the child" 3. at beginning of line 47, add "to"omit the second instance of "using" on this line. Perhaps drop "either" as well.add after CAP - "or an alternate management time slot (MTS) method"LVAL : A" C?WA  I @8Y  ppp  Is this section reaIs this section really the same as 5.4?How does 5.4.1 and 5.4.2 relate to this paragraph."... stopping a piconet." - based on 5.6.1, this should be ending a piconet.What is the last statement saying? The point is not clear.Figure needed to communicate quickly the available operation modes.Description here is the same as a child piconet. It makes it hard to understand why a neighbor piconet is needed and why it is technically beneficial. If the complexity is to be added to provide this functionality, there should be a strong explanation of it's benefit.A figure showing how a neighbor piconet relates to the original piconet is needed here.A figure showing how a child piconet relates to the original piconet is needed here.What if none of the remaining devices have the capability to be a PNC? Does the piconet disappear?How does a device know when to expect to transmit or receive? Need more intro information to understand this feature."connection process" - this is not a descriptive discussion. Is it special? Are there any key features?"streamless asynchronous exchange" and "asynchronous connection" - how do these terms differ? It is not obvious at this point in the document. Also, define what is meant by "small amount of data". Different people would have a different tolerance for data size."... e.g. ssh ..." - what is ssh?Does this paragraph indicate that the defined method could be over written by a higher level protocol?"authenticate with the PNC and then with any other DEV ..." - the listed models only authenticate with the PNC, not with other DEVs.Are GTS and MTS packets randomly intertwined? Figure is unclear? If this level of detail exists in the figure, it should be explained in the section.A WPAN only requires 1 device? or is the WPAN formed when a complete response if received from another device interested in joining a piconet?Why is this sentence not a bullet? It does not have enough information to stand alone as a paragraph.Bullets should be in same order as they are listed in the subsections."Propogation effects ..." - The message of this sentence is unclear."For technical reasons, ..." - what technical reasons?This paragraph describes a potential implementation. Unless this point drives a specific requirement to come, it should be excluded.This paragraph does not add anything to the text.The PNC does not allocate 'bandwidth'. It does allocate time slots in which a pair of DEVs can use any of the supported bit rates in order to obtain an effective throughput rate from the available raw bandwidth and the amount of error recovery required by the effective BER of the channel.DEVs are not required to authenticate with any other DEV with which communication is required. Instead, once a DEV is authenticated with the PNC, it belongs to the authenticated devices in the piconet and may utilized the resources of the piconet to allocated time slots and communicate with other DEVs in the piconet.The use of the CAP and the CFP are optional based on how the PNC allocated time in the superframe. In section 8.4.3.3, page 151, line 4-5 it is noted that "the PNC is responsible for choosing the CAP size if a CAP is used." In section 7.4.2, page 102, line 47-48 states: "The CFP duration is the time allocated to the CFP ... has a range of [0-524280] uS." This makes use of the CAP and the CFP optional as defined by the PNC.The data transport does not explicitly support multiple quality of service levels with optional priority. There is an SSCS that could be used to map prioritized QoS service traffic to specific GTS allocations, but this is not done in the MAC.PNC management does not include security nor extended power save.^<U  8 [GFD,G`z@ @ @ @ @ @``````````````````````````````````````Y``````````@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.61532Te@5Finish explaining all cases.XO}xtaaSC6w@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.51524Ex@5More explanation needed.XO}xtaaSC6v@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.41520Ek@5More description desired.XO}xtaaSC6u@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.31512E @5Needs more explanation.XO}xtaaSC6t@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.2157E$@5>@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.:@ 4XOvhZB6$H|M  9 VnG >C%:H<%  95B:8<%:H<%\d $\ 0&Qo% @3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.1.11326ER@ 8Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.1.11324E@8Add the period.XOyhWD6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments05EK@8XOzxxxxtaaSC6o@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments055.6.11738T@8D@4XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments055.61727Eb@8$@4XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments055.51714E\@8 See aboveXO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments055.21643E[@8Change suggested above.XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments055.21642E`@8Remove "to".XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0551627TR;@8Provide state flow diagram.XO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments054.21624El@8Provide clarificationXO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0551627E)@5Look at combining sections.XO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0541611E4@5Check section flow.XO~zxtaaSC6~@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0541612EN@5(@4XO~zxtaaSC6}@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.8166E=@5Clarify statementXO}xtaaSC6|@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0541610EE@5Provide figureXO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.81549T@5J@4XO}xtaaSC6z@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.81549EY@5Provide figureXO}xtaaSC6y@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments053.71538EV@5Provide figureXO}xtaaSC6LVALYB  ( ` + lQr$ @ @ @qrstuvwxyz|}~'q&I&'&.AiA@4The complexity of supporting the child and neighboring piconet capability seems high. There doeThe complexity of supporting the child and neighboring piconet capability seems high. There does not seem to be any significant value in either since it does not increase the overall capacity.Don't understand what the text is trying to say "The PHY is unprotected from outside signals."A node needs to be authenticated, then authorized before it can join a network. The following statement: "If the beacon indicates a piconet of interest to the DEV, it will attempt to authenticate with the PNC. Upon success, it is considered to be in the WPAN." does not refer to authorization.This refers to a parent piconet ending a subsidary piconet, however it is the parent PNC that can end the subsidary piconet.CSMA/CA is not defined in the document.Some of the list of states (association, authentication, stream connection, etc.) are more device actions than WPAN states. Thus 'disassociation' should be included.'ssh' is not defined either here or in clause 4.command and Data in CAP is confusing: makes the reader think all the commands are tx first and then the datause of "multiple levels" is confusing and for some converningThe term metropolitan area network (MAN) is used but it is not defined in Clause 4, however, the WAN, LAN, and PAN are.The text that describes the components of the IEEE 802.15.3 WPAN is clear but I was expecting a figure that depicted the components of the WPAN being described.The word "wireless" in the sentence "Additionally, WPANs have the expected wireless differences as found in the following paragraphs." should be clarified by adding "medium".The following sentence does not end in a period:  Power is removed removing power from all the DEVsThe following sentences do not end in a period: a) Open - no authentication is required and data is not encrypted by the MAC b) Authentication - DEVs authenticate with the PNC before they have access to the piconet s resources. Data is not encrypted by the MAC and why are the Clause 5 lists different i.e., subclause 5.3.1 unordered and 5.3.2 ordered. Refer to IEEE Standards Style Manual, 12. Homogeneity, pg. 14.The term "GTS2" in Figure 1 is inconsistently used.The following sentences do not end in a period:  Beacon  Contention Free Period (CFP). This is composed of data streams, either synchronous or isochronous, with quality of service provisionsThe following sentences do not end in a period:  Allow DEVs to form and terminate PANs  Transport data between DEVs  Authenticate DEVs with each otherThe following sentence does not end in a period: The WPAN has a dynamic topologyThe following sentence does not end in a period: conformant PHY transceivers are known to be unable to receive network framesThe flow of this section needs to be revisited. It does not read easily.Why would the PNC of the former child piconet immediately form a new piconet if it did not choose to continue operation after the parent piconet disappears? Isn't this the same as removing the parent device ID element and continuing the piconet?"via the disassociation command ..." - this mode of operation should be included in section 5.4."... a new DEVs joins." - add the following: "... a new DEVs joins with more capability.""... a PNC handover could occur." - change the to state "... a PNC handover is possible.""... (whether it needs to power management or not) ..." - the "to" is not needed in sentence.How do the states relate? Is there a state flow diagram?The last sentence is awkward. Is it trying to say that sync streams have different acknowledgement modes?)M r I <IlBA @ @ @ @ @ l vvvIW@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.1.11325Ta@8(@ 4XOseH6@3@@3@  Y Kinney, Patrickpat.kinney@ieee.org724-425-7952Invensys055.216T(@8H@4XO}xtjj\G6@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics055.5.61726E~@8*@4XO|jj\B6@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics055.4.11617E)@8 Define.XO|jj\B6@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics055.41611E@8Add 'disassociation'.XO|jj\B6@3@@3@  Y Huang, Bobrobert.huang@am.sony.com201-358-4409Sony Electronics055.3.2157E2@8 Define.XO|jj\B6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp053.71541EPIND?change "PIND" to "PNID"XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp05Figure 114En@8D@4XO{kk]H6@3@@3@  Y GUBBI, RAJUGOPALrgubbi@broadcom.com408-543-3470Broadcom, corp0531423E?@8!Remove "mulitple" and "levels"XO{kk]H6"@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.11312Ey@82@4XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.2135054T@8`@4XOyhWD6 @3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.11316E@8@4XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.5.61722Ei@8Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.3.2145052E@ 8Z@4XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self05Figure 11441E5@ 8I@4XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.3.1143336E@ 8Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self055.3141315E@ 8Add the periods.XOyhWD6QN L  IFHYFVENaWlc, $  e@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.4.21625Ei@<@;XOugI6d@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.41612E;@<l@;XOugI6c@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.3.31513EJ@<change connection to streamXOugI6b@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.3.21448Ew@<5@;XOugI6a@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum05Figure 11441EM@<Change MTS N to MTS M.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum05FIgure 11441T?@<?@;XOugI6_@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.31412EPAN should be WPANChange PAN to WPANXOugI6^@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.1.11326E,@<_@'4XOugI6@3@@3@  Y Shellhammer, Steveshell@symbol.com(631) 738-4302Symbol Technologies055.315T@8@;XOll\J6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum051754TRNeed to add a clause 5.6@;XOseH6f@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.5.61722ERewrite as ...$@&4XOseH6e@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.5.51711Echange as shownN@%4XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.5.31648TRadd some text)@$4XOseH6c@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.3.3151213E grammatical[@#4XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.3.2157Tadd to clause 4B@"4XOseH6a@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum055.3.11435Egrammatical error8@!4XOseH6LVAL$,h3 D  Z o r~\*S'j p @@X aY@\ aReplace 'security-relateReplace 'security-related' by 'security-relevant'Remove the timeout parameter from the frame.Replace the concept 'DEV' by 'entity' or a similarly appropriate term throughout the clause.Change to "sublayer", dropping Please change from DestinatiPlease change from DestinationDEVAddress to RemoteDEVAID.Replace 'security-related' by 'security-relevant'Remove the timeout parameter from the frame.Replace the concept 'DEV' by 'entity' or a similarly appropriate term throughout the clause.Change to "sublayer", dropping the hyphen.Change to "sublayer", dropping the hyphen.Modify the ordered list to span "a)-c)".Change Figure 6-2 to read "MAC sublayer" and "PHY layer".Change to "sublayer", dropping the hyphen.Indicate the values are reserved for future PHYsI would like to see both jitter and delay defined.Make a clear statement to the reader of communication flow.I would like to see both jitter and delay defined.Include this term and how it relates in figure 2Add ReasonCode to Table 14 as an Enumeration, Valid Range of SUCCESS or TIMEOUT, and Description as "The result of the challenge command." Note that success here is defined to be reception of a valid Challenge.confirm frame from the peer DEV and not whether the PublicKeyProof is correct.Replace "format as device" with "format as defined"in 6.9.4.19 table 57 note that this includes the state for a fully powered PHY in 6.6.10 table 50, make the same note some text touch up may be desired so it is clear that powering up is also via the same mechanism.change "prior to association" to "after association"Update the figure to include QoS sublayer if appropriateMake basic PNC function (beacon) mandatory so two devices can at least discover each other and exchange capability.This statement should be removed or clarified.Change second sentence in paragraph to: "All data sent in the piconet uses payload protection (data integrity and/or data encryption) with the piconet payload protection key(s)." Comment via Ari Singer.Add MTS description: Management Time Slots are a type of GTS that can be used to allow communications between the DEVs and the PNC. MTS slots can either be assigned or they can be shared slots that are accessed using SLotted Aloha.Change to "Power is removed from the DEV before the DEV can perform a PNC handover."add "if allowed by the PNC." to the end of the sentence.Remove reference to "data window"change synchronous to asynchronous. Actually, do a global search on "synchronous" and either change to asynchronous or isochronous as appropriate. In 5.3.4 synchronous is used instead of isochronous. in 5.3.3 synchronous is used instead of isochronous.probably need to drop the "to" or change to "to use"Change to: Data in asynchronous streams can be acknowledged, and synchronous streams are able to request acknowledgement as well....WPAN has sevaral states of operation: An 802.15.3 WPAN has several states of operation: establishment, optional coordination function transfer, and stopping a piconet. DEVs have several states of operration: association, authentication, stream connection establishment, data exchange. These WPAN and DEV states operate around the structure of the superframe.Remove reference to authenticating with other DEVs.Remove reference to command and data from the cap in Figure 1Eliminate the child and neighboring piconet concept or alternativly include a short statement of the utility of these capabilities.5.6 Coexistence with other IEEE802 devices - Overview PHY subcommittee members need to add "overview" text that indicates how 802.15.3 2.4 GHz PHY is going to coexist with 802.11, 802.11b and 802.15.1 devices.LVAL!HL m 9   6 3 E^  f l=ai @h j@l A PHYPIB_Type includes definitions for currently undefined PHYs (5 GHz and UWB). It is good to put a place PHYPIB_Type includes definitions for currently undefined PHYs (5 GHz and UWB). It is good to put a place holder, but do not presume a solution before the SG3a group has a chance to determine future possibilities.Need to list the PHY PIB groups in this section to make it easier to for the reader to know what to expect in this section."... by the LME ..." - should this be "PLME"?"... by the LME ..." - should this be "PLME"?Is Maximum allocation delay the same thing as Jitter? 802.11e has both a jitter and a delay bound. Which is being specified here?Which way is the communication flowing? DEV1 to DEV2 or vice versa?Is MaxTXDelayVariation the same thing as Jitter? 802.11e has both a jitter and a delay bound. Which is being specified here?How does MAC CPS fit into figure 2?The 802.15.3 MAC does not support any prioritization of MSDUs delivered to it nor does it directly handle parameterized QoS requests. This section seems to be left over from earlier drafts that had an as yet undefined model for QoS that was not accepted.The MLME-CHALLENGE primitive parameters does not include the ReasonCode parameter'device' used instead of 'defined'the text of both when generated and effect of receipt seems to have been pasted from elsewhere and does not match the power managment of this sub-clause.It is not clear, how a PHY may be returned to the powered state. This primitive is specified for placing the PHY in one of several available power states. It is recommended that the primitive also serve to restore full power. As an alternative, an additional primitive may meet the requirement.Text mentions that information is available prior to association. In fact, the power management information is a post-assocation process.It would seem that the reference model should include something like a convergence layer for QoS.Operation of draft HR WPAN requires presence of a PNC. If a person owns two WPAN devices but neither of them are AC capable, then his/her products will be useful only when someone else's PNC shows up and is generous enough to provide the functions/services.Does this suggest any 802-compliant wireless devices can operate as a 15.3 neighbor piconet and solve co-existing issue?Again, privacy should be payload protection.Saying that the data is "encrypted" is not really what one might want. Entities may want to know that the transmission came from the appropriate person and wasn't tampered with (data integrity) and/or have the data encrypted. We should allow for these different combinations of integrity and privacy.Should say "Additionally the PNC manages the quality of service (QoS) requirements and authentication requirements of the WPAN.""Power is removed removing power from all DEVs" does not make senseasynch data is only allowed in the CAP if the PNC allows it.there is no "data window" in the CAP"during the CAP" should be "during the CAP or MTS"synchronous stream should be asynchronous stream"whether it needs to power mangement or not" is not proper grammarData in asynchronous streams does not have to be acknowledged. Broadcast streams are not acknowledged.WPAN operation states and DEV operations have been mixed."asynchronous connection" and "isochronous connection" should be streamauthenticate "and then with any other DEV with which communication is required" is inconsistent with security clause.GTS N and MTS N make it look like there are an equal number of MTS and GTSsCAP is devided into Command and Data - inconsistent with textFirst use of DEV shouls say "device (DEV)"8&+ @ U h ] [pGFEDC C)BEAh @ @ @qrs<@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola06Table 133517E$@<5@;XOvhZB6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain066.9.4.19.19219TR@<S@LXOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain066.9.4.19921TR(@<@;XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain066.3.1.12330TR@<6@;XOvhZA6@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain06figure 21918Tc@<:@;XOvhZA6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America052141TR@<u@;XObkk]G6@3@@3@  Y Young, Song-Linsyoung@sharplabs.com360-817-7509Sharp Labs. of America055.3.8164TRz@<0@;XOkk]G6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.5.2163940T.@<@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.3.2152T0@<@ ;XOugI6{@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.2142E@ <Comment via Ari Singer.XOugI6l@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.4.31627ENeed to add a section on MTS@ ;XOugI6k@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.5.61722EE@ <V@ ;XOugI6j@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum055.5.4174E>@ <:@ ;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@;XOugI6#O.NV LK JW 6O{$ d0+:h%x$ `x ,x0$@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self06Figure 2192829E@?;@;XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.1196E@?,@;XOyhWD6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments069.4.118830Er@?FixXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments06Table 548411E.@?add "(see Table 56)"XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments06Table 54848E.@?add "(see Table 55)"XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0688044T~@?Add MAC CPS SAP to Figure 2.XO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments067.1.1808Es@?List the service classes.XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments06Table 417640E@ <2@;XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0667551E}@<List PHY PIB groups.XO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments064.5743E/@<XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments064.17147E/@<XO}xtaaSC69@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments06Table 265542TR@<4@;XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments06Figure 3541EF@<=@;XOxtaaSC68@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments06Table 234949TR@<4@;XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments061.1205T%@<2@;XO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments061.1207ESSCS needs to be definedXO}xtaaSC6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola066.7.2801824TR@<Remove Section 8.7.2.XOvhZB6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola06Table 14370TRS@<"@;XOvhZB6%LVAL!A  ^ n  N F`P[)3guts_ClickErr_gofFinalReports_ClickThe paragraph defines the functional description of the scan process that is already adequately defined in clause 8. TThe paragraph defines the functional description of the scan process that is already adequately defined in clause 8. The redundant description is an abomination to the technical editor and will cause woe, wailing and gnashing of the teeth.No such thing as a generic PNID. This is handled by the OpenScan parameter.The power managment changes come about as a result of changes in the beacon, not from direct communications with other DEVs.Power managment commands are relevant only in the context of an associated device.Change MLME-DEV-INFO to be MLME-PROBE-DEV since that more closely reflects the command name.Add a table with definitions of the parameters for these commands.Should list all of the SAPs in this enumeration.The figure does not include the SSCS layer.The CCA threshold should depend on the transmitter power, which can be changed.The assignment of 5 GHz and UWB PHY layers presumes too much. It is not clear if there will be another PHY layer, if so what format it will be or what it will be called. If a new PHY layer is added, the new draft can add its definition to the PIB. It is not required at this time.The parameter CapabilityInformation field is listed in the primitive but is not defined.The following sentence does not end in a period:  NoError. This value is used to indicate that no error occurred during the receive process in the PHYThe following sentence does not end in a period: The effect of receipt of this primitive by the MAC is unspecifiedThe following sentence does not end in a period: The effect of receipt of this primitive by the MAC is unspecifiedThe term "sub-layer", used in the subclause title "...This sub-clause provides an overview of the PHY services."The following sentences do not end in a period: "device and the intended recipient devices" and "However, it does not maintain ordering among MSDUs belonging to different streams"In Table 41 the terms "UWB and ETSI, FCC, IC, ARIB" are introduced for the first time and are not defined in this clause and/or Clause 4.The following sentence does not end in a period: primitive parameters are defined in Table 28The following sentence does not end in a period: The parameters for this command are defined in Table 2The following sentence does not end in a semicolon: primitive are as followsThe following sentence does not end in a period: The parameters for this command are defined in Table 2The following sentence does not end in a period: The parameters for this command are defined in Table 2The following sentence does not end in a period: The parameters used for these commands are defined in Table 2The term "sub-layer", used in the subclause title "...personality of the sub-layer, hence the acronym PIB.", is spelled wrong.The term "sub-layer", used in the subclause title "6.1.1 MAC common part sub-layer (MAC CPS)", is spelled wrong.The ordered list starts at "d)" which is incorrect it should be a).In Figure 6-2 the term "MAC sub-layer" and "PHY sub-layer" are incorrectly used; it should be MAC sublayer and PHY layer, respectively.The term "sub-layer", used in the sentence "Both MAC and PHY layers may conceptually include management entities, called the MAC sub-layer...", is spelled wrong."PHY has begun the CCA process." - shouldn't this be "ended the CCA process"? Possible cut and paste oversight."A set of parameters" - not very descriptive"A set of parameters" - not very descriptiveMAC CPS SAP is not shown in Figure 2. It is hard to understand how it fits in without seeing the relationships pictorially.It is indicate that two services classes exist. This is an introduction paragraph, the classes should be listed.'Py )Pduel180N Option181'Label182P Option194'Label195x Option196'Label197zDblClickClick@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.6.17642T@?+@HXO}yn`RC6%@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.12.14745TZ@?,@HXO}yn`RC6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.9.4.189133E@?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.9.4.11.28844Et@?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.9.4.9.2888Et@?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.9.38246Er@?,@HXOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.7.3803942E@?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self06Table 417643E@?@HXOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.3.166126E_@?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.3.1.32534Ei@?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.3.1.32528EN@ ?Add the semicolon.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.3.1.22514Ei@ ?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.3.1.12346Ei@ ?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.3.12324Ep@ ?Add the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.22024E@ ?,@;XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.1.1205Er@?,@;XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self066.1194648EE@?*@;XOyhWD6]  % 9 B RIgK^Fb\dCuBz@Jl the@L\ w@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 22417En@,b-@hXOugI6v@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 223EK@+bPlease clarifyXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 22412T+@*b6@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 22419T&@)b ClarifyXOugI6s@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.1.1.1247EN@(bChoose better wordingXOugI6r@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table2245E^@'bPlease ClarifyXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.1.1.224Ti@&b@hXOugI6p@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table1222335ETable is missing some linesFix the tableXOugI6o@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.1.1207EU@%bU@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Figure 21918Tc@$b@hXOugI6m@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.1196E>@#bremove "may"XOugI6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 3976TR^@"b@.dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.9.4.19923E grammatical'@-dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.9.4.12896TR@!b=@,dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Tables 55 and 5684TX@ b@+dXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 5584TRUnused parameter ...@*dXOseH6-A 3 I [ o {F<  w M ! y M # y O % ???v~?? @3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.4.114627E"an RIFS" should be "a RIFS."0@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.4146TR@/@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.414622TRM@I@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum08TR@m@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.41462Tk@3@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.414554T)@u@XOugI6s@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.3.314548T&@9@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.3.214529EG@G@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum08Figure 8314444TR)@"_@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.3.21445E0@!@XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.3.114348EP@ E@ XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.2.6143T|@i@ XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum08Figure 8214321EA@Change to Neighbor Beacon.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.2.4141TRu@w@ XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.2.4TRx@g@ XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum088.2.4141TRT@Z@ XOugI6O                                                                                                                              !"#$%& '!(")#*$+%,&-'.(/)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-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{|}~      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%FELVAL)T  w ~ 1 y821[#P{B`x Delete the word "authenticated" from line 19, 20, 36 aDelete the word "authenticated" from line 19, 20, 36 and 37 all on page 66 (i.e. every occurance in 6.3.18.1).Delete ChannelIndex from the semantics of the primitive and delete "on the indicated ChannelIndex" from line 21.Change "DestinationDEVAddress" to be "RemoteDEVAddress"Add the following as the first row: RequestorDEVAddress MAC address Any valid MAC address The MAC address of the DEV which is requesting the channel status. Add "TIMEOUT" to the valid range for ReasonCode.Change the 3 entries as follows: Type Valid range Description Enumeration SUCCESS, TIMEOUT Indicates the result of the stream termination command.Copy the definitions from table 25 for StreamIndex and SlotStartTimeSet into a table in 6.3.13.5Delete the DeviceID primitive parameter from the semantics and table 18.Delete ReasonCode from the semantics of the primitive in two places, page 44, line 49 and page 45, line 39 (in the .indication primitive).Add the "TIMEOUT" to the valid rangeChange "de-authentication process" to be "de-authentication process or the MAC entity which is requesting de-authentication"Delete the sentence "The DME shall ... command."Add the following to the end of table 16: ReasonCode Enumeration SUCCESS, TIME_OUT Indicates the result of the distribute key command.Change "which which ... process" to "to which the key will be sent"Add a row to the end of the table which is: ReasonCode Enumeration SUCCESS, NOT_AUTHORIZED, Indicates the result of TIME_OUT the key request commandAdd acronyms for KEK, DEK, DIK and SEED to the acronym clause.Change "with which ... process" to "that is requesting the key"Add the following row to the table: Reason code enumeration SUCCESS, FAIL, Indicates the result of TIMEOUT the challenge commandDelete the entire command. If not, delete the ReasonCode, since by definition it is set to SUCCESS for this command to be generated. Also, change the description of AssocDEVAddress to be "The allocated device address of the DEV that has been associated." since the association was successful for this command to have been issued.Delete the sentences "The time spent by ... and aggregated into a PiconetDescriptionSet.Change "from a specific peer MAC entity" to be "from the PNC" Also change "result of acommand ... in the piconet." to be "result of a change in the beacon."Change "to the DEV prior to association" to be "to the DEV after association"Change as indicated here and in 6.3.19.Add the following defintions: Name Type Valid range Description PIBattribute octet string Any PIB attribute as The name of the PIB defined in 6.5 and 6.6 attribute PIBvalue variable as defined in 6.5 and 6.6 The PIB value status enumeration SUCCESS, INVALID_PIB_ The result of the ATTRIBUTE, READ_ONLY_PIB_ command. ATTRIBUTE, WRITE_ONLY_PIB_ ATTRIBUTEAdd SSCS SAP, MAC SAP and PHY SAP as items a and b (and fix numbering).Replace the figure with the one from A.1 or modify it to include the SSCS layer.Delete the assignments for 5 GHz and UWB.Delete the parameter CapabilityInformationChange to "sublayer", dropping the hyphen.Please add "UWB ultra-wideband and ETSI European Telecommunications Standards Institute, FCC Federal Communications Commission, IC Industry Canada, ARIB Association of Radio Industries and Businesses" to Clause 4.@NoML J#J-IVHGGt @ @ @ @ @8OQQNHGLZKZPEZ_ZRQDDLKZNLJRTE553b95083bF@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.10.14434T3@J~@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.9.2.24345T:@J2@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.94247T3@J@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.94235T(@JE@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.84025T-@J@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.84013E&@J@@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.84011T%@JA@ HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.73754TThe reason code is missing.@ HXO}yn`RC6!@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.4.5321T@JM@ HXO}yn`RC6 @3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.2.1.22642T@ ?Z@ HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.2.12621TN@?!Delete the words "generic or a"XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.1.32527T~@?@ HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.1.12331TT@?O@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.32319E^@?)@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.22034TD@?@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.11944T2@?I@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.11920T-@?R@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.6.8795TQ@?Change "Static" to "Dynamic"XO}yn`RC6LVAL6. [! q  9  V o A q 0 aXd"k<f-{EbDs CommentID={IsNull cmd_QuickFindERecordsetClone8 FindFirstM=NoMatch/3 DefaultValue*BookmarkCcmd_QuickFind_DblClickThe sentence fragment "...and a dThe sentence fragment "...and a directed frame with null payload..."AssocDEVAddress parameter name is incorrect.xref to ASSOCIATE-RESPONSE command frame type is missing.No xref to ASSOCIATION-REQUEST command frame type.AssociationTimeOutPeriod has an incorrect data type.AssocDevAddress is inconsistent with its data type.DeviceID is inconsistent with its data type.The functional description of the MLME-SYNCH.request primitive is incomplete.The parameter name " Parent Device ID" is inconsistent.The parameter Channel is incomplete.The Beacon Period data type is incorrect.DeviceID is inconsistently used through out the document.The last sentence of the ChannelScanDuration description is not needed.The definition for PNID is partially correct.The OpenScan paramter is unneeded.OpenScan is an unneeded parameter.The MLME-NEW-PNC primitive is missing from Table 1.The MLME-PNC-HANDOVER primitive is missing from Table 1.The MLME-DEV-INFO primitive is in the wrong location in Table 1.The MLME-REMOTE-SCAN primitive is missing from Table 1.The MLME-CREATE-REPEATER primitive is missing from Table 1.MLME-Tx-POWER-CHANGE primitive is missing from Table 1.The MLME-START primitive is in the wrong table position in Table 1.The MLME-RESET primitive in Table 1 is in the wrong table location.The MLME-POWERMGT primitive in Table 1 is in the wrong location.PHYPIB_CCA_Threshold is programmable but not enough guidance as to what values it should assume has been given in the standard.5 GHz and UWB are assumed to be future spectral bands to be used without any justification or mention given apriori. How can a current standard have mention of specifics of future standardThe descriptions of When generated and Effect of receipt are copied from another sub-clause and are incorrect for this one.The AntSelect parameter is already defined and we don't need any more ants at our picnic.The criteria given are not applicable to this standard.The definition of the DATA parameter is redundant and annoying.This sub-clause is redundant and therefore really irritates the technical editor while simultaneously promoting bad habits.There is only one type of primitive defined in the PHY service specification now.Multicast is not supported in this standard.The sentence "The ReasonCode ... for failure." does not belong here since it has been put into the table.The definition of the ReasonCode is incorrect.The use of the probe request does not require that a DEV be authenticated.The ReasonCode needs "TIMEOUT" added as part of its valid range.ChannelIndex is an invalid parameter for a status report since all DEVs in the piconet use the same channel.DestinationDEVAddress does not match other usage.The RequestorDEVAddress is not defined and the ReasonCode is missing an enumeration.The definition of the ReasonCode for terminate stream is incorrect.The primitive parameters for MLME-STREAM-CTA.indication are not defined.The DeviceID of a DEV is set through the PIB commands and should not be set here.The de-authenticate command does not use a reason code.The valid rane of the ReasonCode for de-authenticate is incorrect.The DeviceID parameter description is inaccurate.The MLME-DISTRIBUTE-KEY.response command does not exist.The ReasonCode for distribute key is not defined.The DeviceID description is incorrect.The reason code for request key is missing.Acronyms for KeyPurpose not defined.The device ID purpose is incorrect.This command is unecessary. When an new DEV associates, the PNC sends out the new DEV info table anyway. A DEV may not even be listening for association response frames since it has already been associated.*T~  . Z p E8e Comment Status Response Status X D A R O W C, U, Z Chief Signatu@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.9.4.12.18918T9@Jr@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.9.4.48611TThere is no PLCPB@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.9.4.18451TA@JV@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.9.3.1831T}@JG@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.9.38246TS@J@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.7.1.1804T.@J@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.19691Tk@JDelete the sentence.XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.196850T0@JX@LXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.18.16619TL@Jp@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.186615TB@JChange as indicated.XO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.16.1628Tn@Jr@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.16.1628T3@J9@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.166131TV@ J@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.15597TE@ J@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.13.55310TJ@ Jb@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.11.14610TS@ JJ@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.10.14449T9@ J@HXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent066.3.10.14436TD@J&@HXO}yn`RC6LVAL\ } ? e t  zQ< Gk @ @  @ (@ $ @Please change AssocDevAddress to DeviceAid which is short for DevicPlease change AssocDevAddress to DeviceAid which is short for Device Assoiciation ID. Also change the data type from octet to integer.Please change DeviceID to DeviceAddress since its data type is MAC address(48bit)Please change the first sentence to this: This primitive is used to initiate a local synchronization with a specific piconet beacon only when the PNID is set to 0xFFFF.Please change the parameter name from Parent Device ID to ParentDevAddress which is more consistent with its data type of MAC address(48bit)Please change the parameter Channel to ChannelIndex and its data type to integer.Please change the Beacon Period data type to duration.Please change DeviceID to DeviceAddress when referring to a parameter of data type address(48bit). It is a more accurate description of the data type. The association between DeviceID and MAC address is not intuitively obvious.Please remove the last sentence of the ChannelScanDuration description.Please change the definition from its current text to: PNID "indicates to the MLME to either search for a specific PNID when the PNID is set to 0x0000 through 0xFFFE, or search for all PNIDs when the PNID is set to 0xFFFF."Please remove the OpenScan parameter from Table 3.Please remove the OpenScan parameter from the paramter list for the MLME-SCAN-REQUEST primitive.Please add the MLME-NEW-PNC primitive to Table 1 just after the MLME-PROBE-PNC primitive.Please add the MLME-PNC-HANDOVER primitive to Table 1 just before the MLME-PROBE-PNC primitive in Table 1.Please move the MLME-DEV-INFO primitive from its current location to just after the MLME-CHANGE-CHANNEL table location.Please add the MLME-REMOTE-SCAN primitive to Table 1 just after the MLME-CREATE-REPEATER primitive and just before the MLME-CHANGE-CHANNEL primitive in Table 1.Please add MLME-CREATE-REPEATER primitive to Table 1 just after the MLME-CHANNEL-STATUS primitive in Table 1.Please add MLME-Tx-POWER-CHANGE primitive to Table 1 just before the MLME-CHANNEL-STATUS primitive in Table 1.Please move the MLME-START primitive from its current position in Table 1 to the second position in Table 1 just after MLME-RESET.Please move the MLME-RESET primitive from its current position in Table 1 to the first position in Table 1.Move MLME-PowerMgt primitive at the beginning of Table 1 to the position just before the MLME-CREATE-STREAM primitive.CCA threshold values should be defined depending on TX power levels similar to 802.11b standard.The 5 GHz and UWB should not be mentioned in this table to avoid confusion.Change "sub-layer needs to ... of an MPDU." to be "sub-layer wants to change the PHY power management state." in 6.9.4.19.1, line 22 Change "will be to start the ... state machine." to be "will be to enter the indicated power management level." in 6.9.4.19.2, line 26Replace the sentence "AntSelect is an ... shall be used." with "The primitive parameter is defined in Table 55"Change "the period indicated ... has expired." to be "the chnannel has been quiet for an aCCADetectTime period."Change "contains both the PLCP and PHY" to be "contains the PHY"Delete the sentence "The DATA parameters is an octet value." in 6.9.4.1 and 6.9.4.2.Delete sub-clause 6.9.3.1 in its entirety and wipe it from our minds.Delete "The primitives associated ... sub-layer to sub-layer interactions." and connect the following paragraph to the previous one.Delete the words "and multicast" from three places, line 4 in 6.7.1.1, line 15 in 6.7.1.2 and line 33 in 6.7.3. Also, change "reorderable multicast service" to be "reorderable broadcast service"Change the two entries to be: Type Valid range Enumeration SUCCESS, TIMEOUT-*T &5@CIBRA]@ @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 ONM*L5K@JKITH_jsEzBA@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@LXOugH6LVALc oI  , N  H #  ȭq{U1 (%H` % %`Change the sentence fragment above to this: In the case where this MLME-PROBE-PNC primitives have been used by a device as part of the PNC-HANDOVER process, the initiating DME shall initiate an MLME-NEW-PNC.request. In the case where the MChange the sentence fragment above to this: In the case Change the sentence fragment above to this: In the case where this MLME-PROBE-PNC primitives have been used by a device as part of the PNC-HANDOVER process, the initiating DME shall initiate an MLME-NEW-PNC.request. In the case where the MLME-PROBE-PNC primitives have been used by a device to simply request DEV information held by the PNC, the initiating DME may initiate another MLME-PROBE-PNC.request for a differenct remote device, or it may initiate an MLME-DEV-INFO.request.Please change to: RESPONSE_TIMEOUTPlease change to: RequestorDEVAID.Please provide the appropriate xref.Please change the QueriedDEVIDSet parameter name to QueriedDEVAID.Please change the DEVInfoSet parameter name to: PNCInfoSet.Please change the RequestorDEVAddress to RequestorDEVAID, its data type to Integer, its valid range to 0-255 and its description to:"The DEVAID of the DEV that is requesting the information from the PNC.Please change the QueriedDEVIDSet parameter name to QueriedDEVAID; its data type to Integer, and its valid range to 0-255. Also change the description to: " The QueriedDEVAID when set to an integer value less than 255 will return information from the PNC regarding a CTA for a specific DEV. It the QueriedDEVAID is set to a broadcast AID value of 255 then the PNC will return CTA information for all the associated DEVs.Please change from RequestorDEVAddress to RequestorDEVAID.Please remove the indicated sentence fragment.Please remove the ChannelIndex parameter from this primitive.Please change RemoteDevAddress to RemoteDevAID and its data type to an integer with a range of 0-255Please insert clauses 6.3.1 through 6.3.1.3.2 of 01/410r1 into the D09 just before the Channel Status subclause and just after the Power Management subclauses.Please move the indicated Power Management clauses to the location just after the Terminate Stream Message Sequence Chart. This new location makes more sense from a functional perspective.Please insert clauses 6.xxxx from 01/410r1 into the space just before clause 6.3.13 Stream creation.Please add the PiconetDescriptionSet parameter to the MLME-START.confirm primitive.Please move the indicated clauses. It makes more sense to have these clauses located near the MLME-SCAN clauses.Please move the requested clauses to the indicated location.Please add this paragraph to this clause: "The PNC MLME, upon receiving this primitive, behaves the same as the DEV MLME with the exception that it transmits a beacon containing a PICONET-SHUTDOWN information element. "Please remove the last sentence from this clause since the MLME-RESET.confirm is unneeded.Please provide missing message sequence chart.Please change the indicated clause title to: MLME-NEW-ASSOCIATED-DEV.indication.Please change both instances of AssocDEVAddress to DeviceAID.Please provide the appropriate xref.Please change the indicated phrase to: "...and a beacon containing the NewAssociatedDEV Information element..."Please change AssocDEVAddress to DeviceAIDPlease provide appropriate xref to ASSOCIATE-RESPONSE command frame type in Clause 7.Please add the required xref to the appropriate subclause in clause 7.0The AssociationTimeOutPeriod data type should be changed from Integer to Duration.'LVAL.2< { . j a T !`2)]Ncu$   Committee report x4IsNull([Clause]) OR [Clause] Not In ("00","01","02",?"04","06","03","04","05","06","07","08","09","10","11","A","B","46"The MLME-NEW-PNC.request, indication and confirm primThe MLME-NEW-PNC.request, indication and confirm primitives are missing from the MLME-SAP interface clause.ACK_TIMEOUT ReasonCode is incorrect.Missing xref to DEVICE-INFORMATION-RESPONSE previously known as PROBE-RESPONSE.RequestorDEVAddress parameter name is incorrect.REquestorDEVAddress parameter is incorrectDestinationDEVAddress parameter name is incorrectMissing xref to DEVICE-INFORMATION-REQUEST command frame previously known as PROBE-REQUEST.Missing xref to the DEVICE-INFORMATION-REQUEST command frame previously known as PROBE-REQUEST.Current Location of clauses 6.3.19-6.3.19.5 is incorrect.The ReasonCode data type field is incorrect and its valid range is incorrect.RequestorDEVAddress parameter name is incorrect, the data type is incorrect, valid range is incorrect, and the description is incorrect.DestinationDEVAddress parameter name is incorrect, data type is incorrect, valid range is incorrect, and description are incorrect.This sentence fragment " ...and may initiate another MLME-PROBE-PNC.request...ACK_TIMEOUT ReasonCode is incorrect.Missing xref to PROBE-PNC-RESPONSE command.DEVInfoSet parameter name is incorrect.Missing xref to PROBE-PNC-RESPONSE command frame clause previously known as DEVICE-INFORMATION-RESPONSE clause in clause 7.0DevInfoSet parameter name is incorrectRequestorDEVAddress parameter name is incorrectRequestorDEVAddress parameter name is incorrect.QueriedDEVIDSet parameter name is incorrect.Missing xref to the PROBE-PNC-REQUEST command previously known as the DEVICE-INFO-REQUEST command.The QueriedDEVIDSet parameter name is incorrectDEVInfoSet is an incorrect parameter name.The RequestorDEVAddress parameter name, its data type, valid range and description are incorrrect.QueriedDEVIDSet is an incorrect parameter name, data type and valid range.The RequestorDEVAddress in an incorrect parameter name.the sentence fragment ...on the indicated ChannelIndex... is not needed.Missing xref to the CHANNEL-STATUS-REQUEST command frame described in Clause 7.DestinationDEVAddress is the wrong parameter name.ChannelIndex is an unnecessary parameter. Since the current Channel-Status command frame is only valid in the current piconet channel.DestinationDEVAddress is an incorrect parameter name.The RemoteDEVAddress is an inconsistent parameter name. Also its data type is incorrect.The MLME-Tx-POWER-CHANGE.request, indication, and confirm primitives are missing from Clause 6.3 MLME-SAP interface.The Power Management clauses 6.3.1, 6.3.1.1, 6.3.1.1.1, 6.3.1.1.2, 6.3.1.2, 6.3.1.2.1, 6.3.1.2.2 should be moved to the space just after clause 6.3.15.4 Terminate Stream Message Sequence Chart.The MLME-CHANNEL-TIME.request, indication,response and confirm are missing.The PiconetDescriptionSet parameter is missing from the MLME-START.confirm primitive.Clauses 6.3.12, 6.3.12.1, 6.3.12.1.1, 6.3.12.1.2, 6.3.12.2, 6.3.12.2.1, 6.3.12.2.2 should be moved to where clause 6.3.2 is located so that the MLME-START primitives follow the MLME-RESET primitive at the beginning of MLME-SAP interface section.Clauses 6.3.11, 6.3.11.1, 6.3.11.1.1, 6.3.11.1.2 and Table 18 should be where clause 6.3.1 is located on page 23.Clauses 6.3.11.2, 6.3.11.2.1, 6.3.11.2.2, and Table 19 are unnecessary.Text describing the effect this primitive has upon the PNC MLME is missing.The last sentence of this clause is unnecessary.Missing Association message sequence chart.The title of clause 6.3.4.5 MLME-ASOCIATION-RESPONSE.indication is incorrect.AssocDEVAddress is an incorrect parameter name.xref to ASSOCIATION-RESPONSE command frame subclause of clause 7 is missing.!  $ , 6 CMWFCEOWC=EO@ @ @ @ @@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.26230T9@P<@OXOugH6b@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1.26221TJ@P0@OXOugH6a@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@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1628T@P?@OXOugH6@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@OXOugH6Z@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.134845TRM@ Pf@OXOugH6Y@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>@ OXOugH6V@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.24642TJ@PPlease remove.XOugH6U@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.1.24640TM@P@ OXOugH6T@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.11.1.24640T2@P\@ OXOugH6p ON" ,L4 J&IH shoulBoc|e A%`D&9CIf ((> = True@R( nC ]@"X"))n@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.5688E!DEV-2 label in MSC is incorrectChange to PNC.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.4.2681TRP@!P@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.4.16748T&@ P$@OXOugH6~@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.4.16747E-@P"Please provide appropriate xref.XOugH6}@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.46738T)@PPlease change to: PNCInfoSetXOugH6|@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.3.26729E~@P"Please provide appropriate xref.XOugH6{@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.36718T(@PPlease change to: PNCInfoSet.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.36717T1@P"Please change to RequestorDEVAIDXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.26648T2@P$@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18/26647T.@P"Please change to: QueriedDEVAID.XOugH6w@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.1.26635Ed@P&@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.18.16624T1@PD@OXOugH6u@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 306611T,@P=@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 30668Td@P@OXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 30665TL@P@OXOugH6LVAL jFy V 2  V o \ >g+}Z%atNj "  "Please insert clauses 6.3.1.24 through 6.3.26.2 of the MLME-PNC-HANDOVER.request, indicPlease insert clauses 6.3.1.24 through 6.3.26.2 of the MLME-PNC-HANDOVER.request, indication, response and confirm clauses into the space just before current D09 clause 6.3.18.Please insert Clause 6.3.1.19 from doc 01/410r1Please change the data type from octet to Duration with valid range of 0 to 255 ms?Please change from octet to integer.Please insert clauses 6.3.1.13 through 6.3.1.16.2 from 01/410r1 into the space just after the MLME-CHANNEL-STATUS and MLME-CREATE-REPEATER message sequence chart clause.Please insert the MLME-CHANNEL-STATUS and MLME-CREATE-REPEATER message sequence chart clause and diagram just after the last clause of the MLME-CREATE-REPEATER.confirm primitive. Text and diagram are in clause 6.3.1.12 of doc 01/410r1Please insert clauses 6.3.1.8 through 6.3.1.11.2 just after the 6.3.16.5 MLME-CHANNEL-STATUS message sequence chart.Please provide the appropriate timer symbol for the message sequence chart.Please change from ACK_TIMEOUT to RESPONSE_TIMEOUT.Please change to RequestorDEVAID.... functions on behalf of the general system ...Include the 'PublicKeyProofe' as a conditional parameter in the MLME-AUTHENTICATE.response and MLME-AUTHENTICATE.confirm.Include the 'PublicKeyChallenge' as an optional parameter in the MLME-AUTHENTICATE.request and MLME-AUTHENTICATE.indication.Change parm name to: DeviceAID; data type to: Integer; valid range to:0-255; and description to: "Specifies the DEVAID of the peer device with which to perform the disassociation process."Please change the indicated text to: " The non-initiating DME, when it receives the MLME-NEW-ASSOCIATED-DEV.indication primitive, is provided with the DeviceAddress and DeviceAID of a successfully associated DEV."Please change the indicated fragment to: "... a beacon containing a NEW-ASSOCIATED-DEV information element."Please change the parm name to DeviceAID; the data type to Integer; and the description to: " The association ID of a new device that has become associated with the piconet."Please change the DeviceID parm name to DeviceAddress. Also change the Description to: The deviceAddress of the DEV that has been associated.Please remove the indicated fields from the table.Please change the indicated primitive to: MLME-NEW-ASSOCIATED-DEV.indication.Please remove the ReasonCode parameter from the MLME-NEW-ASSOCIATED-DEV.indication parameter list.Please change the indicated sentence fragment to: " ...reception of a beacon containing a NEW-ASSOCIATED-DEV information element.Please insert the DeviceAddress parameter into the MLME-ASSOCIATE.request parameter list just before the CapabilityInformation parameter.Please remove the indicated sentence fragment.Please insert Clause 6.3.1.34 MLME-DEV-INFO, MLME-PNC-HANDOVER, MLME-PROBE-PNC, and MLME-NEW-PNC message sequence chart from doc 01/410r1Please insert clauses 6.3.1.31 through 6.3.1.33.2 from doc 01/410r1 into the space just after Clause 6.3.18.5 MLME-PROBE-PNC message sequence chart.Please change to RESPONSE-TIMEOUT.Please change to RequestorDEVAID.Please move the MLME-DEV-INFO clauses and MSC to just after the MLME-CHANNEL-STATUS, MLME-REMOTE-SCAN, and MLME-CHANGE-CHANNEL message sequence chart and just before the MLME-PNC-HANDOVER.request clause.Please change ReasonCode data type field to: Enumeration, and the valid range to: "SUCCESS, RESPONSE_TIMEOUTPlease change parameter name to: RequestorDEVAID, the data type to: Integer, the valid range to: 0-255, and the description to: " The DEVAID of the DEV requesting the information."Please change parameter name to RemoteDEVAID, data type to Integer, Valid range to 0-255, and description to: "The RemoteDEVAID of the DEV from ..." ON *  HGFA@ @ @ @ @ @ck to see if any records exist$. h$(   & SELECT * FROM Main WHERE ."" AND  [Clause] I@3@3@  3@3@Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.12946TA@U@ SRZugH6f@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.1.2308TU@U0@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.47121T:@U@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.47126Tm@-P@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.4.17037T&@,P$@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.4.17036EQ@+P"Please provide appropriate xref.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.3708T2@*P"Please change to RequestorDEVAIDXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.26934T,@)P#@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.16911T3@(PPlease change to RemoteDEVAIDXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.2.16942E]@'P"Please provide appropriate xref.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.19.1.26922Ea@&P!Please add the appropriate xrefXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.196830E;@%P@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 316850TO@$Pn@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 316842T@#P@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 316839T@"P@SXOugH6LVAL0q0F [  p 7 | N  C  p  5uEO5i8___J5S= @RDQϹϹϹ 0ϹϹ!"1N OEOEcGEOE!So3s rst.Clos e dbMsgBox ("All summary reports complete") End SubPrivate snCreTildeFiles_Click*(h'4 6-delimited f&]missing definitive artmissing definitive article, add as shown belowThis clause states there is security information in the frame body.There are only 3 addresses available for neighor piconets.Lack reference to information on encryption keyWhy two Frag fields ... start and end?poor sentence structure ... suggest rewrite as shown in sentence fragment belowNo time out for these two primitivesNo MLME-STREAM-CONNECT primitive in Table 1Why does the device care about the last device to authenticate and deauthenticate? Where does it get this information?Why does the PROBE-PNC command only get information about authenticated DEVs? Can this only be done in a secure piconet? What is the purpose of this command?When does DE-AUTHENTICATE actually get used? What purpose does it serve? I don't think it really makes sense to have a command that says that your key has been compromised if that is what this is for.An MLME-DISTRIBUTE-KEY.response should be created so that the DEV that decided to distribute the key can know whether the key was successfully decrypted or not.EncryptedKeyObjectLength should have values greater than or equal to 0, not 1. It may be that this field is intentionally left blank.DistributeKeyFailureTimeout should be removed.Missing xref to Peer Discovery sub clause in Clause 8.The clause title "Peer attribute discovery" is incorrectThe MLME-PNC-HANDOVER.request is missing from the MLME-SAP interface clause.The MLME-CHANNEL-STATUS-, MLME-REMOTE-SCAN, and MLME-CHANGE-CHANNEL message sequence chart is missing from the MLME-SAP interface clause.The ChannelChangeTimeout data type is incorrect.The NewChannelIndex data type is incorrect.The MLME-REMOTE-SCAN.request, indication, response and confirm primitives are missing from the MLME-SAP interface clause.The MLME-CHANNEL-STATUS and MLME-CREATE-REPEATER message sequence chart is missing.The MLME-CREATE-REPEATER.request, indication, response, and confirm primitives are missing from the MLME-SAP interface clause.The MLME-CHANNEL-STATUS message sequence chart is missing the ChnlStatusRspTO timer.the ReasonCode message "ACK_TIMEOUT" at the end of the indicated sentence is incorrect.The RemoteDEVAddress is incorrect.Missing xref to the CHANNEL-STATUS-RESPONSE command clause in Clause 7The DestinationDEVAddress parameter at the end of the indicated sentence is incorrect.The RequestorDEVAddress is an incorrect parameter namemissing definitive article, modify as shown belowmissing definite article, add as shown belowInclude the possibility for authentication of the PNC.Include the possibility for authentication of the PNC.DeviceID parm name, data type, valid range, and description are incorrectThe text describing the Effect of receipt is incorrectThe sentence fragment "... a broadcast ASSOCIATION-RESPONSE command with a ReasonCode of SUCCESS."The AssocDEVAddress parm name, data type, and description are incorrect.The DeviceID parameter name, and description are incorrect.The ReasonCode parameter, data type, valid range, and Description are unnecessary given the new name of this primitive.The MLME-ASSOCIATION-RESPONSE.indication primitive no longer needed.The ReasonCode parameter name is unneeded.The sentence fragment : "...reception of a broadcast ASSOCIATION-RESPONSE command." is incorrect.The AssocDEVAddress parameter name is incorrect.The DeviceID parameter name is incorrectThe DeviceID parameter name is incorrect.The DeviceAddress parameter is missing from the parameter list.the sentence fragment "...specified by the the DeviceID parameter." is unnecessary.The MLME-PNC-HANDOVER message sequence chart is missing.WNMLK HGGFE"DKt[M@L5 cj'par6gpmt$,8aE#4sQe3 Se`9bi@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.11916E3@Urelationship among the man-XOseH6h@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.11915E.@U3@SXOseH6S@3@@3@  Y Kleindl, Guenterguenter.kleindl@siemens.at43 51707 35738Siemens066.3.63637TR8@U{@SXO}ttdH6R@3@@3@  Y Kleindl, Guenterguenter.kleindl@siemens.at43 51707 35738Siemens066.3.63536TR8@U~@SXO}ttdH6+@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 103315TK@U@SXOugH6(@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.5.23235T9@ U@SXOugH6'@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.5.13230Td@ Un@SXOugH6%@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 93223TJ@ U@SXOugH6$@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 93220T=@ U@SXOugH6#@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 93218Ty@ U4@ SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.5326TRF@UO@ SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.5328T,@Ud@ SXOugH6&@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.5323TRc@U@ SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.33042T2@UPlease change to DeviceAID.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.33041T*@U!Please change to DeviceAddress.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.4.23018T+@U!Please change to DeviceAddress.XOugH6 OM K  ,    (  8 &+H p x " ( j r@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.186552E8@!U"Please provide appropriate xref.XOugH6q@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.186550E:@ U3@XXOugH6p@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.186549TN@U@SXOugH6o@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.186549T@U1@SXOugH6n@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.06Table 296445T2@UU@SXOugH6m@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.176442T-@U&@SXOugH6l@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.176431TR{@U@SXOugH6k@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.176431TU@U@SXOugH6j@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.56431TR@Uw@SXOugH6i@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.56415TV@UM@SXOugH6h@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.4.16349TY@U5@SXOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.46335T$@U Please change to RemoteDEVAID.XOugH6f@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.3.26325EH@U"Please provide appropriate xref.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.1.1.26222TX@U Please change to RemoteDEVAID.XOugH6@3@@3@  Y Heberling, Allenaheberling@xtremespectrum.com703-269-3022571-220-1211XtremeSpectrum, Inc.066.3.16.3637T8@U#@SXOugH6gLVAL$%^ X ;  V )j aD]hKP " X ` p xxp0AoXp  fPicture14 6B@Bko( 6B@I see no need for the application specific information information elI see no need for the application specific information information element. Unless someone can justify it, please delete the entire clause.... DEV to know if any GTSs, where it is either the SA or DA, have changed ...element ID = 0x0B use full name "MACPIBMaxAssignedCTAs" use full name "MACPIBMaxProcessedCTAs"... offset from the start of the superframe and hence the start of the transmission of the beacon frame ...Security subcommittee needs to resolve this TBD in this line.... and shall be set to 1 if they are in EPS mode.This paragraph is confusing. Power management subcomittee needs to clarify and provide addditional references to other clauses.The current TX power is the DEVs estimate ...Clause 10 does not make reference to IEEE P1363 and it appears that it should. How does P1363 enter into the security algorithms?... DEVs shall expect a beacon from the PNC in ...Suggest the 5 bits of table 94 represent the 5 LSBs and that the upper 3 bits of the octet be zeros.Provide reference to the DEK details. If the subclause is missing in clause 10 then provide the details.Bill Shvodian of XtremeSpectrum to provide text on a recommended solution.... 2-octet boundary within the frame body.frames that are allowed to include ...The frame format of the data frame ...PNC and the DEV (during a MTS) or during ...The length field of the frame shall count the number of octets, including the stuffed octet.Provide reference to the specific clause 10 subclause that describes this security information.Please increase the addresses available from 3 to 6 ... 4 on each side, 1 above and 1 below.Please provide reference for the following sentence fragment "currently assigned data encryption key" where in clause 10 is this data contained? If not present it needs to be added.Couldn't the fragmentation process be signified by setting a single bit? 0=not fragmentating and 1=fragmentatingPlease add the definition of a "natural number" to clause 3... fields are numbered from 0 to k, ....... sequence number information, and optional traffic category ...Question for MAC subcommittee ... resolve if this is the correct name. Is there another more common name used in the document?Change text: The PSAVE bit shall be set to 1 if the DEV is capable of using EPS mode as part of power management.change Figure 25 in clause 7.4.6 to allow up to 16 supported rates.This may be as simple as adding a note in this subclause that the destination DEV may reject the operation if not setup in a stream managment command sequence. The offended DEV would then send a switch command to the PNC to let the PNC and other network DEVs know its correct state. The intent is to not burden the PNC with filtering unless this is a simple fit into existing PNC filtering operations (e.g., CTRs are not processed unless they match to an existing stream setup). If this is simple then the PNC should reject the operation.make the change to figure 61 - Momentary EPS CTA command format. Add the stream index and destination DEV address. The text is correct already.Add - The PNC shall provide the switch to ACTIVE operation even if it is unable to return the full CTR allocation.Add time out parameters to the MLME-CREATE-STREME & MLME-MODIFY-STREME primitivesRemove AuthenticateFailDevice (why is it called "Fail" anyway?) and DeauthenticateDevice. Comment via Ari Singer.Recommend explaining the purpose of this command (if it isn't in there already). Comment via Ari Singer.Recommend removing these commands. Comment via Ari Singer.Change the clause title to: "Retrieving PNC Info" L   .GKF@^D~%.N N!bGFind record in Main with CommentID that matches current record in Rough-@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@@3@  Y Siwiak, Kazimierzkai.siwiak@timedomain.com954-755-6828256-990-9062Time Domain066.6.9791023TR@Z!Remove the PHYPIB_Range object.XOrdI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.5.3 Table 3976319Ty@'Ut@XXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.18.1661939T@&Uk@XXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.10T@%U=@XXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.9T@$UComment via Ari Singer.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.9 Table 16423147T@#UComment via Ari Singer.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.8 Table 1540E0@"UComment via Ari Singer.XOugI6LVAL 7l@QoCU  @ @ @ @ @ Reason code definitions ... there aReason code definitions ... there are no reason codes in clause 7.5.7.2Run on sentence ... add white space.In lines 26 and 27, remove the hyphensreplace the word PAN with personalityincomplete specification on EncryptedKeyObjectgrammatical ... add a colon as shown belowadd commas to sentence as shown belowModifications to Figure 32 as shown belowappears there is a typo as shown belowThis paragraph references a field that contains "the least significant two octets of a beacon number".In figure 30 do two things: 1. name the last column as "slot location field" 2. Add SFNext to acronym list in clause 4Add a definite article as shown belowFigure 25 indicates that the supported data rates is represented by up to 8 octets, one octet for each data rate. Reference is provided in the tesxt to clause 11.7. In clause 11.7, Table 94 is a 5 bit mapping to a given data rate. How does the 5 bits map to the octet?Reference is made to the "current data encyrption key (DEK)"Field resolution is 8 uS ... this may be inefficient for 100+ Mbps data rates. Changing this to something less (like 1 uS) impacts a number of issues in the standard.reference is made to a "traffic category". This term is used just once in the whole docuement (i.e. used only in this sentence).There is no mention here of what the setting should be when MTS is used rather than CAP. Also, the xref to 8.4.2 would indicate that more would be found there, and 8.4.2 is fairly short in description.A left over in that EPS is called sleep state. Also, this bit should be to indicate possiblility of operating in EPS mode. Other information carried elsewhereThe task group has indicated before that 8 supported rates will be sufficient for PHYs other than the current one described in clause 11. However, it would seem that the limit be somewhat higher. 16 seems too high but perhaps that would be a good ceiling.There is a possible authentication question with EPS and switch to ACTIVE mode or EPS mode commands. The use of these commands requires agreements between peers (after association and authentication). There may be an opportunity for an unauthorized DEV to control another DEVs power use. Sending DEVs are normally responsible for the mode shift to have the destination DEV react to changes in data transmission flow that the destination is not directly aware of. I am not clear on the security mechanisms to understand if this is an issue or not.Momentary should have had two additional fields in the d0.9 that didn't make it into the draft. The destination DEV address and stream index are required.A DEV requesting switch to ACTIVE CTA expects the PNC to grant previously requested QoS upon receipt of the switch command. This is a "should" and not a "shall" as is appropriate. However, the expectation is that the PNC shall do the switch in the very next superframe beacon even if the requested bandwidth is not immediately available. This lets the EPS DEV make the switch to ACTIVE in anticipation of bandwidth becoming available in the next few superframes as the PNC is able to juggle requirments. The comment is located here because of adjacent text that might lead the implementer to error.6.6.9 PHY PIB ranging support: The PHYPIB_Range object calls for two octets, range in meters in the first octet, and fractional part of a meter in cm for the second octet. At the moment nothing supports this in clause 11. It is too early to understand if this is the correct format to carry us into the future. Since we don't know how "location awareness," which might include ranging and other attributes, will be addressed in 3a. It is better to remove the object now rather than be faced with a work-around in the future. ,  # 6 I \QI]SI8'; @@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.210243T@ZL@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 19102TExplicitly provide element ID0x01XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 18102TExplicitly provide element ID0x00XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.410145E Modify sentence as shown below-@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.410143E modify sentence as shown below(@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.3.410042E0@/U(@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.3.31004Eadd words as shown below ....@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.39819E"rewrite sentence as shown below.^@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.2.79734TRE@.Ua@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.2.39635TR<@-U^@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.2.1.9969TR1@,U@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.2.1.5 & 7.2.1.69536T(@+Us@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.1.19336TRItem to add to clause 3=@ XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.1.19328E!remove the comma as shown below+@ XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.19314EQ@*UD@ XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.19316TR@Z@ XXOseH6;&  vg@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 29106TProvide explicit element ID0x0AXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 28106TProvide explicit element ID0x09XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.81063E modify sentence as shown below/@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 27105TProvide explicit element ID0x07XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.710533TR!Reference is made to IEEE P1363@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.710530TAddition to clause 4Add OID to the acronyms listXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 26105TProvide explicit element ID0x06XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.61053E'@ Z!... are conveyed to the MAC ...XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 25105TProvide element ID0x05XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 21103TProvide explicit element ID0x02XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.510453E modify sentence as shown below4@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 24104TProvide explicit element ID0x04XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 23104TProvide explicit element ID0x03XOseH6@3@3@  3@3@Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 25105TR@ Zf@XRZseH6f@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.21031TR>@ Zk@XXOseH6(M$L -J@ 1*&)8Dj D9wWE epOUz<&̢O[SJ.R@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 37112T!Provide explicit commands typesr@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.111144E,@Z3@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.511133Eadd the word "the"-@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Table 65110T!Why do we need 16 bit commands?]@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 36109TExplicit element ID0x0EXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.14109TDeletion of clause 7.4.14@#XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 34109TProvide explicit ID0x0DXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 33108TProvide explicit element ID0x0CXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.1210840E'@ZP@"XXOseH6j@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 32108TR+@Z`@!XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.1010742Egrammatical as shown belowm@ XXOseH6g@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.1010735TRNeed to resolve TDB?@XXOseH6d@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.1010733TR(@Z4@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.4.1010728Th@ Z@XXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 30106Ty@ ZAs shown aboveXOseH6WLVAL/vC= t  X  @ >  { A  q3UHWjqX8In line 41 it is required that the PNC be the security manager, yet no place in the tIn line 41 it is required that the PNC be the security manager, yet no place in the text is this function detailed. The security subcommittee needs to provide the details.In table 15, the parameter DistributeKeyFailureTimeout is defined but not used by any primitives. Security committee needs to clarify.security subcommittee needs to define and explain usage of the following items from table 15 KEK DEK DIK SEED... of the results, via the reason code, of a previously ...Table 14 does not define the ReasonCode. The security subcommittee needs to provide the reason codes.What and where are the public key authentication challenge described?Refer to MAC/security subcommittee to supply number of octets.Security subcommittee needs to provide text reference to this authentication sequence.Security subgroup needs to provide reference in text where this procedure is described.second line of description for AuthenticationInfoLength parameter ... change the word "device" to "defined"The description for the parameter DEVPublicKeyObject refers to a cipher suite. The cipher suite details are not present in draft 9 text. Needs to be added.Delete the following parameters from table 13. They are used in table 14 and are redundant. PublicKeyChallengeLength PublicKeyChallenge PublicKeyProofLength PublicKeyProofThe following are listed as parameters for a primitive ... but no primitives use these. Where are they used? SecurityManagerPublicKeyObjectLength SecurityManagerPublicKeyObjectRefer to MAC/security subcommittee to supply number of octets.Should be MLME-DISASSOCIATE.confirm primitive parametersShould be MLME-DISASSOCIATE.indication primitive parametersAdd in the MSC ... MAC subcommitteeAdd a comma after DeviceID Remove the comma after AssocDEVAddressShould this be one octet? Is there an upper limit?remove comma after parameter "SyncFailureTimeout"range is listed as 100-65535 ... should this be 0-65535?Put a comma after the parameter "OpenScan"have management subgroup provide proper reference to reason codesfrom errors rather than waiting for the next... management mode. Defined in ...add commas after the following parameters: RequestType EPSSet EPSStatusPIB-related --> PIB related user-entity --> user entity... as a personality information ...Security subcommittee to provide detailed text in clause 10 about the EncryptedKeyObjectSecurity subcommittee to provide technical detail in clause 10 about the KeyPurposeSecurity subcommittee needs to provide technical detail in clause 10 on the PublicKeyProofprovide explicit command type = 0x001Fsecurity subcommittee to provide detail of PublicKeyChallengeIn clause 10, please provide details of the AuthenticationInfo - security subcommittee.In clause 10, provide technical details for the DEVPublicKeyObject1. explicit command type = 0x001CAdd text to clause 10 the details of the Piconet Security Manager - security subcommittee.Channel is too severe to serve the DEV... association address; hence, this command ...... if the frames from the PNC ...... capability field is the same ...replace "hand over" with "handover"At the end of a PNC handover, the new PNC of the piconet uses the PNC selection frame with this action type to signal the end of the PNC handover.0x000B "Alternate PNC announcement command" 0x000C "Alternate PNC pullout command" 0x000D "PNC handover command"... PNC selection commands: the alternate PNC ...... 2-octet boundary within the frame body.MAC subcommittee needs to justify 16 bit commands ... prefer to replace with 8 bit commandsE {sq@ @3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 42116TRDEVPublicKeyObjectD@ ^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 42116TDo folllowing to Figure 42#@ ^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.311549TRPiconet Security Manager\@ ^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.311549T acronym PSMadd PSM to clause 4XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.2.311537E grammatical(@ ^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 41115Tprovide explicit command type0x0014XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.2.211442E grammatical2@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 40114Texplicit command type0x0013XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.2.111418Egrammatical, add definitivelarly, if the PNC did not ...XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.2.111416Eadd definitive article$@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.2.111414Eadd definitive article&@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 39114TProvide explicit command type0x0012XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.1.411328E grammatical%@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 38113Tprovide explicit command type0x000EXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.1.31131Egrammatical correction@^XOseH6 s|~kqfJ,>@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07figure 47118TR0@ZZ@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.3.611821TRincorrect figure numbershould be figure 47XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.3.51181TRincorrect figure numbershould be figure 46XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 47118Texplicit command type0x0021XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 46118TR KeyPurposeU@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 46118Tprovide explicit command type0x0020XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 45117TRPublicKeyProof\@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 45117T see below(@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.3.411732TRin correct figure numberfigure should be 45XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.3.31175TRin correct figure numbershould be figure 44XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum077.5.3.211629TRin correct figure numberchange figure 50 to figure 43XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 44117TRtechnical detail?@^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 44117Tprovide explicit command type0x001EXOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 43116TRAuthenticationInfoY@ ^XOseH6@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum07Figure 43116Tprovide explicit command type0x001DXOseH6&O. 3 , =JC VH[QFCE8@^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&@^XOseH6LVAL-p*q =  2 N   S"28go1yd>Z  $ .$ $$ 0$ (% 00%(x),"This element has no meaning if the EPS DEV is not in"This element has no meaning if the EPS DEV is not in power management mode." In WHAT power mangement mode.What does this mean "The operating superframe length adjusts this value."Why is EPSTime in ms and not superframes?Is EPS Sync only allowed in the PNC?Poor sentence - to implement the power-saving strategy of an implementation.I don't see RequestType in 7.5.7.1. Is this the same as EPS Action request command entries?Need to specify which commands are associated with the generation of the MLME-POWERMANAGEMENT .request."The MAC CPS provides stream-oriented service to the SSCS." What about non-stream?How does MAC-CPS fit in to Figure 2? Is the MAC-SAP in figure 2 the MAC-CPS SAP or the SSCS SAP?"may" does not belong in "Both MAC and PHY may conceptually"The second entry in this table is "privacy". Are we going to call this privacy or security.In line 6 and also in line 10, the parameter STATE is incorrect. The parameter name is actually STATUS. This is needed to be consistent with table 54.Add text to explain why the TX and RX MAC headers are passed in the TX and RX vectors.Add figures to illustrate the vectors TXVECTOR and RXVECTORClause 11 does not address the managed objects of table 50Need to add a statement to clause 6.6.9 that the PHY of clause 11 does not support ranging.Clause 11 does not list the managed objectManaged Object in Table 47 is misspeltThe Managed objects are PHY dependent but are not defined in clause 11.The text in line 4 claims there is a mapping between the data rate vector and the actual data rate that is PHY dependent. Where is this mapping in clause 11. How does this map to the PHYPIB_DataRateVector and the PHYPIB_CurrentDataRate?Modify first line of clause 6.4 as shown below.Opening sentence is missing the opening clause. Modify as shown below.ACK_TIMEOUT is referenced several times in clause 6.3.XX, but I can't find the definition of ACK_TIMEOUT.How is EPS impacted by a stream modification. Does the "SlotStartTimeSet" parameter shown in table 25 also apply to SFNext?Add a figure to show the ChannelTimeList vector as referenced in table 26Modify the sentence of line 33 as shown below.Provide a figure that shows the vector representation of "ServiceFlowList" and "ARQList" as reflected in tables 23 and 24 respectively.Reference to "directed distribute key request command" and a "broadcast distributed key request command". These seem like two different commands.Spelling error in 6.3.9.1, 6.3.9.2, and 6.3.9.3In type column of table 16, how many octets are required?in line 4, reference is made to an "encrypted format".Problem with ReasonCode parameterIn line 22, reference is made to a null key and the appropriate result code.Line 19 indicates that "the PNC shall encrypt and return the designated key"PNC requirement to be the security managerAdd following to clause 4 acronymsNeed octets associated with Types integer and byte string in table 15Lacking definition and explainationDescription of public key authentication challengeUnder the Type column ... should the integer type be defined as to the number of octets? Also, what is the nature of the byte string ... shouldn't the number of bytes be specified?The text at the end of line 32 describes an authentication sequence.The text says ... "The DME may use the MLME-CHALLENGE.request command to obtain additional security information from the associated DEV.Under the Type column ... should the integer type be defined as to the number of octets? Also, what is the nature of the byte string ... shouldn't the number of bytes be specified?Type for AssociationTimeOutPeriodValid range for the ChannelScanDuration7NM K  )I<9G6F?DEGBVe (D@3@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.8.2.24119TRN@ bW@dXOseH6@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@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum066.3.6.2.23632TRF@bX@'^XOseH6~@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@@3@  Y Roberts, Richardrroberts@xtremespectrum.com703-269-3043301-613-5016XtremeSpectrum06Table 13358TRReference to cipher suite@$^XOseH6@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@"^XOseH6LVAL/5z' " , 5 g 0 d . ^5etd117X^ @ Remove all reference to "privacy and private" and replace with "security Remove all reference to "privacy and private" and replace with "security or secure". (The other way around is ok to, but we need to be consistent.)... to the local PHY to enter the ...Replace STATE with STATUS in two places as discussed above.Text that can be added to clause 6.9.4 "The MAC headers TxMacHead and RxMacHead are passed in the TX vector and RX vector respectively to facilitate calculation of the HCS as illustrated in Figure 107."In table 55, in the value column for parameter Length, it is stated the max number of octets is determined by PHYPIB_LengthMax. Should this be PHYPIB_MPDU_LengthMax. If not, then where is PHYPIB_LengthMax defined?add a comma as shown below ... characteristics of, and methods of, transmitting and ...remove comma after the parameter ReceptionStatusremove comma after the parameter Data... to understand the parameters which need ... (remove the comma after the word parameters)change the sentence at the end of line 41 and the beginning of line 42 as: ... identified logical connection; however, it does not ...The PHY committee needs to add reference to the values used for PHYPIB_NumPSLevels and PHYPIB_PSLevelReturn.Add the following statement at the end of line 12 (Note: the IEEE802.15.3 PHY of clause 11 does not currently support ranging).Spelling should be PHYPIB_CCAThresholdDefine PHYPIB_MPDULengthMax in clause 11 ... refer to PHY subcommitteeCorrect spelling ... it should be PHYPIB_MPDULengthMaxThe PHY subcommittee needs to add the following items to clause 11 PHYPIB_TxMaxPower PHYPIB_TxPowerStepSize PHYPIB_CurrentPowerLevel... on the regulatory domains for the 2.4 GHz PHY is given in 11.1.... PHY PIB values that are unique to ...... association group, Table 40, contains ...... authentication group, Table 39, ...The PIB characteristics group, Table 38, ...This optional primitive shall be a request by the PLME to ...Remove the comma after the parameter "DataRate".... shall be a request by the PLME to reset ...... PLME-SET primitives operating on the PHY PIB ...Figure 10 illustrates the sequence of ...add a comma at the end of the parameter StreamindexLine 52, replace "with out" with "without"MAC subcommittee to provide a clause reference to ACK_TIMEOUT.... CHANNEL-TIME-GRANT command (7.5.10.2) with a ....... command (7.5.10.1), which it will send ...Refer this question to the power management subcommittee.... command (ActionType=request) (7.5.10.3), which is ...Add these two figures to clause 6.3.13CAP Mode is not defined in clause 7.4.2. MAC subcommittee needs to clarify the reference here.Add a figure to show the MACParameterSet vectoradd commas to the following parameters PiconetType ChannelList ChannelScanDuration MACParameterSetSecurity commmittee needs to clarify what primitives handle these two commands. Are they differentiated by parameters? If so, which parameters?Table 16 does not provide the reason code ... security committee needs to define the reason code.Question for security committee ... in line 45 the command is given as "MLME.DISTRIBUTE-KEY.response". Should this be "MLME.DISTRIBUTE-KEY.indication"?The commands are misspelt ... replace "distibute" with "distribute"security committee to provide octetsSecurity subcommittee to provide the details as to what is this encrypted format.change the last word in line 43 from "message" to "response".Referenced table 15 does not provide the reason code definitions. Security committee needs to provide these reason codes.Security committee to provide definition of a null key and what are the associated (and appropriate) result codes.Security committee needs to provide the encryption algorithm. What is the algorithm?k N$ 7 KKXJOINH]GceE^DrCcit P/3 Sub AddialCrit=! 3=4V+ `F #b V   Just sort by page and lineStream 0 is used regardless of destination address. Need to specify Stream 0 is used regardless of destination address. Need to specify a destination DEV to start a channel time request for non stream data.Eliminate tripartate negotiation.If we are going to have a figure showing bipartate MSC from DEV to PNC, we should show bipartate negotiaon from PNC to DEV.Move the PNC to in between Dev A and Dev B since A and B only talk to the PNC. This will simplify the drawing.Slot Start Time set is defined in Table 25 - reference neededSource and destination addresses should be initiator and target for consistency with stream management command.Remove Peak Rate, Min rate and Max Burst Size from from service flow and stream mangement. The PNC cannot guarantee any of these. It can only guarantee channel time. If RSVP or other reservation protocol is used, the will negotiate at a higher layer, not at the MAC.Add direction parameter to MLME-CREATE-STREAM.requestDirection bit needed for the MLME-CREATE-STREAM parameters.2 octet SequenceNumber is inconsistent with the 1 octet stream requeest identifier in the stream request command. Also, we have a Sequence Number field in the MAC header - 2 words, but still too close.Source Address and destination address should be the 48 bit MAC address, not the 8 bid AD-AD. This is for 2 reasons: 1) to be consistent with the other MLMEs. Wo does the address translation, the DME or the MLME? We need to be consistent. Second, the stream request command should contain MAC addresses, not AD-ADs to safeguard against discrepancies.MLME-START.confirm should have the channel number that the piconet was started in.Putting clause 6 before clause 7 and 8 will confuse new readers.Break MLME-POWERMGT command up into separate MLMEs, like security/authentication did.Reason Code needs to be added to table 16Reason code needs to be defined in Tsable 15.Need to define KEK, DEK, DIK, and SEED for us non-cryptographers, besides just the acronyms.Table 15 needs maximum values in the range columnReason Code needs to be defined in Table 14Table 14 needs maximum valuse in the range so that implementers can size their design.All the parameters in this table need maximum values in the valid range column so that implementers can choose the proper number of bits to use in their implements.Need a MLME-SyncLost.indicate to tell the DME that the DEV can no longer hear the Beacon.No indication of power level if no beacon found.Move Start MLME to be adjacent to Scan, Synchronization and Associate.There is no way to indicate that a frame with the PNID was found, but not a beaconThe scan is done once PNID is found, but there is a small but non-zero probablity that the same PNID may be heard on separate chanelsWhere does the DEV get the PNID from to scan for? Are PNIDs random at startup, or does PNC always use same PNID? What if different PNC?Why is there no MLME-POWERMGT.response. The PNC should send a response in response to an indication.If you have peer wakeup, you need to have a peer addressMLME-POWERMGT.indication only has one parameter, but it really needs to have almost all of the parameters as the request. The PNC will receive an indication as the result of recieving a power managemnt command.This request better do more than "sets the DEV power management parameters." Doesn't it also determine which power management commands are sent to the PNC or the other DEV?I see no mention of ReasonCode in 7.5.7.2Why is PowerManagementPriority here and not in the capability field where it belongs.It is not clear why the PNC needs to know that the device is RPS vs. PM_OFF.There is no request type for Peer Wakeup, wakeup, DEV to PNC PS Information CommandNNM$ 1KBJV OH^GmF}ECBA@B( @3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table143737TRX@i6@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table13355TR@i@@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.329TR[@ iAdd a MLME-SyncLost.indicateXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table52743TR2@ iH@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.12.24814EH@ iH@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table52733TRT@ i@ hXOugI6 @3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.2.1.22645T@ iS@ hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table312621TR@i4@ hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.125TRg@iAdd MLME-POWERMGT.responseXOugI6~@3@3@  Y3@Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table224TR:@i)@ hXZugI6F@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.12510TR@i/@ hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.1.1.22448TR@iv@hXOugI6{@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table22433E+@i7@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table22428TRW@il@hXOugI6u@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table22423TRN@i@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table22437TRU@iAdd Peer wakeup request typeXOugI6 ON.  I&42'3C: @3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.13.5538E?@iAdd reference to Table 25XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.13.15015Eq@iA@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 23493540TR@i^@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.13.15022TR7@iAdd direction parameterXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 2249TR=@iAdd direction bit.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 224917TR@i@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 22495TRe@i4@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.12.24821TRT@i;@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06EB@iMove Clause 6 after Clause 8XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.123TRW@iM@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.9.3448TR+@iAdd reason code to table 16XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table164232TRNeed max values columnNeed Max Values Column.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.8.34135TR/@i Define reason code in Table 15XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table154013E^@i;@hXOugI6v@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table1540725TR3@i%@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.7.43932TR-@i%@hXOugI6+= Q K \ n cqC @ @ @ @ @8PX@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table3976E(@ m$@'hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table 387534TDont really need 65535 CTAs)@&hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table37757T'@ m!Get rid of MACPIBCFPMaxDurationXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.19.4TRW@m<@%hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.19.1.16922Eg@me@$hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.19E`@mE@#hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.1865E@mM@"hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.18.1.26635T(@m`@!hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Figure 86410E=@mChange to DEV-1 and DEV-2XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.16.1627TD@m@ hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table286133E=@mp@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table286132EF@mAdd the vertical lineXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.1455TR@"i;@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.13.654TR#@!iD@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.13.6E}@ i9@hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Figure3546Eq@iP@hXOugI6LVAL$}91 j  Z x  k  : k W ' (' 8'H'  NP' ' ')')')')')()() ()0(Where is the PHY preamble aWhere is the PHY preamble and PHY header in this figure?"Each field is defined in 7.2.1." - Shouldn't this be 7.2?Figure desired to outline the MAC frame formatAuthenticateFailureTimeout is not sent with the Challenge command. It is used within the MAC to limit the amount of time the MAC will wait for an Authentication response.there is a TBD for the security fieldI don't understand the use of the grant status field format. Isn't the SFNext a short form of the next beacon that an EPS DEV will wake on? It would seem that what we want in Figure 74 is the start time of the adjacent GTS as the text in line 31 states.in the second field, the range of bits should be b16 to b19we should be talking about microseconds and not milliseconds. If we stay consistent, the resolution should be 8 us and range is 0 to 524280the text mentions EPS slots. Clearer wording would be wake superframes.EncryptedKeyObjectLength should have values greater than or equal to 0, not 1. It may be that this field is intentionally left blank.PublicKeyChallengeLength and PublicKeyProofLength should have values greater than or equal to 0, not 1. It may be that these fields are intentionally left blank.DEVPublicKeyObjectLength, AuthenticationInfoLength, SecurityManagerPublicKeyLength, PublicKeyChallengeLength and PublicKeyProofLength should all have values greater than or equal to 0, not 1. It may be that these fields are intentionally left blank.MLME-DISTRIBUTE-KEY does not have a response. Without a response, the PNC (or security manager) will not know if the associated DEV actually received the key or not.Having EPS be both a mode and an EPSSatus is very confusing.Need to specify that the preamble starts when this command is received.Remove PHYPIB_DataRates from the Rx vector. It should be Rxtate, not PIB.Data Rate and Power Level should not be PIB parameters. Rename the value.Need a MAC_DATA.confirm to indicate status in the event of a failure.Remove reference to strictly ordered service class. This is an 802.11 holdover."All DEVs shall support the asynchronous data service." This is a LAN mentality, not WPAN. Devs can may be simplified by eliminating asynchronous data service.The sentence "Broadcast and Multicast transport are part of the asynchronous data service provided by the MAC." provides no information. Unicast is part of the data service, too.The sentence "Broadcast and Multicast transport are part of the asynchronous data service provided by the MAC." provides no information. Unicast is part of the data service, too.Current Power Level doesn't belong in the PIB. It is sent with each packet at the PHY SAPCurfrent Rx and TX antenna are passed at the PHY SAP and should not be PIB values becasue they are set on a packet by packet basis.PHYPIB_CurrentDataRate shouldn't be a PHY PIB. It is passed at the PHY SAP on a packet by packet basis.Why are table 39 and 40 in Clause 6.6?What is MACPIBCFPMaxDuration used forMLME-DEV-INFO.confirm needs a DestinationDeviceID so the DME knows who is responding.This MLME should send the probe command, not the device informmation request (which goes to the PNC).MLME-DEV-INFO MLMEs don't send Device Information commands, they send probe rewquest commands.Subclause is called Peer attribute discover, but the MLMEs are MLME-PROBE-PNC, and they cause device information request commands to be sent, not probe commands.What is the PROBE-PNC-REQUEST command?Why is the PNC on of the MLMEs in a channel status request?The requesting DEV choose the window size, not the responding DEV.RemoteDEVAddress does not match the parameters in the MLMEsTable is missing a vertical line between Valid Range and Description7*N9 5 / @ Q Pcq~CueF  @3@@3@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.8 Table 1540725T@mComment via Ari Singer.XOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum066.3.7 Table 14373554T@mComment via Ari Singer.XOugI6@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@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table5584TRL@m8@oXOugI6@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@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table447752TR\@ m.@*hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table43TR@ m3@)hXOugI6@3@@3@  Y Shvodian, Williambshvodian@xtremespectrum.com703-269-3047301-523-1538XtremeSpectrum06Table4277TRj@ m,@(hXOugI6qLVAL\> z  N  < l 7i=N{@3@@3@ < @ @< @ p< @x <Delete "As a typical implementation, " and change "division is preset" to be "division shall bDelete "As a typical implementation, " and change "division is preset" to be "division shall be preset" in line 1 and change "remainder is preset" to be "remainder shall be preset" in line 5Change "The FCS is calculated" to be "The FCS shall be calculated" on line 43 and "The FCS field is transmitted" to be "The FCS field shall be transmitted"Delete ", including the security information if any"Change "... and priority." to be "... and priority and shall be formatted as illustrated in Fig. 13."Change "is set to zero, and ignored upon reception," to be "shall be set to zero on transmission and shall be ignored upon reception "Delete the itemization point "- the address value of 0xFD is reserved for multicast frames." and change the neighbor PNC addresses to be one more (i.e. 0xFB, 0xFC and 0xFD).Change "is set to" to be "shall be set to" in 2 places in each 7.2.1.5, 7.2.1.6, 7.2.1.7, 7.2.1.10 and one place in 7.2.1.9Change "supports will discard" to "supports may discard"Change "consists of the ... and repeater" with "is used to identify the type of frame and how it is to be handled."Add the figure once it has been generated and reviewed. Figure should have multiple fields with LSb and MSb indicated for each of the fields, an indication of the order in which they are sent over the air and an example of a simple command or information element with specific values.Change "left-most bit is transmitted" to "left-most bit shall be transmitted" in line 26, change "a single octet are sent to" to be "longer than a single octet shall be sent to" in line 31, change "convention and is transmitted" to "convention and shall be transmitted" in line 34 and change "in decimal are coded" to be "in decimal shall be coded" in lin 37.In a) change "frame control, address " to "frame control, network identification, source address, destination adress " In d) change "(FCS) which" to "(FCS), if the frame body is non-zero length, which"This function has been taken over by the key field in the piconet synchronization parameters information element. Delete the sentence and the key bit (b2) from Figure 31. Add the bit to the reserved bits.Add a sentence that says that the MAC header fields are set as appropriate unless otherwise specified.Security is applicable on a piconet basis, not a stream-by-stream basis. Delete the sentence and the associated bits in figure 76 (b4-b6). Reassign the bits as reserved and move the other bits foward so that the reserved bits are contiguous.Looks like agreement is needed here to determine the requirement for this place holder. Finish discussion and complete requirement.Unclear about actual meaning. State clearly.Need a clear understanding of what is optional and what is mandatory.Clarify meaning or method of information determination.Need understanding of this feature. Not explained well.Remove the last field (AuthenticationFailureTimeout) from Figure 44 on page 117. Remove lines 20-22 on page 117.Remove Security field from the control information field and shift other fields left increasing size of reserved field by 2 bits.Remove "The security field is a 2 bit field defined in 7.2.1.2.change from SFNext to adjacent GTS start time in Figure 74 and then use adjacent GTS start time instead of SFNext on line 31.change "EPS slots" to "wake superframes"Add a response message. Comment via Ari Singer.Rename either the EPSStatus values to EPS_Active and EPS_InactiveSpecify that the Preamble starts when PHY-TX-START.request is received.Change PHYPIB_DataRates to RxRatechange data rate and power lavel from being PIB valuse ( G 7 F HHFGeF'XCwth argconditionsTransfer records to output](]H]h@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments073.19829T@q9@ oXO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0739814Ei@qState frame types up front.XO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments072.4976EX@qDelete the paragraph.XO}xtaaSC6u@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments072.1.109615T@q:@ oXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments07Figure 119413T:@#mXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments072944E=@"mXO~zxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments0719312E0@!mXO~zxtaaSC6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola077.5.3.31172021TR@ mr@ oXOvhZB6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola07Figure 7613315TR!Security field is not required.@oXOvhZB6@3@@3@  Y Barr, JohnJohn.Barr@Motorola.com847-576-8706847-651-6822Motorola077.5.10.313339TRSecurity field not required.A@oXOvhZB64@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.313340T'@mdefine the TBDXOvhZA63@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain07figure 7513246Eneed right ) add ) for max frames (Del-ACK)XOvhZA62@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.213231T@m@oXOvhZA61@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain07figure 7413222E=@mchange b9 to b19XOvhZA60@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.113132T@mchange to 8 us and 0 - 524280XOvhZA6/@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.113127EI@m*@oXOvhZA6.@3@@3@  Y Bain, Jayjay.bain@timedomain.com256 428 6415256 527 4778Time Domain077.5.10.113112E extra wordsremove "PNC it the"XOvhZA6-LVAL] H  - y = X  s >m^ 0wC*\Rffff*063b979f7f48<@DHLPThe following sentence does not end in a period: The challenge responsThe following sentence does not end in a period: The challenge response command frame structure shall be formatted as illustrated in Figure 50The following sentence does not end in a period: The authentication response command frame structure shall be formatted as illustrated in Figure 50The following sentence does not end in a period: The authentication request command frame structure shall be formatted as illustrated in Figure 42The following sentence does not end in a period: command shall be formatted as illustrated in Figure 41The following sentence does not end in a period: The EPS info field shall be formatted as illustrated in Figure 35The following sentence does not end in a period: and not all bits in the bitmapThe following sentence does not end in a period:  0b11: both authentication and data encryption are requiredThe following sentence does not end in a period: The format of the piconet synchronization parameter element shall be formatted as illustrated in Figure 19The following sentence has an error in punctuation: PNC and the DEV or during the CAP,.The following sentences do not end in a period:  The address value 0 is reserved for the PNC, for coordinator related transmissions and receptions  The address value of all-ones (0xFF) is reserved for broadcast frames ...  The address value of 0xFD is reserved for multicast frames  The address values of 0xFA, 0xFB or 0xFC are reserved for neighbor piconetsDiagram hard to read. How does this diagram relate to the previous paragraph? Where are the terms aCSFrameRepeat and aCSFrameBroadcast in this diagram? I would like to see their timing relationships."in Koctets/s" (with u meaning micro here) - is this to mean that units are 1024 octets/sec increments?"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?What does "ReTX" mean? It also appears on page 135, line 18."in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?"... same response rules a the device ..." - should be "as"."in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?What is a "EPS set"? Where is it defined? For that matter, where is RPS defined? Is it a parameter set by the design and communicated through the PIB?Where is SFNext defined? Did not find reference to it in the following text. Is it a specific value? Or based on system design and is specified in the PIB?This paragraph is a repeat of one on page 107, line 23.This paragraph is very vague and does not say anything. Given the TBD, I assume this is a place holder for data to come."The bit shall be set to 0 if they are in ACTIVE mode and shall be set to 0 if they are in EPS mode." Which one should be set to 1?"in Kus" (with u meaning micro here) - is this to mean that units are 1024 usecs?Title should read: "Frame and stream control field settings ...""... DEVs may ignore any elements in the beacon that are not listed in Table 60." - then what are the optional elements that can be ignored. Please state them explicitly."The information elements in the beacon frame may appear in any order in the beacon ..." - How do you know what you are looking at if they can appear in any order?"... four defined frame types." - What are they? Please list them, otherwise the sentence is useless.This information is already stated on page 96, line 52. This paragraph is not needed."repeater service" - why is this service needed? Wouldn't the devices just talk in a peer to peer mode? What benefit is there to having a go between (the PNC)?F4l K  L h *Ocx   $ @3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.3.31004EY@qDelete the comma.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.2.3963035Ex@qAdd the period.XOyhWD6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments07Figure 78139T@q See above.XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments075.10.31358Ei@qClarify meaningXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments075.10.3135618ES@qClarify meaning.XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments07Figure 7713436T?@q"Need a definition to understand.XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments075.8.312831ES@qClarify meaningXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments075.8.31286E?@qXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments075.4.412129ES@ qState meaning clearlyXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments075.111233ES@ qState meaning clearlyXO}xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments074.1310918T@ qXO~xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments07Figure 3010646T@ qNeed more information.XOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments074.1010738E9@ qConsolidate information.XO~xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments074.1010735TR{@q@oXO~xtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments074.1010734T@qPick a value of 1.XO~xtaaSC6@3@3@ 3@3@ DuVal, Marym-duval@ti.com972-575-2330Texas Instruments074.510454TS@q/@ o%@AC}xtaaSC66@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments07Table 61 and 6299EB@qXOxtaaSC6@3@@3@  Y DuVal, Marym-duval@ti.com972-575-2330Texas Instruments073.19830T@qG@ oXO}xtaaSC6*> R e z +=M  @3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.10.31333234E)@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.10.113119En@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.4.212044Ef@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.4.212034E@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.4.11202Eq@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.811929E@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.71191E@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.611821E@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.51181E@tAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.411732E@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.211629E@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.3.11165E@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.5.2.311522Ei@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.4.1310921Et@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.4.1210844EQ@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.4.210327Er@qAdd the period.XOyhWD6@3@@3@  Y Gifford, Iangiffordi@ieee.org+1 978 251 3451+1 978 815 8182Self077.4.210230E@qAdd the period.XOyhWD6*LVAL oI D R ! S  kW\|s"axins !B records. Do you wish to delete all records in the dispatch table? cmdClearMainTable_Click$$ R B@B B@BxNo action takenA@$|kOtherwise,Informal language used tInformal language used to define characteristics.Multicast capabilities are not defined for this protocol.Change the label "Slot Start time or SFNext" to be "slot location" since that is how it is referenced in the definitions.Delete reserved field, elements can be defined as odd lengths, the protocol automatically pads them to even numbers of octets.The description of piconet maximum transmit power is incorrect.All occurances of Kus were to be changed to milliseconds, but some were missed.The PNC Des-mode description is incorrect.The piconet synchronization parameters element does not include the guard time. The TG had agreed to use a constant guard time broadcast by the PNC to account for differences in the clocks of the DEVs participating in the piconet. This addition was held off on the chance that the CTAs would have both start and stop times. Since they do not, we need to add guard time back in.The CAP duration is not the time offset from the start of the beacon to the start of the CFP.The transmit power change is a command, not an information element and has already been moved to the appropriate location in the draft.Not all commands are allowed to be chained together. Some shall be sent individuallyThe channel time allocations are required in every beacon. Also, the DEV GTS status is not indicated as an allowed element in the beacon.Informal language. Also, shouldn't all implementations initiallize the the HCS remainder to the same number?Security information is no longer included as separate data, delete this reference.No multicast capabilities have been defined for this standard. There is no way to create or join multicast groups. Delete all references to multicast addresses (this is one of the first).Informal language used, change to shallThe description of the frame control field repeats what is in the figure and therefore is redundant and evil.Need a figure to show how the bit ordering is used in the figures that follow.Requirements are not strong enough for bit ordering.Enumeration items are inclomplete in their description.TBD in "The key change bit is reserved for possible security implementation with TBD meaning"Some of the commands have the settings specified for the MAC header fields, while other commands do not.The security field is a 3-bit field that The following sentences do not end in a period:  A value of  4 indicates that the frame is sent by one of the DEVs to the PNC to reject or disconnect the stream  A value of  5 indicates that the frame is sent by the PNC to one of the DEVs to reject or disconnect the streamThe following sentence does not end in a period: The use of this field for EPS CTRs is described in 8.13.3.4The following sentence does not end in a period: The information request field is defined in 7.5.4.1The following sentence does not end in a period: The probe response command frame structure shall be formatted as illustrated in Figure 51The following sentence does not end in a period: frame structure shall be formatted as illustrated in Figure 50The following sentence does not end in a period: The deauthenticate request command frame structure shall be formatted as illustrated in Figure 50The following sentence does not end in a period: The distribute key request command frame structure shall be formatted as illustrated in Figure 50The following sentence does not end in a period: The request key response command frame structure shall be formatted as illustrated in Figure 50The following sentence does not end in a period: The request key request command frame structure shall be formatted as illustrated in Figure 50)OWM 8 E pG 9femŠa̐endC(.Set s tatus+des: X --> Ds fD++tS%GEndC PriPvate S-6EW 9@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.410126T@t@vXO}yn`RC68@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.3.31006TW@t@vXO}yn`RC67@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.3.19844T@t@vXO}yn`RC66@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.8981To@t@oXO}yn`RC65@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.89743TInformal language@oXO}yn`RC64@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.79733TU@t6@oXO}yn`RC63@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.49650T!Add requirement for formatting.g@oXO}yn`RC62@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.49640TInformal language@oXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.39634T@t@oXO}yn`RC60@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.1.59537T)@t}@oXO}yn`RC6/@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.19444T "will" is not formal language.:@oXO}yn`RC6.@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.2.19425To@tu@oXO}yn`RC6-@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.1.19327TP@t@oXO}yn`RC6,@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.1.19326T6@ ti@oXO}yn`RC6+@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.19314T9@ t@oXO}yn`RC6v@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.1010736T_@ t@oXO}yn`RC6'@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.511017Tj@ th@oXO}yn`RC6w@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.313339T0@ t@oXO}yn`RC6LVAL,2 + N ( # ;(Cq,KAddNewD@![Comm"ID]`RderName$Email3C_PhonǔChange "The structure ... as illustrated in Figure 61." to "The momeChange "The structure ... as illustrated in Figure 61." to "The momentary EPS CTA command shall be formatted as illustrated in Figure 61."Delete the sentence "When an EPS set is confirmed ... for that EPS set."Delete the sentence "When and EPS set is .. for that EPS set." since this requirement is already in clause 8.Move the sentence "If the DEV ... next becomes available" to clause 8.11 or delete the sentence.Delete the field from figure 51 and the sentence referencng it on line 44.Change as indicated in the figure.Delete the two sentences "In all cases ...maager in a piconet."Change reason code 5 from "DEV wishes to disassociate" to "Neighbor piconet not allowed"Change "the DEV and expect the DEV to associate again." to be "the DEV."Delete the entire sub-clause 7.5.1.2 and all other references to the command in the draft, especially in Table 65, renumbering as necessary.Delete the reserved field and move the 3 1 byte fields to the end of the command so that the other fields end on 2 byte boundaries.Change the sentences "The DA is set to the ... upon reception." to read "The DA is set to the broadcast address." (i.e. change first sentence and delete the two that follow).Change "set to request ... zero." to be "set to No-ACK." Change "frame control field of the MAC header" to be "frame control field and the stream control field of the MAC header"Change "No command ... within a piconet." to be "Other than the association request, association response, alternate PNC selection command and new PNC announcement command, no command frame shall be transmitted to or by and unassociated DEV within a piconet."Delete " using a standard a GTS or CFP message exchange" since the negotiation is outside of the scope of the standard.Change "A value of 1 is set" to be "The value shall be set to 1" and change "A value of 0 is set" to be "The value shall be set to 0"Change "this field is set to 2." to be "this field shall be set to 2." and change "the field is set to 1" to be "the field shall be set to 1" and change "the field will be set to 0" to be "the field shall be set to 0"Delete the sentence "The destination address may include group or multicast destinations."Delete the field "Reserved" and change the length of the element to 1Change "... communicate the transmit power control (TPC) capabilities of a DEV." to be "... communicate the maximum power allowed by the PNC as described in 8.14.1"Change all occurances (there are 2 on 104 and more follow in clause 7) of Kus to millisecondsChange the definition to match what is now in clause 8, the new definitions chould read: The PNC Des-Mode is the designated mode of the DEV. This bit shall be set to 1 if it is desired that the DEV be the PNC of the piconet and the AC bit is set to 1. Otherwise this bit shall be set to 0.Add a 2 octet element to the end of the piconet synchronization parameters element that indicates the piconet guard time in microseconds, 0-65536 us. Also need to add to clause 8 the use of the guard time with the CFP.Change "The same value is used as the time offset" to "The same value is used to calculate the time offset"Update tables 63 and 65 by moving the transmit power change command from 63 to 65. Renumber the information element ID's and command ID's as necessary.Insert the following sentence after "... as shown in Figure 15." The following commands shall be sent in a command frame that contains only the command: alternate PNC announcement, new PNC announcement, association request, disassociation request.Change "As needed" to "In every beacon" for channel time allocation in table 60. Also, add a row at the bottom of Table 60 that is "DEV GTS Status" "7.4.12" "Indicates if a DEV's GTSs have changed" "As needed",X   HIs%SAll summary reports completeA@$o<@BCreate Tilde-delimited file containing NEW records for each editor]]K@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.1.41139T@x@yXO}yn`RC6J@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.1.311248T@x@yXO}yn`RC6I@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.1.211242T@x@vXO}yn`RC6H@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.111211TM@x@vXO}yn`RC6G@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.11122TB@x@vXO}yn`RC6F@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.111147T@x@vXO}yn`RC6E@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.511018Tz@x@ vXO}yn`RC6D@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.141109TH@xy@ vXO}yn`RC6C@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.1310936TA@x@ vXO}yn`RC6B@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.1310933T3@t@ vXO}yn`RC6@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.1110830T;@t\@ vXO}yn`RC6@@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.1010646T{@tChange as indicated.XO}yn`RC6?@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.910615T@tG@vXO}yn`RC6>@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.910610TA@t@vXO}yn`RC6=@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.510445EQ@t_@vXO}yn`RC6<@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.310417T,@t&@vXO}yn`RC6;@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.210329T~@t@vXO}yn`RC6:@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.4.210249T_@tm@vXO}yn`RC6QLVALwE + [ A kg'Dg @ @ @at a type selec?has been m If (IsNull(Me!["firma List])) Then  MsgBox ("PleAC from@eUVnF "#ExitQ En0d If@)See if user wants Pto c@rdispatch  CallbCADTxcAm('Op@6rAgain, there is a redundant and evil inclusion of Again, there is a redundant and evil inclusion of functional description in the frame formats clause.There is a redundant and therefore evil definition of functional requirements in this frame format section.The AD-AD should be used instead of the destination device ID.The last sentence defines functional requirements that are already defined in clause 8. The redundant definition is therefore evil and shall be exorcised.The repeater services request command has incorrect fields and fields that are not needed. The PNC will repeat all communications between the two DEVs and it knows all of the CTRB's that have been allowed between the two. Also, the device ID should not be used, but rather the AD-AD. Since this is used for the repeater service grant command, adopting this change will require changes in 7.5.6.2 as well.The information request field is not used in the probe response command.Clarify what is the purpose of the information elements field.The stream control field should be defined once for all commands in 7.5 (as indicated in an earlier comment). Hence it should be deleted from this location. Redundancy is evil. This sentence also occurs in 7.5.4.2 and should be deleted from there as well.Change the order of the fields so that the variable length field is last, in particular put the DistributeKeyFailureTimeout as the first field following the length field.Move the AuthenticateFailueTimeout to be the first field so that the variable length field is last in the command format.Move the Authentication timeout field to be prior to AuthenticationInfo in the command format so that the variable field is last.The definition of the role of the PNC as PSM redundant and is therefore an abomination to the technical editor.Reason code 0 and 2 are not well defined. There is no way for the PNC to know 2, unless it monitors all GTSs. Compliant DEVs are not allowed to overshoot their allocated channel time.The condition code "DEV wishes to disassociate" is not possible in the PNC's response. However, we do not have a code for when the PNC does not wish to allow neighbor piconets.The ACK policy for the association response command is defined in three places and therefore is evil.A DEV that fails ATP will not neccessarily re-associate and so the PNC should not expect that to happen. The PNC does not need to expect anything.Need to add a definition of the stream control field (0x00). Best place to put this is 7.5 since all commands are non-stream data. Also need to delete the redundant and therefore evil definition of what goes in the PNID field (that is defined much earlier, 7.2.2)The PNC handover command has unnecessary items in the frame format and adds a redundant and therefore evil definition of how the frame will be used.The new PNC announcement command doesn't need to use all of the bytes in the other PNC commands. It really only needs the new beacon timeout parameter.The alternate PNC pullout command was deleted from the functional description a couple of revisions ago. This command is no longer used.Reserved fields are no longer used in the commands or information elements.Directed frames are no longer used in the PNC selection process.There are no more directed frames in the PNC selection process, so the ACK policy shall always be No-ACK. In addition, the stream control field should be set to 0 in these commands.The restriction on transmitting command frames is too restrictive. It would not allow an unassociated DEV to associate.The restrictions on negotiating theuse of the ASIE is too restrictive.Informal language to describe the characterisitcs of EPS statusLVAL i F0@pX(Delete the sentences "Additional destination... for self sleep only." Delete the field "Destination DEV addresses" froDelete the sentences "Additional destination... for self sleep only." Delete the field "Destination DEV addresses" from the figure and change the command length to 0. Delete the sentence "The destination DEV ... to EPS mode." on line 30.Change the sentences "The structure of the ... DEV. The use is to instruct" to be "The switch to EPS CTA mode command shall be formatted as illustrated in Figure 60. The command is used to instruct"Change the sentence "The command ... requirements change" to be "The command may be repeated while a DEV is associated in the piconet if the DEV requirements change."Change "destination device ID" to be "destination AD-AD" in the table and in one place in each of the two paragraphs that follow the figure. Change the field size to 2 octets and the command size to 3 octets.Change the destination device ID field to be the destination AD-AD field and change the definition from "The destination device ID is the 48 bit IEEE 802 address" to be "The destination AD-AD is the addresss". Change the length of this field to 2 octets. Delete all of the CTRBs from the figure. Delete the sentences "The format of channel time ... destination device ID." Change the command length to be 2 In 7.5.6.2, change "The destination device ID is that" to be "The destination AD-AD is that" Delete the sentences "The format of channel time ... repeater service."Change "information elements, described in 7.4." to be "information elements, 7.4, about the source DEV that is being provided to the destination DEV."Delete the sentence "The stream control ... ignored upon reception." which ends on the top of the next page. Also delete the sentence "The stream control .. ignored upon reception." on page 120, line 33, sub-clause 7.5.4.2.Change reason code 0 to read "ATP has expired, DEV needs to re-associate". Delete reason code 2 and re-number the reason codes. As an alternative, perhaps allow reason code 2 to be "PNC unable to service DEV" as a catch-all for any problems the PNC might encounter.Delete the sentence "Hence this command shall not be ACKed" Also delete "If there is a match, ... future communications." on line 48 since this is already defined in clause 8.Add the sentence to 7.5 at the end of the first paragraph, "All commands shall have the stream index field in the MAC header set to 0x00 and shall be ignored upon reception." Delete the sentence "The PNID values ... to associate."Change "The PNC shall use this command" to be "The PNC uses this command" and delete the following fields from both the frame format and the definitions that follow: superframe duration - every DEV associated with the piconet is required to know this anyway. PNC device ID - every DEV knows this from the beacon. AC device ID - The DEV already knows its own device ID Change the command length from 18 to 4 octets.Add to the text, following "as PNC in the piconet." on line 52 with "This command is also used at the end of a PNC handover by the new PNC of the piconet to signal the end of PNC handover. The new PNC announcement command shall be formatted as illustrated in Figure 38." Octets: 2 2 2 Type Length (=2) New beacon timeout Figure 38 -- New PNC announcement frame body (delete old paragraph beginning "At the end of ... hand over." and change the paragraph "The CSTimeout ... in the channel." to read as follows:) "The new beacon timeout field indicates the time offset in milliseconds before which the first beacon shall be sent by the winning AC, in the case of PNC selection, or by the new PNC, in the case of PNC handover."*T~  < R|&PzNull([m.sLpt])h|se!XQ aq4'$e!#SubjPF"#DoOC, by K`OM]@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.312449T`@{Delete the two sentences.XO}yn`RC6\@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.212437Tg@xJ@vXO}yn`RC6[@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.7.112341Tm@xo@vXO}yn`RC6Z@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.6.312312T@@x@yXO}yn`RC6Y@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.6.21231T@xb@vXO}yn`RC6X@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.6.112233T@xC@yXO}yn`RC6W@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.4.212044TJ@xL@vXO}yn`RC6V@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.4.212026T@@x@yXO}yn`RC6U@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.4.111949T@x@yXO}yn`RC6T@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.3.71196T@xChange as indicated.XO}yn`RC6S@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.3.311710T{@x$@vXO}yn`RC6R@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.3.211635T@xChange as indicated.XO}yn`RC6Q@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.311548Tq@xA@vXO}yn`RC6P@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.2.311537T@ x @yXO}yn`RC6O@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.2.211511T@ xZ@vXO}yn`RC6N@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.2.211442Tg@ x@yXO}yn`RC6M@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.2.111419T@ xJ@vXO}yn`RC6L@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.2.111343T @ x@yXO}yn`RC6 LVAL f m  C V gx<$F$2CWhy should PNC increment and publish DEK? if the key is changed the key-distribution scheme should make sure all the rWhy should PNC increment and publish DEK? if the key is changed the key-distribution scheme should make sure all the relavant DEVs in the pcionet are informed before the change. Moreover, keys must be per-link and not global per piconet.Is Transmit power change an info-element or command? it is listed in Table-63 on page 101, but described as a command in 7.5.5.1. In addition 8.14.2 references this as a command. the descrription in 7.5.5.1 describes this as an info-elementIs Transmit power change an info-element or command? it is listed in Table-63 on page 101, but described as a command in 7.5.5.1. In addition 8.14.2 references this as a commandIn clause 8, it is mandated that isoch data shall always be streams. But here it seems to say it is upto DEV.Reserve 0xF0 to 0xF9 for future use: We never know what else we'll need special addresses for.add a line describing the situation of SEC bit being set to '0'. otherwise it might be interpreted to be undefinde behavior.Retry bit: This bit is unnecessary since the MAC will have to check for seq-number in the rx-frame to detect duplicates anyway.use of word can mean different thing to different peopleSecurity is not defined on a stream by stream basis, but rather for the piconet as a whole.The action type requires a 3 bit field, not a 2 bit field.Informal language defines the CTA elements.Need to add clarification for the stream index setting when this command is used to allocate a non-stream CTA.The frame format description contains a redundant (evil) functional description.Informal language defines the field settings.This information response command is out of sync with the CTR and stream management commands. However, there is only one piece of information that is not explicitly given in a regular device information response command, and that is the neighbor PNC device ID. However, this is returned if a DEV requests the device information of a DEV with a neighbor PNC AD-AD. DEVs know when there is a neighbor piconet because of the AD-AD in the CTA blocks in the beacon. Likewise, a private GTS of an associated DEV indicates a child piconet. All of the information in this command is already taken care of with the device information response command. Thus this command is redundant and should be deleted.The command structure is not indicated in formal language. In addition, the introductory paragraph gives a redundant and therefore evil functional description in the frame formats clause that belongs the functional description clause.The first sentence is a redundant (aka evil) definition of the functional use of the device information request command that already is in clause 8. Also, the AD-AD should be used instead of the device IDThe command format is specified in formal language (missed in the last round of updates).A DEV should not be able to force other DEVs to sleep. Thus, the swich to EPS CTA should only apply to the DEV that is sending the command. The PNC already knows which CTAs to change from the information that was given when the CTAs were set up.The structure of the command is not stated in formal language (missed in the last update).The DEV to PNC PS command shall only be sent by associated devices and therefore shall not be sent during the association process. Heck, it can't be sent before the DEV is associated since it doesn't know its AD-AD yet.The sentences "Each DEV in the piconet using either EPS or RPS modes ... as is the priority information." adds no useful information about the frame format. The first sentence is incomplete and is a functional definition that is already in clause 8. (redundancy = evil) The fact that mode and priority are provided is obvious from the frame format.*T~ *JT }!L}CAAF@@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]H6j@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@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.10.213217T-@ {k@}XO}yn`RC6g@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`RC6e@3@@3@  Y Gilb, Jamesgilb@ieee.org858-538-3903858-213-6706Appairent077.5.9.112938T/@{@}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`RC66LVAL8M A  S w  QDajx@ Simplify "power management parameters" to have just the list of Device addresses of those DEVs that are currently asleeSimplify "power management parameters" to have just the list of Device addresses of those DEVs that are currently asleep. no other field is needed as the receiving DEVs know that if an address is present in this list, that device is asleep.Remove DEV GTS status element and all references to it from the draft.Add examples to clearly state the differences and relation between MaxAssignedCTAs and MaxProcessedCTAs.Remove line-46 and all references to "guard time" in the draft. However state in clause 8.4.3.2, add a paragraph describing the need for guard time and how PNC is expected to take that into account while allocating the channel time.1. move lines 27:31 on page 107 to be starting right after the current line number 44 on the same page. 2. change "as the SFNext" on line 26, page 107 to "as the SFNext, which is defined later in this clause" 3. reference the place of definition for EPSNext at its first use (at current line #30, page 107) 4. change the second occurrence of "set to 0" on line 34, page 107 to "set to 1" 5. remove line 36 6. Use of "slot location field" in lines 37:43 on page 107, without its definition. Actually its name is different in figure-30.remove "key change" field from figure-31 and mark b2 as reserved.Add a two-octet long Slot-duration field in figure-30 (and text in clause 7.4.10) with the resolution of this field being 8-microsec.Pick a new name for OID in this subclause and at all places referencing to it in the draftChange "supported rates" field in figure-25 from (1-8) octet(s) to 1-octet.Remove Key number from Figure-19 and all references to it from the draftChnage the description in 7.5.5.1 from info-element to commandMove Transmit power change from Table-63 to Table-65Remove "or isochronous" in line 8 and add "All isochronous data transfers shall be streams"Reserve 0xF0 to 0xF9 for future useWhen SEC bit is set 0 the frame body shall not be encrypted.Remove "retry bit" from frame control field and mark its current position as reserved for future usereplace "maintain word aligned frames" to "maintain two-octet alignment of the frames"Delete the security bits in the control information field and delete the sentence "The security field is a 3 bit field that .Change the text from "a 2-bit" to "a 3-bit" and re-number the bits accordingly in figure 76Change "element is defined" to be "element shall be formatted as illustrated in Figure 30 and is defined"After the paragraph that ends "This field is defined in 7.2.4." add the following: "For a new channel time request, the stream index shall be 0x00 for this command. All time requests that are for non-zero stream indices use the stream management command, 7.5.10.3, to initiate the request."Delete the sentence "The PNC shal create and retain this EPS CTR based on this request."Change "bits set to 1 indicate" to be "bits shall be set to 1 to indicate" in line 38 and change "bits set to 0 indicate" to be "bits shall be set to 0 to indicate" in line 39.Delete sub-clause 7.5.8.3 and all references to the child or neighbor information response command. If not, the sub-clause needs to be synchronized to use CTRBs like the DEV info response command. Also needs a "shall be formatted".Replace the sentences "Only the PNC ... all DEVs in the piconet." with "The device information response command shall be formatted as illustrated in Figure 63."Delete the sentence "Only a DEV shall send the device information request command." Change "device ID" to be "AD-AD" in the figure, change the field length to 2 and the command length to 2. Change "The queried device ID is the device ID" to be "The queried AD-AD is the address" on line 14.76O`M KKG pIG(UE8Ak@g$ 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]H6LVAL5  U Y 6 1 O+oL|U'  0H $` xRr  Alternate PNC pullout command unneeded givAlternate PNC pullout command unneeded given the change in Clause8.2.3 p139 line30-32.Alternate PNC announcement command unneeded.DeviceID parameter name is incorrect.MAx TX delay variation in figure-77 and MAximum allocation delay in figure-72 are same but have different name and descriptionStream index is listed in figure-66 but there is no description of what it is?Use of "CTRB" without definitionProbe request and response command types are redundant since their format is exactly same. Define one command with that format "Probe Information" and use it both as request and responseUse of Alternate PNC pullout command unneeded given the change in Clause8.2.3 p139 line30-32.Alternate PNC announcement command unneeded.DeviceID parameter name is incorrect.MAx TX delay variation in figure-77 and MAximum allocation delay in figure-72 are same but have different name and descriptionStream index is listed in figure-66 but there is no description of what it is?Use of "CTRB" without definitionProbe request and response command types are redundant since their format is exactly same. Define one command with that format "Probe Information" and use it both as request and responseUse of redundant fields that increase the overhead and lead to inconsistencies in the implementationUse of "commands frame body chall be formatted ..." is wrong. Command is not a frame by itself, but some command frames may have only one command in them (along with MAC header, FCS etc.)Just the number of commands, fields/subfields in information elements makes one wonder why power management has to be this complex. Why not simple commands like (a) sleep-time-request from DEV to PNC (b) sleep-time-grant/reject from PNC to DEV? What is not being acheived in those simple commands that is being achieved by this complex mechanism? What is the justification to add this complex mechanism to a draft that is supposed to spec a low-cost, low-power PAN implementation?Ordering the subclauses for commands to be in the same order as the order of commands in Table-65 is very helpfulFor ease of understanding and implementation (use of clean ifs and elses), there is a need to reorder the command-type value to a given command.Figure 36: spec on length missing1. Figure-34 is inconsistent in "length" field and the contents of the element 2. Nowhere in the draft I see the text describing how this is set at PNC and how it is used at DEVs. 3. on lines 35:36: If EPS device is asleep how does it make use of this info? if this is for other DEVs, how is it useful. 4. What is the guarantee that DEVs always get EPS status of another DEV through beacon? Why not use a simple mechanism wherein a DEV can tell the PNC that it is going to be asleep and hence not allocate GTS with the current DEV in question as the recipient? What is the justification for the complexity of this mechansism that is being thrusted upon implementors?Lack of examples to MaxAssignedCTAs and MaxProcessedCTAs make the readers think they are same.Use of "guard time" without defining it. Beacon does not contain it.Definition of SFNext is better suited to be later in the sub-clauseKey change field in figure-31 is unusedGiven that there can be different guard-band between GTS and between CFP and CAP depending on PHY type and network conditions, it is a good idea to let the PNC account for it when allocating the channel time. To enable that degree of freedom at PNC we ne