Standard Jet DBЕnb` ТUщЉgr@?œ~Ÿџ…š1ХyКэ0МпЬcйфУŸFћŠМN›iь7@жœњлЬ(ц$Š`I{6шрпБjfCв=Б3)ѓy['|*jњ|™˜§мTЙЧ}‚f_•ја‰$…gЦ'DвюЯeэџЧFЁx эщ-bдT4.0dЛvаˆ\"шЋs;џ с У — ] ш А ’ t V 8 Ю  S  о І g , щ Ћ  € €џўlb34_r0.Autonumber1 ' € €џўlb34_r0.SuggestedRemedy6 g €€џўlb34_r0.Comment. g €€џўlb34_r0.CommentType2 g €€џўlb34_r0.Line+ g €€џўlb34_r0.Page+ g €€џўlb34_r0.Subclause0 g €€џўlb34_r0.Clause- g €€џўlb34_r0.CommenterName4 g €€џўlb34_r0.Autonumber1 g €lb34_r0  € G € G €џ  € G € €џўlb34_r0.Line+ ' € €џўlb34_r0.Page+ ' € €џўlb34_r0.Subclause0 ' € €џўlb34_r0.Clause- ' €lb34_r0  € G € G €џ  € G€ €џўlb34_r0.Line+ '€ €џўlb34_r0.Page+ '€ €џўlb34_r0.Subclause0 '€ €џўlb34_r0.Clause- '€ўјџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџо Yи№ES  Y   Y Y  Y Y  Y  ўY  Y   Y u Y o Y n Y zў Y 2lўY  Y  z Y  pўY ConnectDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeƒџџџџnџџџџiџџџџџџџџфіEƒџџџџEџџіџџфџџџџEџџіџџфџџфіEYџџџџYџџџџIdParentIdName        џџb b b b bbbhange 802.11.џўAdd editing instruction: ""Add the following element to table 20 of ... and assign an available element ID"".џўRemove the MLME interface and add section saying that the MIB values are updated whenever a beacon is received. Beacon transmitted contains latest MIB values of these variables. Support T1 and TWLAN MIB variables (TWPAN is redundant and problemmatical if TWLAN+TWPAN != TB).џўSignal T1 and TWLAN. Add ""editing instructions"" to this document for any required changes to 802.11.џўAdd "" or when SCO links need to be supported."" to the end of this para.џўI'll give you a wmf from my original drawing.џўAdd to reference section and make references by [1] rather than name.џўsuggest ""implementation specific.""џўCheck spacing before and after periods throughout table.џўCompare and contrast the simulated results with the earlier theoretical predictions.џўShould say, ""Thus, the interference between the WLAN FH and TG1 systems is limited.""џўsay, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?)џўImprove the explanation in the text.џўFix the Bluet{99} citation error.џўDefine phi2 as deviation, and as a function of t and b, like the BT case in 5.4.1.1.џўShould be ""symbol intervals,"" not ""symbols.""џўKeep a single style format thoughout the symbol list. Include units in all definitions.џўTo define A, mention that it is the peak amplitude.џўeferences should be cited by number [1].џў""The GFSK signal can be represented as ([B1], [B6], [B9])...""џў""Bandwidth"" should be lower case.џўDelete the reference to orthogonal FSK, and ensure that the following technical derivation is still valid without the assumption of orthogonality.џў""The intended transmission is attenuated by the path loss as defined in subclause 5.2 to the receiver. The transmitted signal power, less the path loss, is the signal power at the receiver.""џўchange to, ""due to near-field and implementation effects.""џўEither change the sentence to ""An adaptive notch filter can be used to ..."" or define the term ""frequency nulling"" prior to its use.џўThe coexistence modeling approach used is based on detailed simulation models for the Radio Frequency (RF) channel and the Medium Access Control (MAC) and Physical (PHY) layers developed in OPNET and ANSI C, respectively.џўAvoid using ""interfere""--for example, ""...that might reduce the quality of desired received signals ...""џў""The ability of each of a set of (perhaps disparate) systems to perform specified tasks in a given shared environment.""џўAs I understand the draft, 2 MHz is not included. If so, remove it from line 3.џўUse complete sentences to describe the scope of the document.џўReplace with reference to Figure 53џўClean up the reference to Bluetooth (802.15.1?)џўProvide an explanation of this reasoning.џўReplace with "ќџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџЉOYISY Y Y  Y 2ўACMFInheritableObjectIdSIDƒџџџџџџ џџџџџџџџџџџџ AtˆYџџџџObjectIdџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ§џџџўџџџўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ0bЗ ТРPropData џџџџForms џџџџаˆ Таˆ ТReportsџџџџаˆ Таˆ ТўџџџўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџijфMSysDbModulesџџџџџџџџаˆ Таˆ ТScriptsџџџџџџџџџџџџаˆ Таˆ ТVBAџџџџџџџџ аˆ ТіЛ ТCmdbarsџџџџџџџџџџџџаˆ Таˆ ТDataAccessPages џџџџџџџџџџџџаˆ Таˆ ТDatabasesџџџџџџџџ аˆ ТPП Т0џџџџ аˆ ТPП ТBlob џџџџџџџџџџџџўџџџCustomGroups џџџџаˆ Таˆ ТVBAProjectџџџџџџџџp›‰ Тp›‰ ТDirDataџџџџџџџџџџџџAcessVBADatažšы Y"AccessS"Y  Y 0Y Y  Y oў Y 8ўY  Y ўAttributeExpressionFlagLvExtra Name1 Name2ObjectId Orderƒџџџџџџџџџџџџџџ Yџџџџ"ObjectIdAttributeџџAcessVBADataџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ §џџџўџџџ ўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџVBAџџџџџџџџ№Е ТіЛ ТPROJECTwmџџџџџџџџџџџџPROJECTџџџџ+_VBA_PROJECTџџџџџџџџ ўџџџўџџџўџџџўџџџўџџџ ўџџџ !"#$%&'()*+,-./012345ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot EntryџџџџџџџџPП Т € PropData џџџџForms џџџџаˆ Таˆ ТReportsџџџџаˆ Таˆ ТijфMSysDbID="{7C6F6A2F-E8D8-4835-9DFD-B0A5435629D5}" Name="lb14_r0" HelpContextID="0" VersionCompatible32="393222000" CMG="8183828286828682868286" DPB="020001828383838383" GC="8381800500060006FF" [Host Extender Info] &H00000001={3832D640-CF90-11CF-8E43-00A0C911005A};VBE;&H00000000 [Workspace] оБ€0* pH‚dфlb14_r0Q(@=­ l €пЩ@> J"< DAO>BDA O ™*\G{0002 5E01-0C  0046}#5.0#0#D:\Program Files€\Common Microsoft Shared\w350.DLL#‡ 3.51 Object Library€HUstdole>‚fstdole5^f€\€^04V3„[W-^2^WINNT\Sys@tem32\ƒ12.tlb#OLE Automat˜ion/СVBIDE> VBIDдECЗ€­€C0E157ŸC5.B3яPVBA\Р6E6EXT.OLBHRVisual Basic for Applic1s Extdirџџџџџџџџџџџџ тџџџџџџџџџџџџžšЫ -Yи№ESY Y Y  Y  ў Y фіў Y іEў Y Eў Y фўccolumn grbiticolumnszColumnszObject$szReferencedColumn$szReferencedObjectszRelationshipƒџџEџџіџџфџџџџEџџіџџфџџџџE фіE‚ƒџџEџџіџџфџџџџEџџіџџфџџџџE фіE‚ƒџџEџџіџџфџџџџEџџіџџфџџџџE фіE‚YџџџџYџџџџYџџџџszObject$szReferencedObjectszRelationshipџџice2000\Office\msacc9.olb#Microsoft Access 9.0 Object Library*\G{00025E01-0000-0000-C000-000000000046}#5.0#0#D:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL#Microsoft DAO 3.51 Object LibraryИ*\G{00020430-0000-0000-C000-000000000046}#2.0#0#D:\WINNT\System32\stdole2.tlb#OLE AutomationZ*\G{0002E157-0000-0000-C000-000000000046}#5.3#0#D:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB#Microsoft Visual Basic for Applications Extensibility 5.3 џџџџџџџџпЩ@>џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ7Ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџx€ џ%AccessVBAїтWin16С~Win32MacГВVBA6­#lb14_r0uЪDAOž‚stdole“`VBIDEAџџџHџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ џџџџ џџџџџџ žšYЛv1ьЇbи “ N Ф  : ѕ А k & с œ W  Э ˆ C ўЙt/ъЅ Т ЈТ”ЧЪ‡ВwcctLLS@LL0јEИ№Eџ№cpeАd cфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEАg hџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ0f№fPш їEџџџџџџџџџўџџџџџMSysAccountsћяИXђџџџџ €€€@@   €€€€@@ OJmJJMMQkkfJUQkOJmJLJkQkSdi`k `dOo^Qk iQ^JmYdbkWYfkiQfdimk kMiYfmk kvkiQ^ mJL^QkM^JokQ+kdim^L<>+i6`kvkJMMQkkdL[QMmk`kvkJMQk`kvkY`QuMd^o`bk`kvkY`QukfQMk`kvkdL[QMmk`kvkhoQiYQk`kvkiQ^JmYdbkWYfkkdimLvM^JokQsWd^QJMMQkk^Jvdom`kvkOLko``JivYbSdokQiOQSYbQO€Vb.€Vb/€YG€YGbbbbbb b b b bbbi_VBA_PROJECTНЬa^џ  ф*\G{000204EF-0000-0000-C000-000000000046}#3.0#9#D:\Program Files\Common Files\Microsoft Shared\VBA\VBA332.DLL#Visual Basic For Applications*\G{4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}#8.0#0#D:\Program Files\Microsoft Office\Office\MSACC8.OLB#Microsoft Access 8.0 Object Library*\G{00025E01-0000-0000-C000-000000000046}#4.0#0#D:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL#Microsoft DAO 3.51 Object Library џџџџџџџџѕЪЖ<џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ7Ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџx€џ”$AccessVBAїтWin16С~Win32MacГВDAOž‚lb14_r0uЪџџ0џџџџџџџџџџџџџџџџџџ џџџџџџџџџџџџџџџџџџdirБ€0* pH‚dфlb14_r0Q(@=­ l €ѕЪЖ< J"< DAO>BDA O ™*\G{0002 5E01-0C  0046}#4.0#0#D:\Program Files€\Common Microsoft Shared\w350.DLL#‡ 3.51 Object Library€H†‚7Ў H  @€ @€ @€        €€€€€€R€Y€]џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ EЮ Т€ VBAџџџџџџџџEЮ ТEЮ ТVBAProjectџџџџEЮ ТEЮ ТVBAџџџџџџџџEЮ ТEЮ Тdirџџџџџџџџт_VBA_PROJECTџџџџџџџџџџџџ PROJECTџџџџ-+PROJECTwmџџџџџџџџџџџџ2ўџџџ  !"#$%&'()*+,ўџџџ./01ўџџџўџџџўџџџўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџоБ€0* pH‚dфlb14_r0Q(@=­ l €пЩ@> J"< DAO>BDA O ™*\G{0002 5E01-0C  0046}#5.0#0#D:\Program Files€\Common Microsoft Shared\w350.DLL#‡ 3.51 Object Library€HUstdole>‚fstdole5^f€\€^04V3„[W-^2^WINNT\Sys@tem32\ƒ12.tlb#OLE Automat˜ion/СVBIDE> VBIDдECЗ€­€C0E157ŸC5.B3яPVBA\Р6E6EXT.OLBHRVisual Basic for Applic1s ExtensibiliИty РР+€‚›ˆТ7Ў‚Ьamџ  фњ*\G{000204EF-0000-0000-C000-000000000046}#4.0#9#D:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA6\VBE6.DLL#Visual Basic For Applications*\G{4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}#9.0#0#D:\Program Files\Microsoft Office2000\Office\msacc9.olb#Microsoft Access 9.0 Object Library*\G{00025E01-0000-0000-C000-000000000046}#5.0#0#D:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL#Microsoft DAO 3.51 Object LibraryИ*\G{00020430-0žš  @€ @€ @€ @€ @€ @€ @€ @€ @€````````` ` ` ` `````````````$`% `& `' `( `C `D `E `F `G `H€`9€`:€`;€`<€`0€`1€`2€`=€`>€`?€`@€`A€`B€`)€`*€`+€R`,€R`-€R`.€R`/€Y`3€Y`4€Y`5€]`6€]`7€]`8```` `` ````!`"`#џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџx€ џ%AccessVBAїтWin16С~Win32MacГВVBA6­#lb14_r0uЪDAOž‚stdole“`VBIDEAџџџHџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ џџџџ џџџџџџ ID="{7C6F6A2F-E8D8-4835-9DFD-B0A5435629D5}" Name="lb14_r0" HelpContextID="0" VersionCompatible32="393222000" CMG="8183828286828682868286" DPB="020001828383838383" GC="8381800500060006FF" [Host Extender Info] &H00000001={3832D640-CF90-11CF-8E43-00A0C911005A};VBE;&H00000000 [Workspace] ijфMSysDbAcessVBADataџџџџџџџџџџџџ3Forms  џџџџEЮ ТEЮ ТCmdbarsџџџџџџџџџџџџEЮ ТEЮ ТModules џџџџEЮ ТEЮ ТReportsџџџџџџџџџџџџEЮ ТEЮ ТScripts џџџџEЮ ТEЮ ТPropDataџџџџџџџџџџџџ4DatabasesEЮ ТEЮ Т0џџџџEЮ ТEЮ ТBlob џџџџџџџџџџџџўџџџDirDataџџџџџџџџџџџџ5CustomGroupsџџџџџџџџEЮ ТEЮ ТDataAccessPages џџџџџџџџџџџџEЮ ТEЮ ТџџџџџџџџџџџџžšV  €@ €@ €@ €@                џ                џ                  ! џюwФtЩ* ›ПZс…B,bпё+Њ…Ÿ8|(гqлэЫњPpxъp  €џџ,[  €џџ-[  €џџ.–Ыпѕяnы=ШѕЧПwъgВЗфSПn>’ј‰GcіXГUњк„ЖўЩ—зAЅЗnЩ= 8MТŽЩ&m&юwФtЩ* ›ПZс…B,bпё+Њ…Ÿ8|(гqлэЫњPpxъp  €џџ,[ -[ .–Ыпѕяnы=ШѕЧПwъgВЗфSПn>’ј‰GcіXГUњк„ЖўЩ—зAЅЗnЩ= 8MТŽЩ&m&юwФtЩ* ›ПZс…B,bпё+Њ…Ÿ8|(гqлэЫњPpxъp ,[ -[ .–Ыпѕяnы=ШѕЧПwъgВЗфSПn>’ј‰GcіXГUњк„ЖўЩ—зAЅЗnЩ= 8MТŽЩ&m&юwФtЩ* ›ПZс…B,bпё+Њ…Ÿ8|(гqлэЫњPpxъp ,[ -[ T.–Ыпѕяnы=ШѕЧПwъgВЗфSПn>’ј‰GcіXГUњк„ЖўЩ—зAЅЗnЩ= 8MТŽЩ&m&юwФtЩ* ›ПZс…B,bпё+Њ…Ÿ8|(гqлэЫњPpxъp ,[ Vў -[ VY и-ЋCт@Ф-ЋCт@TempMSysAccessObjects,[LLLLLLLLLLJ џ €Вr-ЋCт@Вr-ЋCт@DataAccessPages,[@@@@@@@@@@> џ €RЂУ?s?т@0$џLs?т@whole,[Ъ@eє@cD88,,,,,,,* џ@ €~'Iі?т@~'Iі?т@sortbyclause,[Я@ dє@cRFF:::::::8 џ@Vmб”Ъ=т@mб”Ъ=т@MSysIMEXSpecs,[<<<<<<<<<<: џRPб”Ъ=т@Pб”Ъ=т@MSysIMEXColumns,[@@@@@@@@@@> џšъzЈЪ=т@z+ъЌ@т@lb34_r0,[и@e<<<0000000. џ@€UNё$і?т@Ѓбі=і?т@clause_sort,[Я@dє@cPDD88888886 џ@€ €‚Š[‹Ъ=т@‚Š[‹Ъ=т@UserDefined,[88888888886 џ€ €‚Š[‹Ъ=т@‚Š[‹Ъ=т@SummaryInfo,[†@dDDD88888886 џ@€ €А%–зЪ=т@Вr-ЋCт@AccessLayout,[4€MR2€KeepLocal T@c†zz:::::::8 џ@€‚Š[‹Ъ=т@‚Š[‹Ъ=т@SysRel,[.........., џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Scripts,[0000000000. џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Reports,[0000000000. џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Modules,[0000000000. џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Forms,[,,,,,,,,,,* џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysRelationships-YDDDDDDDDDDB џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysQueries-Y88888888886 џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysACEs-Y22222222220 џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysObjects-Y88888888886 џ‚Š[‹Ъ=т@%z-ЋCт@€MSysDb,[@e:::......., џ@‚Š[‹Ъ=т@‚Š[‹Ъ=т@€Relationships-Y<<<<<<<<<<: џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€Databases-Y44444444442 џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€Tables-Y.........., џ ZerosDateOrderDecimalPointFieldSeparatorFileType SpecIDSpecNameSpecTypeStartRowTextDelimTimeDelimƒџџ џџ„џџџџFџџ џџ„џџџџFџџ WXF„ ‰YџџџџPrimaryKeyџџVRћ-ЋCт@Rћ-ЋCт@MSysIMEXSpecs::::::::::: ПRRћ-ЋCт@Rћ-ЋCт@MSysIMEXColumns>>>>>>>>>>> Пш@-ЋCт@ш@-ЋCт@lb34_r0........... П€ЁФ-ЋCт@ш@-ЋCт@clause_sort66666666666 П€ €ЁФ-ЋCт@ЁФ-ЋCт@UserDefined66666666666 П€ €ЁФ-ЋCт@ЁФ-ЋCт@SummaryInfo66666666666 П€ €ЁФ-ЋCт@ЁФ-ЋCт@AccessLayout88888888888 П€~†-ЋCт@~†-ЋCт@SysRel,,,,,,,,,,, П€~†-ЋCт@~†-ЋCт@Scripts........... П€~†-ЋCт@~†-ЋCт@Reports........... П€~†-ЋCт@~†-ЋCт@Modules........... П€~†-ЋCт@~†-ЋCт@Forms*********** П~†-ЋCт@~†-ЋCт@€MSysRelationships-YDDDDDDDDDDB џ~†-ЋCт@~†-ЋCт@€MSysQueries-Y88888888886 џ~†-ЋCт@~†-ЋCт@€MSysACEs-Y22222222220 џ~†-ЋCт@~†-ЋCт@€MSysObjects-Y88888888886 џ~†-ЋCт@~†-ЋCт@€MSysDb,[.........., џ~†-ЋCт@~†-ЋCт@€Relationships-Y<<<<<<<<<<: џ~†-ЋCт@~†-ЋCт@€Databases-Y44444444442 џ~†-ЋCт@~†-ЋCт@€Tables-Y.........., џ      €€€€€€R џџџџFџџ џџ„џџџџFџџ џџ„SU F„‰YџџџџYџџџџ Index1PrimaryKeyџџerFaxCommenterCo ClauseSubclausePageLineCommentTypeCommentSuggestedRemedyResponseCommentStatusResponseStatus  џџthem.1051ћяюэшоtsmYI: џћ> 20Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation10.2.4T""The Clear-to-Send (CTS) packet is addressed to its own 802.11 MAC address plus the group address bit is set to 1 (multicast group). This allows any other Access Point on the same channel to determine that this is a pseudo-reservation message and to notRemove this comment or add normative editing instructions to change 802.11.TE-??XOŠ@ EK@ C105028тромаФУТНrtsmYI: џџџj< +`O0Stephens, Adrianadrian.stephens@mobilian.com+44 1954 204609+44 771 276 3448Mobilian Corporation10.2.2TSection 10.2.2. It is not necessary to have both an MLME and a MIB interface to these values. Recommend just a MIB one (less text!). Should have just T1 and TWLAN variables.Remove the MLME interface and add section saying that the MIB values are updated whenever a beacon is received. Beacon transmitted contains latest MIB values of these variables. Support T1 and TWLAN MIB variables (TWPAN is redundant and problemmaticalTE-??XOЏ@D@ F1043DDB@4('&!#tsmYI: џћдLVAL Й2СˆPPУУ++ТОј @€ @€ @€ @€ @€ @€ @€ @€the word ""dynamically"" is an adverb. What is it modifying? ""The PTA technique however coordinates sharing of the medium on dynathe word ""dynamically"" is an adverb. What is it modifying? ""The PTA technique however coordinates sharing of the medium on dynamically, based on the traffic load of the two wireless networks.""This sampling rate is appropriate for f d up to 22 MHz. A uniform random delay t d = [0,T) and a random phasechange Similarly, changes in the behavior of the MAC layer protocol and the associated data traffic distribution could pl=€ЁФ-ЋCт@ш@-ЋCт@clause_sort66666666666 П€ €ЁФ-ЋCт@ЁФ-ЋCт@UserDefined66666666666 П€ €ЁФ-ЋCт@ЁФ-ЋCт@SummaryInfo66666666666 П€ €ЁФ-ЋCт@ЁФ-ЋCт@AccessLayout88888888888 П€~†-ЋCт@~†-ЋCт@SysRel,,,,,,,,,,, П€~†-ЋCт@~†-ЋCт@Scripts........... П€~†-ЋCт@~†-ЋCт@Reports........... П€~†-ЋCт@~†-ЋCт@Modules........... П€~†-ЋCт@~†-ЋCт@Forms*********** П~†-ЋCт@~†-ЋCт@€MSysRelationships-YDDDDDDDDDDB џ~†-ЋCт@~†-ЋCт@€MSysQueries-Y88888888886 џ~†-ЋCт@~†-ЋCт@€MSysACEs-Y2222222222>Еd Д_Л Z § Д g  Э ‚ п ~ ) М c  ЅLн|џџ €RЂУ?s?т@0$џLs?т@wholez‹Ъ@bє@aD88,,,,,,,* џ@ €~'Iі?т@~'Iі?т@sortbyclausez‹Я@bє@aRFF:::::::8 џ@]mб”Ъ=т@mб”Ъ=т@MSysIMEXSpecsz‹<<<<<<<<<<: џYPб”Ъ=т@Pб”Ъ=т@MSysIMEXColumnsz‹@@@@@@@@@@> џR и-ЋCт@Ф-ЋCт@MSysAccessObjectsz‹DDDDDDDDDDB џšъzЈЪ=т@ sуEЋCт@lb34_r0z‹и@b<<<0000000. џ@ €UNё$і?т@Ѓбі=і?т@clause_sortz‹Я@bє@aPDD88888886 џ@€ €‚Š[‹Ъ=т@‚Š[‹Ъ=т@UserDefinedz‹88888888886 џ€ €‚Š[‹Ъ=т@‚Š[‹Ъ=т@SummaryInfoz‹†@bDDD88888886 џ@€ €А%–зЪ=т@пЁOFЋCт@AccessLayoutz‹4€MR2€KeepLocal TТ@a†zz:::::::8 џ@€‚Š[‹Ъ=т@‚Š[‹Ъ=т@SysRelz‹.........., џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Scriptsz‹0000000000. џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Reportsz‹0000000000. џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Modulesz‹0000000000. џ€‚Š[‹Ъ=т@‚Š[‹Ъ=т@Formsz‹,,,,,,,,,,* џ€Вr-ЋCт@Вr-ЋCт@DataAccessPagesz‹@@@@@@@@@@> џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysRelationships{‰DDDDDDDDDDB џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysQueries{‰88888888886 џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysACEs{‰22222222220 џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€MSysObjects{‰88888888886 џ‚Š[‹Ъ=т@%z-ЋCт@€MSysDbz‹@b:::......., џ@‚Š[‹Ъ=т@‚Š[‹Ъ=т@€Relationships{‰<<<<<<<<<<: џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€Databases{‰44444444442 џ‚Š[‹Ъ=т@‚Š[‹Ъ=т@€Tables{‰.........., џY "тФІˆ\"шЋs;џ с У — ] ш А ’ t V 8 Ю  S  о І g , щ Ћ €џџџџџџџџџџџџџџџџџџџџџџџџensibiliИty РР+€‚›ˆТ7Ў‚Ьamџ  фњ*\G{000204EF-0000-0000-C000-000000000046}#4.0#9#D:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA6\VBE6.DLL#Visual Basic For Applications*\G{4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}#9.0#0#D:\Program Files\Microsoft Office2000\Office\msacc9.olb#Microsoft Access 9.0 Object Library*\G{00025E01-0000-0000-C000-000000000046}#5.0#0#D:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL#Microsoft DAO 3.51 Object LibraryИ*\G{00020430-0000-0000-C000-000000000046}#2.0#0#D:\WINNT\System32\stdole2.tlb#OLE AutomationZ*\G{0002E157-0000-0000-C000-000000000046}#5.3#0#D:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB#Microsoft Visual Basic for Applications Extensibility 5.3 џџџџџџџџпЩ@>џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ7Ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџx€ € T€џўlb34_r0.Autonumber1 ' €T €џўlb34_r0.SuggestedRemedy6 g €T€џўlb34_r0.Comment. g €T€џўlb34_r0.CommentType2 g €T€џўlb34_r0.Line+ g €T€џўlb34_r0.Page+ g €T€џўlb34_r0.Subclause0 g €T€џўlb34_r0.Clause- g €T€џўlb34_r0.CommenterName4 g €T€џўlb34_r0.Autonumber1 g €Tlb34_r0  €T G €T G €џT  €T G € €џўlb34_r0.Line+ ' € €џўlb34_r0.Page+ ' € €џўlb34_r0.Subclause0 ' € €џўlb34_r0.Clause- ' €lb34_r0  € G € G €џ  € G €  €џўlb34_r0.Line+ ' €  €џўlb34_r0.Page+ ' €  €џўlb34_r0.Subclause0 ' €  €џўlb34_r0.Clause- ' € €џўlb34_r0.Clause- g € lb34_r0  €  G €  G €џ   €  G| |Yњ˜(FNY  Y erў Y Agў Y @ў Y mў Y 8ў Y —ў Y d Y ў Y  Пd Y isd Y inў Y a Y   I Y  02ў Y d ў Y bўAutonumberCommentIDCommenterNameCommenterEmailCommenterPhoneCommenterFaxCommenterCo ClauseSubclausePageLineCommentTypeCommentSuggestedRemedyResponseCommentStatusResponseStatus  џџ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EФ„EРeАfџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ€bePш…EџџџџџџџџџўџџџџџMSysAccounts?яИИџџџџ  € “-ЋCт@ “-ЋCт@clause_sort66666666666 П€ € “-ЋCт@ “-ЋCт@UserDefined66666666666 П€ € “-ЋCт@ “-ЋCт@SummaryInfo66666666666 П€ € “-ЋCт@ “-ЋCт@AccessLayout88888888888 П€ “-ЋCт@ “-ЋCт@SysRel,,,,,,,,,,, П€ “-ЋCт@ “-ЋCт@Scripts........... П€ “-ЋCт@ “-ЋCт@Reports........... П€ “-ЋCт@ “-ЋCт@Modules........... П€ “-ЋCт@ “-ЋCт@Forms*********** П€ “-ЋCт@ “-ЋCт@DataAccessPages>>>>>>>>>>> П “-ЋCт@ “-ЋCт@€MSysRelationships{‰DDDDDDDDDDB џ “-ЋCт@ “-ЋCт@€MSysQueries{‰88888888886 џ “-ЋCт@ “-ЋCт@€MSysACEs{‰22222222220 џ “-ЋCт@ “-ЋCт@€MSysObjects{‰88888888886 џ “-ЋCт@ “-ЋCт@€MSysDbz‹.........., џ “-ЋCт@ “-ЋCт@€Relationships{‰<<<<<<<<<<: џ “-ЋCт@ “-ЋCт@€Databases{‰44444444442 џ “-ЋCт@ “-ЋCт@€Tables{‰.........., џHЛv1ьЇb €@             џ scenarios of mutual interference and which solutions address which scenario of interference.џўThe document only addresses 802.11B interference while current standardization in the 2.4 GHz band is covered in the 802.11G annex. The new modulation schemes proposed in 11G need to be taken into account in the analysis on mutual interference and in proposed solutions. Any new development in this band is likely to address 802.11G rather than just 11B. Any investment in collaborative schemes must have applicability for 11G to be of interest.џўThe recommended practice to use a notch filter has the problem that 802.15.1 signals are frequency hopping; this means that the 802.11b receiver would have to change its notch and equalizer if a hop occurs within a packet. It is not clear whether this is possible without fatal transient effects that would kill the 802.11b packet.џўThis says No new on-air signalling is required . However, since we need a new information element for beacon and probe response management frames I don t see how this statement is true. In fact I think new on-air signally is required and this is outside the scope of a recommended practice.џўThe 802.11 MAC does not allow the transmission of a CTS frame in isolation with a specific duration value. This frame exchange sequence and duration setting facility simply do not exist in the current 802.11 MAC. This is one reason why in the IEEE802.11 TGh draft we have defined a new quiet period mechanism (an aside is that even if it did exist the duration is limited to 32Kus). Note that (a) even if this CTS mechanism existed it would be imperfect and (b) the group addressing scheme to involve other APs violates the current rules further. This latter point is due to the fact that CTS is not used in multicast communication.џўFirstly see comments from this author on appropriate scope for an 802.15 recommended practice. Second the 802.11 MAC behaviour around the start and end of the WPAN interval needs to be more precisely defined, for example, do STAs that defer due to a pending WPAN period select a backoff value, increment their retry counters, etc..џўNew 802.11 MLME primitives are outside the scope of this recommended practice. If it is possible to specify this coexistence mechanism without change to the 802.11 MAC then this MIB should be defined as an 802.15.2 MIB.џўTiming values to be distributed through the WLAN network management tool (i.e. outside the scope of this recommended practice). This implies that the element defined is not actually required and that some 802.15.2 MIB is being set by a higher layer protocol. If that is the case why define the element at all (which is outside the scope of a 802.15 recommended practice). I also note that (a) these need to get into STAs before active scanning to avoid getting management frames sent in the WPAN period, and (b) some description of IBSS operation is required.џў No new on-air signalling is required . However, a new information element for DB@BD „˜’Ѕ”$Љh%-R)Z•LVAL#А„`<шП˜hC Є g <  Й - ч у ‡ A aЧ—rПi4‡CщThis puzzles me. How does this result compare with the earlier theoretical prediction that TG1 packets will hit almost every WLAN packet (s. 4.1.1), but most TG1 packets џўThis puzzles me. How does this result compare with the earlier theoretical prediction that TG1 packets will hit almost every WLAN packet (s. 4.1.1), but most TG1 packets will not be hit by WLAN packets (due to the difference in hop rate--s. 4.1.3)? How can "the packet error rate for both the IEEE 802.15.1 and WLAN is negligible (below 5%)"?џўI don't understand the explanation for the delay spike. Does this imply that the simulated time period was too short (i.e., too few packets being received for good statistical inference)? џўShould be ""symbol intervals,"" not ""symbols."" (We assume possibly multiple bits per symbol, but not multiple symbols per bit.)џўList of symbol definitions does not keep a single format throughout (extraneous semicolons and ""ands"" abound). Also, units should be included in all symbol definitions.џўTo define A, mention that it is the peak amplitude.џўReferences should be cited by number [1] or author (Smith 2002), not both Smith [1].џў""The GFSK signal can be represented by Murota [B6], Aulin [B1], and Steele [B9] as"" is really awkward (I mean, the rest of us can also represent the GFSK signal the same way).џў""Bandwidth"" should be lower case.џў""differential"" QPSK, not ""differentiated.""џў15.1 is *not* orthogonal FSK. The modulation index h = 0.315, not 0.5.џўWhere did these numbers come from? A sample calculation would be most welcome.џў""The intended transmission is attenuated by the path loss as defined in subclause 5.2 to the receiver. This is the signal power at the receiver."" This is not correct.џў""near-field"" is not an ""implementation effect.""џў"frequency nulling" has not yet been defined; since this term usually refers to matching the frequencies of two independent sources, it's quite a puzzle what this means here without a definition. (As an aside, the definition given later in the text more closely resembles an adaptive notch filter ... why not call it that?)џў""respectively"" is confusing here, since there are three precedents but only two sequels.џўcommas needed before and after ""say""џўWhile I know this is the definition in the IEEE dictionary, defining ""interference"" using the word ""interfere"" doesn't provide much light on the matter--especially since ""interfere"" is not in the IEEE dictionary.џўStyle error: Definition is a complete sentence; all others are not.џў"Coexistence" is poorly defined:(a) The "task" is not defined. All tasks? Any one task? Some specific task? All the time? (b) The definition is one-sided: "The ability of *one* system to perform a task ...". A dictionary definition is "to exist together, at the same time, or in the same place," implying that A does not coexist with B, nor B with A; rather, A and B coexist *together*.џўThe phrase ""set of rules"" is used in many definitions, and is undefined.џўLine 3 says 2 MHz is included; line 7 says it is not.џўIncomplete sentences in scope descriptionџўFigure shows Bluetooth devices instead of 802.15.1 devices.џўIt's not clear to me why a narrowband interferer will be attenuated more at the middle of the spectrum than at 1 MHz away.џўThis sentence doesn't make sense.џўI don't see the curve for 802.15.1.џўThe word ""required"" doesn't make sense here.џўShould be 802.11 instead of 802.15.1.џўTable number shouldn't include em-dash.џўTable numbers should not include the em-dashes.џўThis paragraph is poorly written.џўTwo periods at the end of the lineџўRefers to Bluetooth 1.1 hop kernelџўMissing period at the end of the sentence.џў""Committee of the IEEE Society"", and ""Abstract"" are in incorrect position.2\ є 4  Ж  Y Ё ѓZœ%~кѓ%?h0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil12џў12.2.1775E€џўReference to Figure xxx%@џўTE-?? Is the correct figure 53?XOАЎЌŠ~YWUQIE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil9џўTable 1033џў10-20E €џўBT is used instead of 802.15.1€џўReplace BT with 802.15.1.џўTE-AgreeXOПНЛБŠ^\UQGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil9џўFigure 1733џў21-51E=@ "€џўReplace Bluetooth with 802.15.1.џўTE-AgreeXOЇЅЃ™k_]VRGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil6џў6.0298E!€џўBad citation of Bluetooth spec.1@џўTE-Agree Will remove the end of the sentenceXOРОМTRPLGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.4.2.1226TR|@ +@џўTE-??XO}{yrfZVTPGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.4.2.12152E#@ G@џўTE-AgreeXO€~|rfZXTPGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.4.1191E€џўWhy is there (23)?!€џўRemove this or add explanation.џўTE-Do Not Accept, This is from Bluetooth to reflect that there are two differenct frequency hopping sets due to regulations 79 or 23. See 802.15.1 for further detailsXOPNLЃvVTRNGE;;-пџ 0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џўFigure 41828E%@ €џўAdd the 802.15.1 curve.џўTE-??XO—•“Œg[YUQGE;;-пџ 0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў3.6.31620E0@€џўRemove the word ""required"".џўTE-??XOš˜–dXVRNGE;;-пџ 0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.3.6.21544E"€џўMissing parentheses in equation.€џўAdd parentheses.џўTE-??XOБЏ­ІˆZXTPGE;;-пџ 0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.3.6.21539E'@ €џўReplace.џўTE-??XO‡…ƒ|fZXTPGE;;-пџ 0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.3.5143E)@€џўRemove the em-dash.џўTE-AgreeXO‘ƒbVTRNGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil5џў5.3.3139E1@€џўRemove the em-dashes.џўTE-AgreeXO“‘…bVTRNGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil4џў4.1.48џў11-19E#@U@џўTE-??XO|zxqeYWPNGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil4џў4.1623E!€џўRemove this one line paragraph. €џўRemove it.џўTE-??XOЄЂ ™TRNLGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil4џў4.064E$@€џўRemove one of themџўTE-AgreeXOŒŠˆ~^RPNLGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil3џў3.3549E$@"€џўReplace with 802.15.1 hop kernelџўTE-??XO™—•Ž`TRNLGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil3џў3.1.3321E,@ €џўAdd it.џўTE-AgreeXO…ƒwbVTPNGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil1џў1.2221E€џў802.119 WLAN €џў802.11 WLANџўTE-AgreeXO•“‘‡nTRNLGE;;-пџ0џўSeals, Michaelџўmseals@intersil.comџў321-724-7172џўIntersil00I43EP@€џўFix.џўTE-AgreeXO}{yo]QOKIGE;;-пџ=LVAL)Ћd9уЄRз i Š Т l G  м Ї M  ХЂ|)б{AдЅZђлlt5ѕ:пThis draft is generally well џўThis draft is generally well written and ready forAdd ""Frequency nulling"" to clџўAdd ""Frequency nulling"" to clause 3.1 as a definition or term.џўReplace ""IEEE 802.15.2 has decided to select"" to ""This recommended practice selects"".џўRemove all references to collaborative coexistence techniques in the document. Modify Section 4.3 to delete references to Collaborative models. Delete Section 4.3.2 Delete Section 10џўIn the absence of any such coordination, remove section 12.3.џўAdd a statement of compatibility to the BT SIG AFH mechanism.џўRemove all mention of communication between slave and master in this section. Make appropriate adjustments so that master operates only on the basis of local knowledge.џўRemove this comment or add normative editing instructions to change 802.11.џўAdd editing instruction: ""Add the following element to table 20 of ... and assign an available element ID"".џўRemove the MLME interface and add section saying that the MIB values are updated whenever a beacon is received. Beacon transmitted contains latest MIB values of these variables. Support T1 and TWLAN MIB variables (TWPAN is redundant and problemmatical if TWLAN+TWPAN != TB).џўSignal T1 and TWLAN. Add ""editing instructions"" to this document for any required changes to 802.11.џўAdd "" or when SCO links need to be supported."" to the end of this para.џўI'll give you a wmf from my original drawing.џўAdd to reference section and make references by [1] rather than name.џўsuggest ""implementation specific.""џўCheck spacing before and after periods throughout table.џўCompare and contrast the simulated results with the earlier theoretical predictions.џўShould say, ""Thus, the interference between the WLAN FH and TG1 systems is limited.""џўsay, ""Mb/s WLAN"" not just ""Mbit/s."" (Isn't Mb/s standard form, not Mbit/s?)џўImprove the explanation in the text.џўFix the Bluet{99} citation error.џўDefine phi2 as deviation, and as a function of t and b, like the BT case in 5.4.1.1.џўShould be ""symbol intervals,"" not ""symbols.""џўKeep a single style format thoughout the symbol list. Include units in all definitions.џўTo define A, mention that it is the peak amplitude.џўeferences should be cited by number [1].џў""The GFSK signal can be represented as ([B1], [B6], [B9])...""џў""Bandwidth"" should be lower case.џўDelete the reference to orthogonal FSK, and ensure that the following technical derivation is still valid without the assumption of orthogonality.џў""The intended transmission is attenuated by the path loss as defined in subclause 5.2 to the receiver. The transmitted signal power, less the path loss, is the signal power at the receiver.""џўchange to, ""due to near-field and implementation effects.""џўEither change the sentence to ""An adaptive notch filter can be used to ..."" or define the term ""frequency nulling"" prior to its use.џўThe coexistence modeling approach used is based on detailed simulation models for the Radio Frequency (RF) channel and the Medium Access Control (MAC) and Physical (PHY) layers developed in OPNET and ANSI C, respectively.џўAvoid using ""interfere""--for example, ""...that might reduce the quality of desired received signals ...""џў""The ability of each of a set of (perhaps disparate) systems to perform specified tasks in a given shared environment.""џўAs I understand the draft, 2 MHz is not included. If so, remove it from line 3.џўUse complete sentences to describe the scope of the document.џўReplace with reference to Figure 53џўClean up the reference to Bluetooth (802.15.1?)џўProvide an explanation of this reasoning.џўReplace with ""The power spectrum of the Barker codes is: Lee [B11]""џўPlease rewrite this section using better English and a more coherent flow of ideas.fџш У Д м š у2*sМ$gR–фНiЅоFф2ыАo)м•*%0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.4.11851E%@%@џўTE-AgreeXO•“‘‡{omie^\RA0џџ$0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.3.6.3165T0@€џўChange to ""differential.""џўTE-?? Not the only place where this term is used, which is correct?XOюьъЄ{omkg^\RA0џџ#0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.3.6.11442TRI@”@ џўTE-??XO–”’‹sokg^\RA0џџ"0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џўTable 3, 4, 513џў11-46TQ@€џўAdd a sample calculation.џўTE-??XOИЖД­†zxqm^\RA0џџ!0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.3.21145TЋ@Т@ џўTE-??XO’Ž‡{omie^\RA0џџ 0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.21035T5@>@ џўTE-??XOŽŒ…ymkgc^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola4џў4.3.2922EF@Š@ џўTE-??XOŽŒ…ymkge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola4џў4.2826E\@п@ џўTE-?? English reading indicates only two, but it is confusing for detemining the pairingXOспнƒwkiec^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola4џў4.1.3749E€џў""exact same"" is redundant.€џўdelete ""exact""џўTE-AgreeXOУСПЕ—mkge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola4џў4.1.1654E(@ €џўAdd commas.џўTE-AgreeXO žœ’ymkge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola3џў3.1.8336Tм@n@џўTE-??XOŽŒ…ymkge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola3џў3.1.7331EF@€џўDelete ""it is.""џўTE-Do not accept This is copied from the given reference. If permission is not obtained, entire definition will be removed.XO˜ymkge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola3џў3.1.3321E€џўperiod missing. €џўadd period.џўTE-AgreeXOБЏ­ЃŠmkge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola3џў3.1.2316TRŒ@{@џўTE-Do not accept. A term shall be general enough to be applied else where within the IEEE.XOшцф‡{okge^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola3џў3.138TRL@€џўDefine ""set of rules.""џўTE-Do not accept. A term shall be general enough to be applied else where within the IEEE.XOўќњwkgec^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola1џў1.223T7@R@џўTE-?? Remove editor's note line 7, or perhaps make clear that 2 MHz is done for Physical, but not for MACXO№юьuigec^\RA0џџ0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola1џў1.1147E+@ ?@џўTE-?? Scope must match scope in PAR, cannot change unless text in PAR is changedXOкижƒwkiec^\RA0џџ яэ 2 w О ф і ? rЊѓ2-.p’‘<А70џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation3џў3.1џў3-4џў10-15E+@G@џўTE-Do not accept Permitted as IEEE Standards Style Manual, but if permission is not obtained, then the entire definition will be removed.XO.,*ž’†„}xsq[I8џџ60џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation1џў1.0141A@€џўRemove the (tm) џўTE-Do not accept TG1 holds WPAN trade markXOкижЈŠ~~zxsq[I8џї50џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola12џў12.1.2.47322E€џўextra comma.€џўDelete comma.џўTE-AgreeXOЗЕГЉŽtrnj`\RA0џџ40џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola12џў12.1.1.17117E7@&@џўTE-??XO—•“Œ€trnj`\RA0џџ30џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola11џў11.06138EG@€џў""above (see 12.1).""џўTE-Do not accept As per The Gregg Reference ManualXOиждŸ|pnjf`\RA0џџ20џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola10џў10.4.16038E €џў""t the""€џўdelete ""t.""џўTE-?? Might be a variable and not an extraneous "t"XOомкЄ‰rplh`\RA0џџ10џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola10џўTable 215242EF@:@џўTE-AgreeXOš˜–Œ€trnj`\RA0џџ00џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola9џў9.33824TZ@"V@џўTE-??XOŽŒ…ymkgc^\RA0џџ/0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola9џў9.33824E€џўAmbiguous text.X@џўTE-??XOЁŸ–Šmkgc^\RA0џџ.0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola9џў9.237џў2429E€џўStyle is informal.S@џўTE-??XOІЄЂ›omgc^\RA0џџ-0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola9џў9.13548TР@!&@џўTE-??XOŽŒ…ymkgc^\RA0џџ,0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola6џў6.0298E€џўCitation error.#@џўTE-Agree Will remove the end of the sentenceXOЧХУ”ˆkigc^\RA0џџ+0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.4.1.2205E!€џўSymbol list style inconsistent.V@џўTE-??XOГБЏЈœomkg^\RA0џџ*0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.4.1.1205E„@ 2@џўTE-??XO’Ž‡{omkg^\RA0џџ)0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.4.1.11941E­@Z@џўTE-??XO”’‰}qokg^\RA0џџ(0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.4.1.11936E5@5@џўTE-??XO”’‰}qokg^\RA0џџ'0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola00EV@*@џўTE-Do not accept IEEE Standards Style Manual (9/20/02) clause 19 states as currently used.XOлйзznb```^\RA0џљ&0џўCallaway, Edџўed.callaway@motorola.comџў+1-954-723-8341џў+1-954-557-7187џўMotorola5џў5.4.1.11929EГ@A@џўTE-Do not accept IEEE Standards Style Manual (9/20/02) clause 19 states as currently used.XOъшц‰}qokg^\RA0џџіLVALКs<ћаpC ’  ‰  f …>—зж(ХOЊ–\С•:{џўCarl AndrenThe example does not support the text. In џўThe example does not support the text. In fact the example appears not to be an exampleџў""So the odds are that"" should be deletedџўThe word ""for say 100 ms"" should be ""for example 100 msec""џўthe sentance talks about a project. Isn't this a recommendation, like stated in line 18?џўParagraph 1.1 has 2 Mbit/s specified. Why the comment?џўAWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.џўDividing beacon interval for 802.11 will have problems for legacy stations, will have problems maintaining QoS for 802.11e, and will interfere with certain timers.џўThis discussion of stationarity indicates that the parameters are constant when they are, in fact, assumed constant.џўFrequency nulling is mentioned, but the definition is not easily found (or possibly unavailable.)џўThis clause starts with a reference to the group that wrote the recommended practice as ""IEEE 802.15.2"". It is awkward in the context of a completed recommended practiceџўAll methods suggested for collaborative coexistence impose an unacceptable burden on 802.11 equipment (requiring either "marriage" to 802.15 equipment and/or incorporation of sophisticated "interference ameliorating" subsystems) as well as upon 802.11b neџўIt is meaningless to define values contained in LMP commands unless there is a defined coordination between the BT SIG and 802.15.2 that permits 802.15.2 to define LMP commands and features.џўSection 12.2. It is not clear from this section whether it is an alternative to the AFH that will be defined by the BT SIG, or is intended to be compatible with it.џўThis section is meaningless. There is no NACK in 802.11 or 802.15.1.џўThere is no point defining behaviour requiring negotiation before use (such as setting up an EV3 connection) if there is no agreed means for 802.15.2 to define modifications to the connection setup process and LMP commands.џўI see packet scheduling only of value when a new master device talks to a legacy device. A legacy device is unable to characterise the channel and report the frequency usage table.џўTable 19 has an error. The adjacent ""none"" and ""receive"" cells near the bottom RH need to be swapped.џў"The Clear-to-Send (CTS) packet is addressed to its own 802.11 MAC address plus the group address bit is set to 1 (multicast group). This allows any other Access Point on the same channel to determine that this is a pseudo-reservation message and to not delay any of its own transmissions, such as CTSs or Beacons." No it doesn't. The current 802.1 makes no such interpretation on the CTS RA.џўDon't select an element ID, but instruct the editor to find an unused one. You cannot be sure this value will be available.џўSection 10.2.2. It is not necessary to have both an MLME and a MIB interface to these values. Recommend just a MIB one (less text!). Should have just T1 and TWLAN variables.џўSection 10.2 needs some work. The T1 and one of the TWLAN/TWPAN need to be communicated. The other duraction can be calculated from TB. This document should include changes to 802.11 in the form of editing instructions to a particular revision of 802.11(see the other 802.11 drafts for examples).џўLast para of 10.1 doesn't mention that PTA should also be used when SCO needs to be supported.џўThere's lots of ""M Weik"" in section 3.1џўWho owns the trademark on ""Wireless Personal Area Networks""??џў""vendor specific"" is not what is intended, I think.џўIncorrect period placement and capitalization: ""above. (See 12.1)""џўextra space before period: ""transmitting or receiving .Additional""ЋF { Ў й  / 1f}žгZ›нˆС“,"On interfI0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies4џў4.3.2922Ec@B@(џўTE-??XO—•“Œ€trnlecL>0џџH0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies4џў4.3839EЎ@[@'џўTE-AgreeXO˜–”Š~rpljecL>0џџG0џўCarlos Riosџўcarlos@riostek.comџў(408)202-6294џў(408)202-6294џўRiosTek LLC10џў10.1, 10.2, 10.3, 10.440TR@Л@&џўTE-??XO›™—„xttpXTG8)џћF0џўHousley, Russellџўrhousley@rsasecurity.comџў703-435-1775џўRSA Laboratories1џў1.2221E€џўChange "802.119" to "802.11b€џўChange "802.119" to "802.11bџўTE-AgreeXOХУСЗca][VTBB4пџE0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation12џў12.382TР@@@%џўTE-??XOЄЂ ™{uq[I8џћD0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation12џў12.274TЇ@?@$џўTE-??XOЄЂ ™{uq[I8џћC0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation12џў12.1.1.471TG@ €џўRemove sectionџўTE-??XOИЖД­‘…ƒƒuq[I8џћB0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation11џў11.2.164Tс@ €џўRemove all mention of EV3.џўTE-??XOТРОЗƒ}uq[I8џћA0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation11џў11.366TЗ@ Ћ@#џўTE-??XOЄЂ ™{uq[I8џћ@0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation11џў11.1.263џў12-43E!€џўFigure 43 needs to be re-drawn.џўTE-?? Action for J. LiangXOзегЗЗŠˆ}uq[I8џп?0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation10џў10.3.151Tl@  €џўSwap them.џўTE-??XOВАЎЇƒ}uq[I8џћ>0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation10џў10.2.45028TŒ@ M@"џўTE-??XOЊЈІŸ“‡…}uq[I8џџ=0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation10џў10.2.2.6.34824T}@o@!џўTE-??XOЎЌЊЃ—‹‰…uq[I8џџ<0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation10џў10.2.243TБ@@ џўTE-??XOІЄЂ›ƒ}uq[I8џћ;0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation10џў10.242T-@h@џўTE-??XOЄЂ ™{uq[I8џћ:0џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation10џў10.141T`@K@џўTE-??XOЄЂ ™{uq[I8џћ90џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation5џўFigures 9-1525E€џўThese figures are too small.€џўMake them bigger.џўTE-??XOлйзаБ‡……sq[I8џћ80џўStephens, Adrianџўadrian.stephens@mobilian.comџў+44 1954 204609џў+44 771 276 3448џўMobilian Corporation5џў5.3.212џў23-49E€џўFigure 3 looks really naf./@џўTE-??XOЦФТЛЏ‡…~zsq[I8џџ\LVAL ŸfУ1a М б ƒ   Є›„ЫŽ.Т‰'мСеŸito IEEE 802.15.1 uses frequency hopping spread spectrum, while IEEE 802.11b uses direct sequence spread spectrum and complementary code keying. The bandwidth of 802.11b is 22 MHz. 22 of the 79 hopping channels available to IEEE 802.15.1 hops are subject to interference. A frequency hopping system is susceptible to interference from the adjacent channels. This increases the total number ofџўto IEEE 802.15.1 uses frequency hopping spread spectrum, while IEEE 802.11b uses direct sequence spread spectrum and complementary code keying. The bandwidth of 802.11b is 22 MHz. 22 of the 79 hopping channels available to IEEE 802.15.1 hops are subject to interference. A frequency hopping system is susceptible to interference from the adjacent channels. This increases the total number of interference channels from 22 to 24.16 17 18 The detailed model described later quantifies the level of packet error rate. The 802.11b represents a worse interferer than the 802.11 FH. For data transfer the network throughput would decrease and the network latency would increase, in the presence of 802.11b interference. The packet error rate for SCO link can cause voice quality degradation.џўto IEEE 802.15.1 voice communications use a synchronous connection-oriented (SCO) link. Since the SCO link does not support automatic repeat request, there will be some perceivable degradation in voice quality dyuring periods of IEEE 802.11 FH interference. The detailed model described later quantifies the level of packet error rate. The network throughput would decrease and the network latency would increase for 802.11b interference. A A large number of errors on an SCO link can cause voice quality degradation.џўBoth frequency-hopping systems are susceptible to interference on the channel in use and the two adjacent channels.џўThe IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link, without data loss. A interference increases, the network latency increases, and data throughput decreases.џўThere is a potential packet collision between a WLAN packet and an 802.15.1 packet when the WPAN hops into the WLAN passband.џўMost implementations allow manual or automatic modification of the data rateџўThe IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link, without data loss. A interference increases, the network latency increases, and data throughput decreases.џўAdd sentence:The PTA technique only works well if the WPAN device also uses adaptive frequency hopping to avoid interfering with other WLANs in the same location. џўAdd sentence:Alternating Wireless Medium Access Control Area (AWMACA). All devices entering into the AWMACA shall adopt the rules of the area. 1. All WPAN master devices must role-switch to a AWMA master in the area. 2. Only piconets with a AWMA master are allowed 3. IBSS networks must adopt the timing parameters and synchronize its clock with the AWMACA. 4. All WLANs in the AWMACA shall adopt the timing parameters and synchronize its clock with the AWMACA. џўAdd sentence:Additionally, in an environment where there are multiple WLANs in the same coverage area the clocks of all WLANs are synchronized. џўRe-word sentence:These two parameters are programmable over the WLAN and can be allowed to change dynamically according to the load of the two wireless systems. џўDelete all references to it in the Recommended PracticeџўChange ""(and hence link loss) is constant."" to ""(and hence link loss) is assumed constant.""SB ў Z Ж  k Щ % ~ —ѓMЉL—ю<“эDВ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351š"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.16џў12-15E|@ы@ XOŽŒŠŠ~rpig`^MM= пП™"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.27џў35-40EI@ XO‚€~~~rpig`^MM= пŸ˜"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.2732EB@ XO}{{{omig`^MM= пŸ—"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.27џў26-27EЙ@ XO‚€~~~rpig`^MM= пŸ–"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.2725E@ @XO‹‰‡‡{omig`^MM= пП•"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.27џў21-22EЎ@XO‚€~~~rpig`^MM= пŸ”"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.27џў19-23EV@N@XOŽŒŠŠ~rpig`^MM= пП“"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.17џў12-15E|@ы@XOŽŒŠŠ~rpig`^MM= пП’"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.16џў6-10E[@XO}}}qoig`^MM= пŸ‘"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.171E,@XO}{yyymkig`^MM= пŸ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.1654E@@XO}{{{omig`^MM= пŸ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1611Eк@XO}{yyymkge`^MM= пŸŽ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman1џў1.2220E €џўwhat is ""IEEE 802.119 WLAN""?€џўtry IEEE 802.11b WLANXOРОММ™mkge`^MM= пП"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman1џў1.22џў25-27Eэ@XO€~|||pnge`^MM= пŸŒ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman1џў1.2213E[@XO}{yyymkge`^MM= пŸ‹"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman1џў1.127T:@XO{ywwwkige`^MM= пŸŠ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman1џў1.11џў49-54EХ@XO€~|||pnge`^MM= пŸ‰"0џўKline, Davidџўdave_kline2@hp.comџў541-715-7607џўHewlett Packard10џў10.04050TR‡@Ѕ@XO}{yyma]YUOK::, пПˆ"0џўKline, Davidџўdave_kline2@hp.comџў541-715-7607џўHewlett Packard10џў10.14149TRH@а@XO}{yyma]YUOK::, пП‡"0џўKline, Davidџўdave_kline2@hp.comџў541-715-7607џўHewlett Packard10џў10.14146TR>@’@XO}{yyma]YUOK::, пП†"0џўKline, Davidџўdave_kline2@hp.comџў541-715-7607џўHewlett Packard10џў10.1422TR@Ѓ@XO{ywwk_[YUOK::, пПK0џўJohn, Kowalskiџўkowalskj@sharplabs.comџў(360) 817 7520џўSharp Labs4џў4.3.2915TRЅ@9@XO{ywwk_[WUNL@@0пПJ0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies5џў5.11026Ev@a@џўTE-??XO—•“Œ€trnjecL>0џџьLVAL Тz ѓ . A g ы•чXŸ]  a > - <|!сІєg3фc т{Sр} С‰_reword One of the important issues that effects the level of interference is the WLAN automatic data rate scaling. If it is implemented and enabled it is possible for the WPAN interference to cause the WLAN to scale to a lower data rate. At a lower data rate the temporal duration of the WLAџўreword One of the important issues that effects the level of interference is the WLAN automatic data rate scaling. If it is implemented and enabled it is possible for the WPAN interference to cause the WLAN to scale to a lower data rate. At a lower data rate the temporal duration of the WLAN packets is increased. This increase in packet duration can lead to in increase in packet collisions with the interfering WPAN packets. In some implementations, this can lead to yet a further decrease in the WLAN data rate. This can result in the WLAN scaling down its data rate to 1 Mbit/s.џўwhere is the detailed interfence model (place reference in text)џўthe following sentance makes no sense Since the bandwidth of the 802.11b WLAN is 22 MHz, as the WPAN hops around the ISM band 22 of the 79 WPAN channels fall within the WLAN passband.џўThere is a potential packet collision between a WLAN packet and an interfering 802.15.1 packet any time the WPAN hops into the WLAN passband.џўThis line makes no sense- The higher rates are desirable for many applications but the distance of transmission using the higher rates is less than that of the lower rates.џўMost implementations allow either manual or automatic modification of the data rate.џўredo ""The IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link. So there is little chance that the data will be lost. The effect the interference has on the WLAN is that the delivered data throughput decreases and the network latency increases. Depending on the application this may or may not be tolerable.""џўIn section 1 it states the scope of this document is "" 802.11b and 803.15.2"" But on line 11 we state ""For example, both IEEE 802.11b and IEEE 802.15.1"" like the document addressed more than 802.11 and 802.15.2.џўline 5 states ""This document defines several coexistence mechanisms.."" The next sentance states ""This recommended practice defines two classes of coexistence mechanisms"". This is confusing. Are three two classes of several types?џўthe three sentances need and introduction. Or perhaps ""the scope... is"" Bullet 1 ""To ..."" Also note that on page 2 it starts ""The scope of this document..."". Are lines 40-54 really needed?џўPTA can only work if the WPAN device also uses adaptive frequency hopping to avoid interfering with other WLANs in the same location.џўIn order for AWMA to work and to not burden low cost WPAN devices with the need for WLAN radios, the term Alternating Wirless Medium Access Control Area needs to be defined (AWMACA). As such all devices entering into the AWMACA shall adopt the rules of the area. 1. All WPAN master devices must role-switch to a AWMA master in the area. 2. Only piconets with a AWMA master are allowed 3. IBSS networks must adopt the timing parameters and synchronize its clock with the AWMACA. 4. All WLANs in the AWMACA shall adopt the timing parameters and synchronize its clock with the AWMACA. џўAWMA is recommended for high density WLAN/WPAN areas. As such there will be 3 non-overlapping WLANs in the same area.. For AWMA to be effective, all the WLANs need to share the same time sharing parameters and have the same clock timing. A method needs to be developed that allows all the WLANs to coordinate timing.NLVAL „ћ ˆ } ыБp G(и…v ч > Ф u ЂЙ†5Ÿ[кЋ…NжThe document specifies three ""recommended"" approaches. 1- No where does it state if that there is compliance between devices if toџўThe document specifies three ""recommended"" approaches. 1- No where does it state if that there is compliance between devices if tow vendors choose two different approaches 2- If these are recommendations, what happens if a vendor implements a non-standard approach?џўThis is then converted into an effective BER given the number of bits per symbol.џўreword - In addition, by carefully scheduling packet transmission so that the IEEE 802.15.1 devices transmit during hops that are outside the WLAN frequencies and refrain from transmitting while in-band, interference to WLAN systems could be avoided/minimized and at the same time increase the throughput of the IEEE 802.15.1 systems.џўchange Collaborative is defined as a coexistence mechanism where WPAN and WLAN exchange information between one another to minimize mutual interference while Non-Collaborative is defined as a coexistence mechanism where no exchange of information is used between two wireless networks.џўchange Similarly, changes in the behavior of the MAC layer protocol and the associated data traffic distribution could play an important factor in the interference scenario and affect the overall system performance.џўchange impact the performance of higher layer applications and the MAC layer.џўchange The MAC layer models are interfaced to these PHY models,џўremove the word ""respectively"". With respect to what?џўchange IEEE 802.15.1 uses frequency hopping spread spectrum, while IEEE 802.11b is a frequency-static system that uses direct sequence spread spectrum and complementary code keying. The bandwidth of 802.11b is about 22 MHz so of the 79 channels that 802.15.1 hops over, approximately 22 of those channels are subject to interference, depending on signal power levels. 18 The detailed model described later quantifies the level of packet error rate. The 802.11b represents a worse interferer than the 802.11 FH. For data transfer the network throughput would decrease and the network latency would increase, in the presence of 802.11b interference. The packet error rate for SCO link can cause voice quality degradation. Since a frequency hopping system is susceptible not only on the channel it is operating, but also the adjacent channels, the 22 channels susceptible channels could be increase to 24 channels.џўchange So with limited packet error rate the ACL link will have a small decrease in network throughput and a small increase in network latency. However, for delivery of voice IEEE 802.15.1 uses a synchronous connection-oriented (SCO) link. The SCO link does not support automatic repeat request. As a result there will be some perceivable degradation in voice quality over an SCO link in the presence of 802.11 FH interference. The detailed model described later quantifies the level of packet error rate. The 802.11b represents a worse interferer than the 802.11 FH. For data transfer the network throughput would decrease and the network latency would increase, in the presence of 802.11b interference. The packet error rate for SCO link can cause voice quality degradation.џўspecify where the model is located- The detailed model described later quantifies the level of packet error rate.џўchange Both frequency-hopping systems are usually only susceptible to interference on the channel in use and the two adjacent channels.џўredo ""The IEEE 802.11 MAC incorporates automatic repeat request (ARQ) to insure reliable delivery of data across the wireless link. So there is little chance that the data will be lost. The effect the interference has on the WLAN is that the delivered data throughput decreases and the network latency increases. Depending on the application this may or may not be tolerable.""ЋNЊї B ž э : Œ й 1 }м'~ЩO–р9хА"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman10џў10.3.85729T/@XO„‚€€€trnjb^MM= пŸЏ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman10џў10.24235Ec@XO‚€~~~rplhb^MM= пŸЎ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman10џў10.2425EШ@XO€~|||pnlhb^MM= пŸ­"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman10џў10.142џў3-4E†@}@ XO‹‹sqlhb^MM= пПЌ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.4.1.220џў27-28Eo@:@XO’ŽŽ‚vtmi`^MM= пПЋ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.4.1191TR€џўwhat is meant by '79(23)'?XOžœšššqmkg`^MM= пŸЊ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.418џў44-45E‰@G@XOŽŒŠŠ~rpie`^MM= пПЉ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.418џў41-42E”@›@XOŽŒŠŠ~rpie`^MM= пПЈ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.418џў36-37E‚@XO‚€~~~rpie`^MM= пŸЇ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.418џў32-34Eн@р@XOŽŒŠŠ~rpie`^MM= пПІ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman00--TR@ XOzxvvvjfdb`^MM= пŸЅ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman5џў5.3.61436ES@ R@XO‹‰‰}qokg`^MM= пПЄ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.3.19џў8-12EP@ XO}}}qoig`^MM= пŸЃ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.38џў41-43E@ @XOŒŠˆˆ|pnge`^MM= пПЂ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman42џў33-35Eй@Љ@XO‡…ƒƒwkiib`^MM= пЛЁ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.28џў31-32EP@-@XOŒŠˆˆ|pnge`^MM= пП "0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4829џў####EA@9@XOŠˆ††znlfb`^MM= пПŸ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.2825E:@XO}{yyymkge`^MM= пŸž"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.48џў11-19E’@@ XOŽŒŠŠ~rpig`^MM= пП"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.38џў3-7E @ @ XOŒŠˆˆ|pnig`^MM= пПœ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў1.3452Es@XO}{yyymkge`^MM= пŸ›"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman4џў4.1.3751E‰@u@ XO‹‰‡‡{omig`^MM= пПLVAL'Чšё№ ž О # м Ђ % Э e / ч ЮK<п0ч‹Э™kлŒb=а5ъЕ’cChange references fromџўChange references from Bluetooth to 802.15.1.џўChange to ""in a timely manner.""џўAdd explanation for the shape of this distribution.џўFix the formatting for this reference.џўChange ""802.11"" to ""802.11b.""џўChange the formatting for references to figures. This occurs throughout the document.џўRefer to the bands as unlicensed, or license free, 2.4 GHz bands.џўMake sure heading styles are consistent and used appropriately.џў...implies that only asynchronous data....џўuse shall or should instead of mustџўBoth MAC layer techniques involve ......џўNeed a new subclause describing the timing alignment of superframe and clock.џў"Note that the same partition sequence value is assigned to both the master-to-slave slot and the immediately following slave-to-master slot."џўMake a clearer explanation or redo the work?џўNon-Collaborative ""techniques"" or ""mechanisms""џўDelete this clause- in fact, delete the whole section relating to AWMAџўDelete it as it exists. A better method is to have fixed channelization partitioned between the 2 systems as in 10.4џўInclude a comparison of before and after AFH similar to figure 46 and its supporting text.џўExplain more fully how the PCF is affected by a denial at a TX request.џўSince table 20 defines the ""receive"" collision type as ""in-band"", then it makes sense to swap the entries in table 19 so ""receive"" appears in the ""in-band"" location.џўIllustrate how the knowledge of T1 is shared, or explicitly share it in the beacon element.џўEither correct my assumption about what a recommended practice may do, or complete the required coordination with 802.11 to insert this into the standard (possibly under QoS enhancements). (802.15 coordination needed too)џўInsert a functional definition for colocationџўChange scope so that this document provides ""guidelines for all current and future 802.15 standards to ensure interoperability""џўFile the document away as an interesting set of ideas and let the market forces develop appropriate solutions. Giving the document the status of recommended practice at this stage implies we understand the spectrum of solutions and can make a reasonable recommendation; we can't!џўThis will compromise the accuracy of the measurements at each channel.џў12.1.1.1. received signal strength indication (RSSI)џў(a bit map standing for conditions of different channels) will be used to compile a final list of goodџўWhen bad channels are used, dropped packets are retransmitted, yielding large delays.џўThe PTA technique coordinates sharing of the medium on dynamically, based on the traffic load of the two wireless networks.џўThis sampling rate for f d up to 22 MHz is appropriate.џўSoltanian [B14] contains additional results for flat fading channels.џўThe outline of the clause is as follows: subclause 5.4.1 describes the model for IEEE 802.15.1 and sub-clause 5.4.2 describes the model for for 802.11b.џўIn this subclause, the modeling of the physical layers of the IEEE 802.15.1 and IEEE 802.11b (WLAN) systemsare discussed,. Followed an examoination of the bit error rate performances in interference-limited environments.џўGiven the number of bits per symbol, the SER is converted into an effective BER.џўCollaborative is defined as a coexistence mechanism where WPAN and WLAN exchange information r to minimize mutual interference. Non-Collaborative is defined as a coexistence mechanism where no exchange of information between two wireless networks occur.џўto Changes in the behavior of the MAC layer protocol and the associated data traffic distribution impact the interference scenario and the overall system performance.џўto impact the performance of higher layers.џўto-The MAC layer models interface to these PHY models,фLVAL#Ё „   Ч d 5 ѕ П Š  Ё oџeœ@К”OЙg$ь"0џўChindapol, AikџўaiThe draft consists of a number of ideas supported by detailed simulations. Most of the ideas will never be implemented in practice (particularly the collaboratiџўThe draft consists of a number of ideas supported by detailed simulations. Most of the ideas will never be implemented in practice (particularly the collaborative mechanisms and the mechanisms that require communictations between entities) and it is not even clear that the simulations are valid given their limited scopeџўThis will, however, compromise the accuracy of the measurements at each channel.џўif you are offline, how can you collect anything? ""The channel classification can be performed by blocks, during the connection state or offline.""џўThis paragraphs repeats the first paragraph. It should be deleted.џўor profile for BER (Bit Error Rate).џўdon't all packets have access codes and headers? ""These packets (during connection) contain at least an access code and a header.""џўany time slot or odd time slots? in ""any receiving time slot (i.e., each odd time slot)""џўyou state ""failure to synchronize the access code (or access code correlator fails)"" in line 13. In 21 you only use ""if the access code correlator fails,"". Does line 21 have an incomplete list?џўthe term ""RSSI has been low the error(s) nature is propagation effects"" and ""RSSI has been high the error(s) nature is interference"" makes no sense? in For example, if the packet has not been decoded successfully and RSSI has been low the error(s) nature is propagation effects. On the other hand if the packet has not been decoded successfully but RSSI has been high the error(s) nature is interference.џў(usually a bit map standing for conditions of different channels) will be used to compile a final list of goodџўrun on sentance- ""Since there may be vendor-specific variations and even implementations besides the examples described here, to qualify and accept a channel classification implementation should call for an objective criterion, and even a testing pro-cedure, which are beyond the scope of this clause.""џўNote that, when bad channels are used, packets are dropped and have to be retransmitted, which yields large delays.џўthe values in ""error rate is ~ 24% for DM5 and DM3, and 19% for and DM1 packets,"" are not supported in figure 48џўfigure 48 legand states ""wo"" it should be ""w/o""џўfigure 42 has a legond of 8 items, but only 7 curvesџўtitle in figures 39 and 40 have extra period after ""nulling""џўis this a recommended practice or a standard?џўChange the double arrow to two inward pointing arrows. I thought the double arrow was a diamond.џўthe word ""dynamically"" is an adverb. What is it modifying? ""The PTA technique however coordinates sharing of the medium on dynamically, based on the traffic load of the two wireless networks.""џў The PTA technique however coordinates sharing of the medium on dynamically, based on the traffic load of the two wireless networks.џўThis sampling rate is appropriate for f d up to 22 MHz. A uniform random delay t d = [0,T) and a random phaseџўSome of the text and the figures have been taken from Soltanian [B14], which also contains additional results for flat fading channels.џў The outline of the clause is as follows: subclause 5.4.1 describes the model for IEEE 802.15.1, while sub-clause 5.4.2 does the same for 802.11b.џўdelete ""The resulting performance curves are quite accurate, but they are obtained at the expense of significant computation.""џў In this subclause, the modeling of the physical layers of the IEEE 802.15.1 and IEEE 802.11b (WLAN) sys-tems are discussed, and then their bit error rate performances in interference-limited environments are exam-ined.;QЄћ R ™ э 6 n Р  fЙм,ƒСeЁѕ@uЦ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco1џў1.2213E€џўWhat is a ""project""? €џўClarifyXOЄЂ  ‹gea_ZXQA1 џПХ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco1џў1.1149TRЧ@! €џўClarifyXOŽŒŠŠuiea_ZXQA1 џПФ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco1џў1.1149TR@!ƒ@XO…ƒuiea_ZXQA1 џПУ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco1џў1.1149EM@!€џўAdd introduction to listXO›™™sgea_ZXQA1 џПТ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco00TRC@@XO|zxxl`\\\ZXQA1 џЙС"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.2.47319ER@H@ XO’ŽŽ‚vtplb^MM= пПР"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.2.3739E€џўremove ""(say 0.55)""XO›™———trplb^MM= пŸП"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.2721T–@XO‚€~~~rpnjb^MM= пŸО"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.271џў33-35EE@XO‰‡………ywplb^MM= пŸН"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.271џў30-31E&@!€џўor BER (Bit Error Rate)profile XOЖДВВ…ywplb^MM= пПМ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.27120T†@XO†„‚‚‚vtplb^MM= пŸЛ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.27119T\@XO†„‚‚‚vtplb^MM= пŸК"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.27121TЩ@XO†„‚‚‚vtplb^MM= пŸЙ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.171џў6-8Eš@XO‡…ƒƒƒwuplb^MM= пŸИ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.1.17047E€џў12.1.1.1 RSSI6@ XOЁŸ‘vtplb^MM= пПЗ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.1.17041Ep@h@ XOŽŒŒ€trnjb^MM= пПЖ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman12џў12.170џў30-33E2@XO…ƒuslhb^MM= пŸЕ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman11џў11.3.169џў9-10Eu@ X@ XO’ŽŽ‚vtnjb^MM= пПД"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman11џў11.3.1691Tt@ XO‚€~~~rpnjb^MM= пŸГ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman11џў11.36820E5@ XO‚€~~~rplhb^MM= пŸВ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman10џў10.4.261џў3-17T6@ XO†„‚‚‚vtnjb^MM= пŸБ"0џўchickinsky, alanџўachickinsky@northropgrumman.comџў70363383008554џўnorthropgrumman10џў10.4џў58-59џў42-17E@@ XOˆ†„„„xvohb^MM= пŸ LVALГ™в Š D  х ў { a Z#io4фŸ-у† •"ъbTWPAN ...(WPAN should be sub-scripted). The combined duration of tџўTWPAN ...(WPAN should be sub-scripted). The combined duration of these two subintervals must equal... (must is a depricated IEEE word)џўThe two MAC layer techniques both involve.... (reword)џўTable 19 Receive-Receive in-band entry should be Receive collision, while out-of-band entry should be None entry.џўCurrently superframe is periodic and we have to define its boundary with respect to some reference signal (i.e. CLK).џўThe sentence is not cleared. "Note that the same partition sequence value is assigned to both the master and the slave."џўThe result in figure 21 is quite counter-intuitive when compared with the PER in figure 20.џў802.15-2001 should be 802.15-2002џўReference {Blue99} not clear/correct.џўFigure text smaller that that allowed in IEEE Style Guide (applies throughout) Figures 9, 10, 11, 12, 13, 14, 15џўFigure 1--- (remove/fix the long dash) applies throughout document.џўSubtitle for 4.3.1 and 4.3.2 Non-Collaborative and Collaborative ""proposals""џўHere's another deficiency with AWMA: the use of a CTS would only silence the medium for 3.2767ms. Thus it would be effectively unusable to signal the end of a WLAN period, assuming a beacon interval of approximately 100ms, unless one wanted to limit the 802.15.1 system to use less than 3% of the available time.џўTo expand on other comments about AWMA, in this clause, a change is required to 802.11, beyond, I believe the PAR of 802.15.2. Furthermore this change would have to be dealt with in light of changes being made now in 802.11h, 802.11e, and 802.11i.џўAWMA will not work for legacy stations, will not provide QoS support for 802.11e, and will interfere with timers for legacy equipment. It may also have problems with overlapping BSSs.џўGreat research, information and proposals. Good job.џўThe minimum number of frequencies permitted by the FCC is something on the order of 72 or 76 hops of the total 80 available. Does eliminating 3 to 7 hops do much to enhance cooperation between technologies? The importance of the AFH technique is not apparent.џўTable 24 shows PCF reacting to denied TX requests by waiting a PIFS time before resuming operation. I don't understand if this is an additional PIFS time, or a PIFS instead of a SIFS, or something else. I read this to mean that the PCF is unaffected by a denial of a TX request.џўTable 19 appears to swap ""None"" and ""Receive"" in the ""in-band"" and ""out-of-band"" locations of ""receive"" vs ""receive"".џўThere is insufficient information in the beacon element to determine the start of the WPAN interval. The value of T1 is required and does not explicitly appear. There is a mention of shared knowledge of T1, but I can't see how.џўTo the best of my knowledge, a recommended practice is not permitted to directly make changes to a standard. A new beacon element for 802.11 violates my assumption. The description of AFH later in the document attempts to modify 802.15, which is also beyond the license of a recommended practice.џў""meter"" is spelt ""metre"", even in US English!џў0.5 metres appears arbitrary; on what basis is this distance chosen?џўLine 3 claims 2Mb/s is included; line 7 claims it is not. Which is it?џўThe scope is confusing; the first paragraph appears to suggest a wide scope including all 802.15 now and into the future. The second paragraph limits the scope to just current 802.11h. Which is it?џўThe scope includes ""to suggest modifications to other IEEE 802.15 standard(s) to ..."" Why does this practice ""suggest modifications"" to other 802.15 standards? Wouldn't it be more sensible to actually change the standards themselves rather than making it a two step process.џўThe first paragraph is a list (or non sentences) that needs an introductionšHwЩ  J  М љ 4 qЛюKЂэ9™С!|вY  Y ў Y ў Y ў Y  ў Y U0џўMaa, Yeong-Changџўycmaa@inprocomm.comџў+886-3-5165106 ext 201џўInProComm, Inc.9џў9.1361T]@!.@XOƒsgec_ZXGG/пП_"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc10џў10.14022E#@!XO~|zzznlhd^Z??1 пŸ^"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc6џў6.0298E'@!XOywuuuigea\Z??1 пŸ]"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc5џўFigure 925џў11-28Er@!"€џўScale to match that of Figure 2.XOБЏ­­sqjf\Z??1 пП\"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc5џў5.1950EE@!XOywuuuigca\Z??1 пŸ["0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc4џў4.3.1, 4.3.2џў8-9EP@!4@XO‹‰‰}qooj\Z??1 пЛT0џўJohn, Kowalskiџўkowalskj@sharplabs.comџў(360) 817 7520џўSharp Labs10џў10.2.45021TR;@!€џўRemove AWMA.XOŽŒŠŠpd`\XPL@@0пПS0џўJohn, Kowalskiџўkowalskj@sharplabs.comџў(360) 817 7520џўSharp Labs10џў10.2.2.64729TRњ@ !H@XO‚€~~rfb^ZPL@@0пПR0џўJohn, Kowalskiџўkowalskj@sharplabs.comџў(360) 817 7520џўSharp Labs10џў10.1411TRК@ !v@XO|zxxl`\ZVPL@@0пПZ"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc1џў1.2221E€џўIEEE 802.119 WLAN€џў802.11b-1999XOІЄЂЂˆigca\Z??1 пПQ0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies00E7@ !џўTE-Refuse complimentXO‹uuigggecL>0џйP0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies12џў12.3.38450T@ !\@џўTE-??XOœš˜‘…ywsogcL>0џџO0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies10џў10.3.55511TR@ !I@џўTE-??XOžœš“‡{wsogcL>0џџN0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies10џў10.3.15112Eƒ@!Џ@џўTE-??XOœš˜‘…ywsogcL>0џџM0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies10џў10.2.34849TRч@!]@џўTE-??XOžœš“‡{wsogcL>0џџL0џўSpiess, GaryџўGary.Spiess@Intermec.comџў319 369 3580џў319 310 4425џўIntermec Technologies10џў10.2.2.6.14733TR,@!р@џўTE-??XOЂ ž—‹{wsgcL>0џџЫ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.1.6327E€џў""data"" should be ""Data""€џўFixXOЇЅЃЃ’igcaZXQA1 џПЪ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.1.4323E3@!€џўFixXOŠˆ††uigcaZXQA1 џПЩ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.1.4323TRF@!/@XO‡…ƒƒwkgcaZXQA1 џПШ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco1џў1.2220E"€џў""802.119"" should be ""802.11""€џўFixXOЊЈІІ•gea_ZXQA1 џПЧ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco1џў1.12џў3 & 7TRH@! €џўClarifyXO‘xlha_ZXQA1 џПЁkЛ ё @  ш ' €Џ etЯuж:•зo"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim4џў4.1.1710E#@ $€џўChange to ""affects""XO—•““pdb^\USK=/ џПn"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim4џў4.1612EŽ@ $C@ XO~|zznb`\ZUSK=/ џПm"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim00Eo@ $A@XOusqqeYWWWUSK=/ џЙlџў Kwang-Cheng Chenџў kc@inprocomm.comџў+886-3-5165106 ext 668џў InProComm, Inc.1џў1.01џў39-45EЪ@ $XOxvttthf_]XVDD,нŸk"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc12џў12.3.38441E1@$XO€~|||pnjf^Z??1 пŸj"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc12џў12.2.17819E2@$,@XOŒŠˆˆ|pnjf^Z??1 пПi"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc12џў12.2.1775E.@$XO~|zzznljf^Z??1 пŸh"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc12џў12.1.2.5749E€џўInstead of sending packet... €џўInstead of sending a packet...XOЪШЦЦšpnlh^Z??1 пПg"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc12џў12.1.2.272E=@$XO~|zzznllh^Z??1 п›f"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc12џў12.17018E0@$XO~|zzznlhd^Z??1 пŸe"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc11џў11.3.1697EB@$ €џў...policy leads to a delay...?XOЊЈІІznljf^Z??1 пПd"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc11џў11.2.16425Ea@$XO€~|||pnjf^Z??1 пŸc"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc10џўFigure 4363џў12-43E7@$€џўredrawXOš˜––‚vtmi^Z??1 пПb"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc10џў10.2.24328E’@$XO€~|||pnjf^Z??1 пŸa"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc10џў10.24217Eˆ@!%@XOŠˆ††znlhd^Z??1 пП`"0џўThrasher, Jerryџўthrasher@lexmark.comџў859-825-4056џўLexmark International Inc10џў10.04032E8@!*@XOŠˆ††znlhd^Z??1 пПY0џўMaa, Yeong-Changџўycmaa@inprocomm.comџў+886-3-5165106 ext 201џўInProComm, Inc.10џў10.3.1511Es@!€џўCorrect them accordingly.XOЃЁŸŸxljhd\XGG/пПX0џўMaa, Yeong-Changџўycmaa@inprocomm.comџў+886-3-5165106 ext 201џўInProComm, Inc.12џў12.27425Tw@!O@џўTE-Refuse The information is defined in the IEEE 802.15.1, if it were present here, it would lead to confusion on whether this Recommendation is redfining it. Since this is a Recommended pratice for IEEE 802.15.1 and IEEE 802.11b, it is assumed, and alsoXO‰‡…„xljfb\XGG/пџW0џўMaa, Yeong-Changџўycmaa@inprocomm.comџў+886-3-5165106 ext 201џўInProComm, Inc.12џў12.2.17850Ez@!@XOŠˆ††znlhd\XGG/пПV0џўMaa, Yeong-Changџўycmaa@inprocomm.comџў+886-3-5165106 ext 201џўInProComm, Inc.12џў12.2.17815E€џўTd and Ts is not defined.€џўAdd their definitions.XOНЛЙЙ•nlhd\XGG/пПLVAL%n7ж”d'љ Ч – Ь ] Я Ќ † ^ " iB р"дЊoњЖ…2Чž•^ ъА\Need to consider the impact of equalizerџўNeed to consider the impact of equalizer for the coexistence PHY model simulation.џўShows IEEE 802.15.1 (Draft 1, July 2001 Sponsor Ballot).џўText currently reads IEEE 802.119џўT1 is also required in order to do an accurate calculation of the two periods.џўT1 could possibly be better expressed in 802.11 TU's.џўThe definition of coexistence seems to (partly) overlap with interoperability. Do we want to strictly divide between the two?џўThis high-rate PHY is often referred to as IEEE802.11b. It is not  often referred to but was  standardized as IEEE802.11b!џўTypo IEEE802.119 should be IEEE802.11b џўRemove editor s note referring to 2Mbps. 2Mbps is part of 802.11b and therefore this not is incorrect.џўThe equations do not cover all cases, eg when RTS/CTS is sent before a packet/ACKџў""to in increase"" should be ""to an increase""џў""In a communication system, extraneous"" should be ""Extraneous""џўHow is T1 decided? Why the 1-10ms range? Is T1 to be negotiated by the devices or should it be the same within BSS?џўIn Figure 4, there is no curve for the 802.15.1 receiver.џўThe period time ... should be changed toџўSeveral figures(43, 45) refer to Bluetooth throughput, rather than 802.15.1.џў""The foundation for the effectiveness of these types of methods is to be able to figure out the current channel conditions accurately and timely."" Does this mean ""in a timely manner?""џўThe curve for scenario 3 may need some more explanation. It is clear that at short distances the 802.15.1 voice connection is causing severe interference to the WLAN, blocking packets, and increasing latency. However, why would this peak at 1.5 m? Why isn't the effect worse at 0.5m and 1.0m?џўShould the references to ""BT"" be changed to 802.15.1?џўFix ""specifications cite{Bluet99}.""џў""The performance for 802.11 interference"" should be ""The performance for 802.11b interference."" Other work will need to be done to look at 802.11g, 802.11 frequency hopping, etc.џўThe word ""gray"" in ""gray coded"" should be capitalized.џў""Figure 1-."" should be ""Figure 1.""џў""increase"" should be ""increased""џў""effects"" should be ""affects""џў""For example, both IEEE 802.11b and IEEE 802.15.1 operate in the same 2.4 GHz Industrial, Scientific, and Medical (ISM) band."" This may be a minor point, but it is not relevant to refer to the 2.4 GHz band as an ISM band, because the devices to which we refer are not ISM devices. ISM, according to the FCC is ""equipment or appliances designed to generate and use radio frequency (RF) energy to perform some work other than telecommunications."" The ISM band is actually 2400-2500 MHz, while the Part 15 band, the relevant rule section in the US, is 2400-2483.5 MHz. References to ISM bands occur in other places as well, for example Section 12.џўSignificant formatting problems. The headings that appear in the Acrobat menu are completely inappropriate.џўThe overview is not quite consistent with the PAR title. The overview focused on WLAN/WPAN coexistence, while the PAR addresses more general wireless devices operating in unlicensed frequency bands.џўBad grammer in first sentence of 4th paragraph.џўAn ACL only connection implies that only data...џўFigure citation needs fixing....(Figure XXX)џўRefer to ""Master"" as ""The Master"" throughout subclause.џўStrike the word ""two"" in the first sentence.џў...average the schedulaing policy yields to a delay increase....џўIn the example below, the first pair..... (refer to example in Figure 44 by name, not location)џўFigure not readable (also applies to Figure 45 pg 65)џў...values must be sent to each... (search on the word ""must"" and replace with appropriate (either shall or should) especially in Clause 10... @›к 1 Œ Х  t Ш , ќ4oП [Љт9к…"0џўKline, Davidџўdave_kline2@hp.comџў541-715-7607џўHewlett Packard10џў10.458TR‚@(€џўremove section 10.4XOŽŒŠŠi]YYUOK::, пЛ„џўLars Falkџўlars.p.falk@telia.seџў+4640105133џў+46705945555џўTelia Research AB10џў10.242TR @(i@&XOƒsgcc_YUB4'§ЛƒџўShawn Liuџўshawnliu@inprocomm.comџў+886-3-5165106 ext 865џўInProComm, Inc.10џў10.24216Tu@$X@&XO‚€~~rfd`\VRAA)нП‚џўShawn Liuџўshawnliu@inprocomm.comџў+886-3-5165106 ext 865џўInProComm, Inc.5џў5.3.6.81828E;@$€џўAdd the curve for 802.15.1.XO žœœsgea]TRAA)нП"0џўWakeley, Timџўtim_wakeley@hp.comџў916-785-1619џў916-712-1474џўHewlett Packard10џў10.04050TR†@(Ј@&XO‹‰‡‡{okgc]YH:, џП€"0џўWakeley, Timџўtim_wakeley@hp.comџў916-785-1619џў916-712-1474џўHewlett Packard10џў10.14149TRH@(б@&XO‹‰‡‡{okgc]YH:, џП"0џўWakeley, Timџўtim_wakeley@hp.comџў916-785-1619џў916-712-1474џўHewlett Packard10џў10.14146TR=@'”@&XO‹‰‡‡{okgc]YH:, џП~"0џўWakeley, Timџўtim_wakeley@hp.comџў916-785-1619џў916-712-1474џўHewlett Packard10џў10.1422TR@'Ѕ@&XO‰‡……ymigc]YH:, џП}"0џўWakeley, Timџўtim_wakeley@hp.comџў916-785-1619џў916-712-1474џўHewlett Packard10џў10.4588TR€@'€џўremove section 10.4XOžœššymigc]YH:, џП|џўShawn Liuџўshawnliu@inprocomm.comџў+886-3-5165106 ext 865џў InProComm, Inc.3џў3.1.1441E*@$€џўThe period of time & џўTE-AgreeXOЁŸ“oca_]USAA)нџ{џўBobby Joseџўbobby@ieee.orgџў916 9618977џў916 9618977NA1џў1.1147TRР@'’@&XOmkii]QMIGB@</"§Пz"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim00T0@'d@&XOusqqeYWWWUSK=/ џЙy"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim00E"@')@&XOusqqeYWWWUSK=/ џЙx"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim11џў11.1.26343EN@$/@&XO…ƒuigc_WSK=/ џПw"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim11џў11.06136EО@$#@%XOƒsgea]WSK=/ џПv"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim9џў9.13618T)@$5@$XO€~||pdb^ZUSK=/ џПu"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim9џў9.03311E9@$ €џўChange references to 802.15.1.XO žœœpdb^ZUSK=/ џПt"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim6џў6.0298E'@$(@#XO~|zznb`^ZUSK=/ џПs"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim5џў5.4.42832EЙ@$#@"XO‚€~~rfd`\USK=/ џПr"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim5џў5.3.6.31618E<@$€џўCapitalize ""gray"".XOš˜––thfb^USK=/ џПq"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim5џў5.1950E(@$X@!XO~|zznb`\ZUSK=/ џПp"0џўChinitz, LeighџўLChinitz@Proxim.Comџў781-772-1317џў240-460-3257џўProxim4џў4.1.4816E&@ $€џўChange to ""increased""XO™—••pdb^\USK=/ џПСLVALзsс<Ј з / з n 5 о Л ~  Г)ё€€@ It is not possible to change, or add to the 802.11 MAC from this document (I believe). Redefine this coexistence mechanism to use the existing MAC and define any new functionality separately. Maybe it is OK to say that implementations following the recommended practice have a view џўIt is not possible to change, or add to the 802.11 MAC from this document (I believe). Redefine this coexistence mechanism to use the existing MAC and define any new functionality separately. Maybe it is OK to say that implementations following the recommended practice have a view of the internal state of the 802.11 MAC? Even if MLME additions are allowed, there is no need for new primitives. This interface would be better done using MLME-GET/SET on the new MIB attributes defined (with the addition that it would be nice to have a capability MIB attribute too).џўThis coexistence mechanism seems to be very confused. Either remove it, or rewrite it to be (a) self-consistent and (b) consistent with a recommended practice. Does it use a side channel, or new elements for parameter communication? Are the parameteters set by the AP in an infrastructure BSS? Are they set by the STA that starts an IBSS? Do other IBSS STAs inherit the values when they join?џўI don t believe that modifications to the 802.11 MAC are permitted within the scope of a 802.15 recommended practice. Therefore, either this has to be a new 802.11 standard, or the functionality has to be built on top of the existing MAC without modification (like 802.11 TGh has). Maybe it would be possible to still have this coexistence mechanism by assuming that implementations following the recommended practice have a view of the internal state of the MAC but surely new elements, primitives and the like are out. Even if this view is not the case, there does seem to be new on-air signalling!џўConsider dividing the document into a recommended practice body and informative simulation/analysis annexes.џўCorrect introductory text, or remove PCF behaviour in PTA. џўRemove AWMA recommended practice.џўRemove the recommended practice of using spectral excision for PHY layer coexistence.џўAt the very least remove all the ""why"" to an appendixџўClarify how the collaborative methods in 10.2 and 10.3 will work in an 802.11 QoS enhanced environment.џўPlease provide the rationale for T1's range, and how it will be decided or negotiated.џўAdd sentence: The PTA technique only works well if the WPAN device also uses adaptive frequency hopping to avoid interfering with other WLANs in the same location. џўAdd sentence: Alternating Wirless Medium Access Control Area (AWMACA). All devices entering into the AWMACA shall adopt the rules of the area. 1. All WPAN master devices must role-switch to a AWMA master in the area. 2. Only piconets with a AWMA master are allowed 3. IBSS networks must adopt the timing parameters and synchronize its clock with the AWMACA. 4. All WLANs in the AWMACA shall adopt the timing parameters and synchronize its clock with the AWMACA. џўAdd sentence: Additionally, in an environment where there are multiple WLANs in the same coverage area the clocks of all WLANs are synchronized. џўRe-word sentence: These two parameters are programmable over the WLAN and can be allowed to change dynamically according to the load of the two wireless systems. џўLiason with 802.11 TGe. Add text to address the issue of 802.11g, perhaps based on studies described in 01061r0g-Coexistence_of_BT_with_80211g.џўAdd some discussion in section 10 of the effect on user throughput of these mitigation techniques.џўMake the recommendations more specific.мLVALо Ў юnZЯDєаŒ,Џ‡  Ѓ  } j ѓ р Э К Ї 0  ї € m Z G а Н Њ 3 –ƒ љцo\IвПЌ5"˜…rћше^K8СЎ›$It is not clear how the spectrum factor values have been derџўIt is not clear how the spectrum factor values have been derived. An informative reference would be useful to the reader.џўIEEE 802.11b is mis-spelled as 802.119џўIt is said to be a complex baseband model. But the equations in the subclauses sometimes are presented in a passband form.џўThere should be no difference betweem spectrum factors of Barker mode and CCK mode in Table 4.џўThe definition of frequency offset in Table 3 should be clarified.џўorder 11 is already defined in 11eџўorder 11 is already defined in 11eџўlines after figure number, i.e. figure 34-џўIt would be nice to have the OPNET MAC model as appendix.џўIt would be nice to have source code for the PHY coexistence model as AppendixџўShould use BT hopping sequence instead of random sequence in MAC OpNet modelџўAWMA is recommended for high density WLAN/WPAN area. As such there will be 3 non-overlapping WLANs in the same area.. For AWMA to be effective, all the WLANs need to share the same time sharing parameters and have the same clock timing. A method needs to be developed that allows all the WLANs to coordinate timing.џўAWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.џўDeterministic spectral excision is a poor recommended practice. 1. WLAN devices still interfere with WPAN deviced 2. WPAN devices still interference with other WLAN devices unless those device have scatternet capable WPAN receivers 3. WPAN device needs to be scatternet capable 4. Overlapping piconets will transmit simultaneously on different WPAN channels within the WLAN channel џўThe scope of 802.15.2 D05 is limited to coexistance of 802.11b-1999 and 802.15.1. There is need for information on 802.11g performance in the presence of a 802.15.1 intereference. The co-existance mechanisms should address the specific case when 802.11e is the mac. Although these standards are in draft ballot stage, they are reasonably complete enough to address coexistance issues, P15.2 should address both g and e to be useful.џўIn all of the coexistence simulation modeling, for example in section 9, there are many figures showing the effect on throughput and delay of various interference scenarios. In section 10, though, which discusses collaborative mitigation techniques there does not appear to be any discussion of the effect that these techniques will have on throughput. For example, AWMA in its simplest implementation would allow 50% of the time for WLAN transmissions, and 50% of the time for 802.11 transmissions. This should reduce the effective throughput by approximatly 50%. Even the PTA, which operates more dynamically, will reduce the throughput of each of the systems according to the load being offered by the other system. Since this is recommended practices document, such an effect should be explicitely stated.џўThere are very few explicit ""recommendation"" sections. (An exception would be section 10.1.) That being the case, should all statements in the document be taken as recommendations? For example, in section 5.4.3 it says ""This result is not surprising, since the CCK provides a higher bit rate but occupies the same 22 MHz bandwidth, thereby having less of a coding gain. Generally, the receivers used for both 1 Mbit/s and 11 Mbit/s are fairly simple, and improved performance can most likely be obtained using more sophisticated signal processing. This fact is especially true for the 11 Mbit/s CCK system."" Is it, then, a recommendation from IEEE that improved signal processing be used in 11 Mbps 802.11 DS devices in order to reduce their sensitivity to interference from 802.15.1 devices?&LVALИ 2   е P Тв$0ƒФЯTЯCЛTwŒШ`d ZјЧ%(@ZчBЛTwŒШcР ZјЧThis document only applies to WPANs and 802.11-1999, џўThis document only applies to WPANs and 802.11-1999, not to any other wireless technologies.џўIt appears to me that the AWMA technique can be easily extended to PCF/HCF.џўAs the recommendation suggests additions of the Information elements, this needs to be added into 802.11 standard so that non-802.15.2 devices can still be conformantџўThis document would be easier for a new reader if the analytical work that is the background to the actual recommended practice was moved to an annex (this applies to sections 5 through 8).џўThis introductory clause says that the scope of this document is limited to DCF and does not address PCF. However, Table 24 in 10.3.5 addresses how PTA functions for PCF.џўHow is AWMA coordinated with probable enhancements of fair-queuing in WLAN, such as HCF and EDCF, where time division of the beacon interval is used for QOS reasons. Have the mechanisms of HCF been studied when used in conjunction with AWMA?џўUsing a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will work if the interference location is static through the entire 802.11b packet (which it is not since it hops 160 times in 100ms). Otherwise, changing the location of the notch filter as the 802.15.1 interference hops will create what looks like a time-varying channel response to the 802.11b packet. This type of channel behavior would necessitate the use of an advanced equalization method.џўWhy wouldn't you want to use the CTS to itself technique to stop all transmission during the WPAN period? It seems strange that other AP's on the same channel are alllowed to transmitџўThe clause does not make clear in what period the CTS is transmitted. If it is sent in the WLAN period there will be cases in which it would not be sent at all. If it is sent in the WPAN period the 802.15.1 master had better know about itџўPresumably the recommended practice is more restrictive than just ""IEEE 802.11 WLANS""; it should be 802.11 WLANS operating in 2.4GHz bandsџўfhop is claimed to be a frequency and yet the definition seems top refer to channel numbers. Is is a frequency or a channel number?џўThe document contains too much ""why"" (with very detailed supporting equations and simulations) rather than a concise statement of the problem and a recommended solution (or solutions)џўDeterministic spectral excision is a poor recommended practice. 1. WLAN devices still interfere with WPAN devices 2. WPAN devices still interference with other WLAN devices unless those devices have scatternet capable WPAN receivers 3. WPAN devices needs to be scatternet capable 4. Overlapping piconets will transmit simultaneously on different WPAN channels within the WLAN channel џўIt is not clear to me how the collaborative methods in 10.2 and 10.3 will work in a QoS enhanced 802.11 environment. Since it is likely that the collaborative methods will be implemented at the same time as the 802.11 QoS enhancements more than the 802.11 legacy case should be treated.џўPTA can only work if the WPAN device also uses apative frequency hopping to avoid interfering with other WLANs in the same location.џўIn order for AWMA to work and to not burden low cost WPAN devices with the need for WLAN radios, the term Alternating Wirless Medium Access Control Area needs to be defined (AWMACA). As such all devices entering into the AWMACA shall adopt the rules of the area. 1. All WPAN master devices must role-switch to a AWMA master in the area. 2. Only piconets with a AWMA master are allowed 3. IBSS networks must adopt the timing parameters and synchronize its clock with the AWMACA. 4. All WLANs in the AWMACA shall adopt the timing parameters and synchronize its clock with the AWMACA. ’2о V ‘ р / y СTЃ№OГќ`НqЬЃ\Э К Ї 0 /ъЅс"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine10џў10.2.35017TRN@*?@+XO~|zznb^ZVNJB11 яПр"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine10џў10.2.2.14340TRн@*8@&XO€~||pd`\XNJB11 яПп"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine10џў10.2.24330TR1@*Š@&XO~|zznb^ZVNJB11 яПо"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine10џў10.04028TRѕ@*]@&XO|zxxl`\XTNJB11 яПн"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine5џў5.0936EП@ (n@ &XOusqqeYWSQLJB11 яПм"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine4џў4.1636EŠ@$€џўUse  standardized .XOŽŒŒeYWSQLJB11 яПл"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine4џў4.1626T­@ (=@ &XOusqqeYWSQLJB11 яПк"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine1џў1.1221E)@$€џўFixXOzxvveYWSQLJB11 яПй"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine1џў1.127Ek@$€џўRemove editor s noteXOŒŠˆˆcWUSQLJB11 яПиџўVK Jonesџўvkjones@woodsidenet.comџў650.475.1915џў650.475.1915џўWoodside Networks10џў10.24212TRє@ (#@ &XOŠˆ††znjfb\XE7)§ПзџўVK Jonesџўvkjones@woodsidenet.comџў650.475.1915џў650.475.1915џўWoodside Networks10џў10.45810TRѕ@ (W@ &XOŠˆ††znjfb\XE7)§Пж"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco10џў10.2.45028TRЙ@( €џўClarifyXO•“‘‘|plhd\XQA1 џПе"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco10џў10.2.450TR№@( €џўClarifyXO‘xlhhd\XQA1 џЛд"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco10џў10.2.3505TRS@$€џўFixXO‹‹znjhd\XQA1 џПг"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco4џў4.1.2738E1@$€џўFixXOŠˆ††uigcaZXQA1 џПв"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco4џў4.1623TRŽ@(€џўFixXOŠˆ††uiea_ZXQA1 џПб"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco4џў4.064E€џў"".."" should be "".""€џўFixXOžœšš‰eca_ZXQA1 џПа"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.3549TR…@( €џўClarifyXOŽŒŠŠuiea_ZXQA1 џПЯ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.1.11345E!€џў""fading"" should be ""Fading""€џўFixXOЌЊЈЈ—jhdbZXQA1 џПЮ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco00TRЛ@(9@ &XO|zxxl`\\\ZXQA1 џЙЭ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.1.8336ED@$€џўFixXOŠˆ††uigcaZXQA1 џПЬ"0џўMyles, Andrewџўandrew.myles@cisco.comџў+61 2 84461010џў+61 418 656587џўCisco3џў3.1.7331E€џў""It is a"" should be ""A""€џўFixXOЇЅЃЃ’igcaZXQA1 џПуLVAL к § Џ 5Фќpс* п < л †  РTable 24, third column (PCF(as CF-pollable STA)): This condition here seems rather artificial. If a STA getџўTable 24, third column (PCF(as CF-pollable STA)): This condition here seems rather artificial. If a STA gets a poll and has a WLAN MPDU to send, would it be still denied access? Am I not understanding this correctly?џўThe proposed control of legacy systems will not work when a legacy device is operating in power save mode and wakes up to transmit a packet.џўThe document lacks a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.џўThe document only addresses 802.11B interference while current standardization in the 2.4 GHz band is covered in the 802.11G annex. The new modulation schemes proposed in 11G need to be taken into account in the analysis on mutual interference and in proposed solutions. Any new development in this band is likely to address 802.11G rather than just 11B. Any investment in collaborative schemes must have applicability for 11G to be of interest.џўThe recommended practice to use a notch filter has the problem that 802.15.1 signals are frequency hopping; this means that the 802.11b receiver would have to change its notch and equalizer if a hop occurs within a packet. It is not clear whether this is possible without fatal transient effects that would kill the 802.11b packet.џўThis says No new on-air signalling is required . However, since we need a new information element for beacon and probe response management frames I don t see how this statement is true. In fact I think new on-air signally is required and this is outside the scope of a recommended practice.џўThe 802.11 MAC does not allow the transmission of a CTS frame in isolation with a specific duration value. This frame exchange sequence and duration setting facility simply do not exist in the current 802.11 MAC. This is one reason why in the IEEE802.11 TGh draft we have defined a new quiet period mechanism (an aside is that even if it did exist the duration is limited to 32Kus). Note that (a) even if this CTS mechanism existed it would be imperfect and (b) the group addressing scheme to involve other APs violates the current rules further. This latter point is due to the fact that CTS is not used in multicast communication.џўFirstly see comments from this author on appropriate scope for an 802.15 recommended practice. Second the 802.11 MAC behaviour around the start and end of the WPAN interval needs to be more precisely defined, for example, do STAs that defer due to a pending WPAN period select a backoff value, increment their retry counters, etc..џўNew 802.11 MLME primitives are outside the scope of this recommended practice. If it is possible to specify this coexistence mechanism without change to the 802.11 MAC then this MIB should be defined as an 802.15.2 MIB.џўTiming values to be distributed through the WLAN network management tool (i.e. outside the scope of this recommended practice). This implies that the element defined is not actually required and that some 802.15.2 MIB is being set by a higher layer protocol. If that is the case why define the element at all (which is outside the scope of a 802.15 recommended practice). I also note that (a) these need to get into STAs before active scanning to avoid getting management frames sent in the WPAN period, and (b) some description of IBSS operation is required.џў No new on-air signalling is required . However, a new information element for beacon and probe response management frames is defined. Sounds like new on-air signalling. This together with new MLME primitives and MIB extensions seems to be defining extensions to the 802.11 MAC. Given this is the case I don t see how this can be a recommended practice since it is defining new protocol elements and modifying the behaviour of the 802.11 MAC - it has to become a new 802.11 standard surely.ъLVAL"Сgv ; | ћ и • f  ј Л  Њ _ ) ь|8єю…Z0к`=ƒC‰S)<Have one or more technical editors review and fix the text. Watch out especially for number mismatches ("one item arџўHave one or more technical editors review and fix the text. Watch out especially for number mismatches ("one item are..."), "effect" when "affect" is meant, and typos in table fields. Aside: Is a "Recommended Practice" a *Standard*?џўChange title word "Other" to 802.11-1999џўRemove the recomended practice of spectral excision.џўRemove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.џўProvide a mechanism that addresses co-existence in PCF and HCFџўRemove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.џўRemove AWMA recommended practice.џўExpand the scope of this set of recommended practices to include .11g now, rather than waiting for some future revision.џўRemove the recommended practice of using spectral excision for PHY layer coexistenceџўRemove PTA recommended practice for now.џўRemove AWMA recommended practice for now.џўClarify how the collaborative methods in 10.2 and 10.3 will work in an 802.11 QoS enhanced environment.џўIt should be defined as the offset between the central frequencies of the transmitter and the receiver. The rows of two types of transmitters should be splitted, and the table of content should be modified according to the above frequency offset definition.џўcoordinate the order number with other task groups, 11e, 11i, 11hџўcoordinate the order number with other task groups, 11e, 11i, 11hџўTake this section out or ask more results to backup its performance: 2,5.5, 11mbps, with equalizer considered.џўChange the hopping sequence in the MAC model to BT sequenceџўRerun simulation to extend the results to more BERs.џўSuggest adding multipath results in the simulated and analytical results.џўWhen the schedule for this LB allows, AFH section should be harmonized with Bluetooth SIG.џўDepending on the progress/schedule of this LB, it may be possible to incorporate changes to harmonize with Bluetooth SIG. If it becomes feasible to do so, changes are recommended.џў Replace with IEEE 802.15.1 Standard (and appropriate date)џўadd sensing function in .15.1 master.џўremove collaborative proposals; focus on non-collaborative proposals.џўWork with 802.11 group to make that addition.џўClarify. If my understanding is correct, remove this restriction.џўAdd this shortcoming to the text.џўInclude a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.џўInclude analysis and simulation material addressing the 802.15 and 802.11G coexistance. Include outcome of those analysis and simulation in proposed schemes for interference reduction.џўRemove the recommended practice of using notch filtering.џўIf there is no solution that can be implemented without these signalling changes then the recommended practice should be dropped and a PAR sough for a new standard.џўState clearly whether interoperability is included in coexistence or not.џўRemove this mechanism as no such facility exists and it overloads the CTS functionality.џўIf I'm incorrect about it being inappropriate for this 802.15 recommended practice to add to, or modify the 802.11 MAC, then specify explicitly the MAC behaviour around the WPAN period, including back-off, IFSs used and retry counter behaviour. See the behaviour of the .11 MAC around dwell boundaries for an example.3[Дr п N  ф  g ™Э/‘рGЎtсRЛq"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments0000E;@'€џўAdd if possible.XO~|zz\PNNNJF33' пЙ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments0000EP@'€џўAdd if possible.XO~|zz\PNNNJF33' пЙ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments10џў10.458 @-p@+XOpnll`TTTPJF33' пГ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments06TN@'=@+XOhfddXLJJJJF33' пИ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments0000Tћ@-6@+XOljhh\PNNNJF33' пЙ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments05џў5.3 & 5.4џў11-28TT@$$K@+XOzxvvj^\\UJF33' пЛџ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments12џў12.069T@-\@+XOrpnnbVTTPJF33' пЛў"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments11џў11.264Tž@-Е@ +XOrpnnbVTTPJF33' пЛ§џўDenis Kuwaharaџўdenis.kuwahara@boeing.comџў425-957-5366џўBoeing2џў2.0248E:@#$=@ +XOrpnnbVTPNIG??1нПќџўDenis Kuwaharaџўdenis.kuwahara@boeing.comџў425-957-5366џўBoeing1џў1.2221E#@"$€џўChange to IEEE 802.11bXOŠˆ††bVTPNIG??1нПћ"0џўXu, Shugongџўsxu@sharplabs.comџў360-834-8672џўSharp Labs of America0000TR@-'@ +XOwussg[WWWSO88* пЙњ"0џўXu, Shugongџўsxu@sharplabs.comџў360-834-8672џўSharp Labs of America0000TRB@-G@ +XOwussg[WWWSO88* пЙљ"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.10џў10.242TRЈ@ (/@ +XOЅЃЁЁ•‰……{wRB2 џЛј"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.10џў10.3.555TRк@ *C@+XOЇЅЃЃ—‹‡‡ƒ{wRB2 џЛёџў Leo Montebanџўmonteban@agere.comџў+31 3060 97526џўAgere Systems10џў10.2.45021T@ *#@+XOzxvvj^\XTLH99)нП№џў Leo Montebanџўmonteban@agere.comџў+31 3060 97526џўAgere Systems10џў10.2.2.6.14740T€џўT1 is essemntial information.€џўAdd T1 as extra field.XOЕГББb`\XLH99)нПяџў Leo Montebanџўmonteban@agere.comџў+31 3060 97526џўAgere Systems10џў10.2.2.14345TQ@!$€џўAdd T1 as parameter.XO’ŽŽl`^ZVLH99)нПюџў Leo Montebanџўmonteban@agere.comџў+31 3060 97526џўAgere Systems10џў10.24247T7@ $€џўExpress T1 in TUXOŠˆ††h\ZVRLH99)нПчџў Leo Montebanџўmonteban@agere.comџў+31 3060 97526џўAgere Systems00TŒ@*@+XOjhffZNLLLJH99)нЙцџў Leo Montebanџўmonteban@agere.comџў+31 3060 97526џўAgere Systems00TRШ@*П@+XOljhh\PLLLJH99)нЙхџўRichard van Neeџўvannee@woodsidenet.comџў+31-346259650џўWoodside Networks10џў10.45810TRM@*;@+XOƒsgc_[UQ>>/нПфџўJonathan Edneyџўjon.edney@ntlworld.comџў+44 1954 20573910џў10.04028TR$@*І@+XOqommaUQMIC???.ПуџўAllen Tsaiџўallen@inprocomm.comџў+886-3-5165106 ext 870џўInProComm, Inc.3џў3.1.23џў16-17E@$K@+XO€~||pdb[YRP??'нПт"0џўBlack, Simonџўsimon@motix.demon.co.ukџў+44 7780 677453џўQosine10џў10.2.45023TRz@*Z@+XO~|zznb^ZVNJB11 яП4LVALО.   §  цЙа$9л`Although not part of the standard, the comment that the IntrџўAlthough not part of the standard, the comment that the Intro is not part of the standard should be complete and correct.џўThis document is a yeoman technical effort, but needs a thorough editorial review and fixes.џўTGg is describing mechanisms to enable coexistence between legacy .11b devices and .11g capable devices. These need to be taken into account in regards to the AWMA recommended practice or the recommended practice needs to be removed.џўGiven that TGg has made significant progress and is likely to be finished soon, it makes much more sense to expand the scope of this document now to include the issues associated with coexistance between 802.15 devices and 802.11g devices. It is highly likely that most if not all future products in the 2.4 GHz WLAN space will be incorporating .11g it is practically irrelevant to speak to coexistence with .11b only devices.џўThe use of a notch filter to remove the interference effects of an 802.15.1 signal from an 802.11b signal will likely not be effective, since the interference location is not static through the entire 802.11b packet (hops 160 times in 100ms). Changing the location of the notch filter as the 802.15.1 interference hops creates what appears to be a time-varying channel response to the 802.11b packet. This type of channel behavior necessitates the use of an advanced equalization method.џўTGg is describing mechanisms to enable coexistence between legacy .11b devices and .11g capable devices. Have the performance impacts and increased complexity of these mechanisms been modeled when used in conjunction with PTA?џўTGg is describing mechanisms to enable coexistence between legacy .11b devices and .11g capable devices. Have the performance impacts and increased complexity of these mechanisms been modeled when used in conjunction with AWMA. A mechanism needs to be defined regarding the prioritization of 802.15, 802.11b legacy and 802.11g.џўIt is not clear to me how the collaborative methods in 10.2 and 10.3 will work in a QoS enhanced 802.11 environment. Since it is likely that the collaborative methods will be implemented at the same time as the 802.11 QoS enhancements more than the 802.11 legacy case should be treated.џўThe specturm factor is not necessarily unity at frequency offset zero. Consider the case of 802.11b tx and 802.15.1 rx, the full tx power occupies a bandwidht of 22MHzm, and only a fraction of it can pass the 1MHz channel filter of 802.15.1.џўTake out Section 10.4: the method is only shown effective for 802.11b 1Mbit/s mode. The impact of equalizer is unknown. Cost of implementing an 802.15.1 receiver to just get the hopping sequence and timing is expensive and hardly feasible due to cost consideration.џўSome of the simulation curves only cover BER down to somewhere between 10-2 and 10-3. Should use BER of at lease 10-4 as the threshold for more useful results, because a BER of 10-2 to 10-3 will yield too high a Packet error rate for pactical usage.џўSection 12 (Adaptive Frequency Hopping) needs to be harmonized with Bluetooth Coexistence group work when schedules from both groups allow.џўSection 11.2 (Packet Scheduling for Improving SCO Links) needs to be harmonized with Bluetooth 1.x Speech Improvement when schedules from both groups allow.џўSince there is no sensing in .15.1 master, how can the proposed collaborative proposal to prevent the .15 device sending in WLAN subintervals?џўIt seems that the Collaborative proposals are creating new system which need some interaction fucntions between .11b and .15.1 system. How many chances these two systems exist in one physical unit, which happens to have such functions? Why bother to create so complicated scheme which will hurt both systems performance?lY›ё 3  а  h Ь  dАjЯћ.=P}Єї"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.10џў10.242TRM@( €џўMake it so.XOВАЎЎ•‰……{wRB2 џЛі"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.10џў10.040E@/ €џўClarifyXOЌЊЈЈ“‡……{wRB2 џЛѕ"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.05џў5.3.313E{@'"€џўProvide an informative referenceXOЦФТТ”ˆ††‚{wRB2 џЛє"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.4џў4.1.2738E€џўMisspelled ""an"" as ""in"" €џўCorrectXOЪШЦЦБˆ†‚€ywRB2 џПѓ"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.04џў4.1628TR–@/@@+XOІЄЂЂ–Š†‚€{wRB2 џПђ"0џўKandala, Srinivasџўsrini@sharplabs.comџў(360) 817-7512џў(360) 907-7318џўSharp Laboratories of America, Inc.01џў1.2221E(@' €џўCorrectXO­ЋЉЉ”ˆ†‚€{wRB2 џП"0џўChoi, Sunghyunџўsunghyun.choi@philips.comџў914-945-6506џўPhilips0000TRz@/К@+XOtrppdXTTTPLCC5 пЙџўFrank Howleyџўfhowley@woodsidenet.comџў650-475-2020џўWoodside Networks10џў10.242џў12-18TRы@ -#@+XOƒsgc\XRN;;-нПџўFrank Howleyџўfhowley@woodsidenet.comџў650-475-2020џўWoodside Networks1џў1.11EЌ@ -z@+XOusqqeYWWUPN;;-нЛџўRolf Devegtџўrolf@woodsidenet.comџў650 475 1913џў650 823 1523џўWoodside Networks10џў10.458џў10-24TRщ@ -V@+XO‹‰‰}qmfb\XE7)§ПџўRolf Devegtџўrolf@woodsidenet.comџў650 475 1913џў650 823 1523џўWoodside Networks10џў10.350џў35-39TRф@ -*@+XO‹‰‰}qmfb\XE7)§ПџўRolf Devegtџўrolf@woodsidenet.comџў650 475 1913џў650 823 1523џўWoodside Networks10џў10.242џў12-18TRI@-+@+XO‹‰‰}qmfb\XE7)§ПџўRolf Devegtџўrolf@woodsidenet.comџў650 475 1913џў650 823 1523џўWoodside Networks10џў10.458џў10-24TRXOusqqqqmfb\XE7)§џўLars Falkџўlars.p.falk@telia.seџў+4640105133џў+46705945555џўTelia Research AB10џў10.2 & 10.3TR @-i@+XO†„‚‚vjfffYUB4'§Йџў HungKun Chenџўhkchen@inprocomm.comџў+886-3-5165106 ext 661џўInProComm, Inc.5џў5.418E}@'€џўMake them consistent.XO”’ma__[VTCC+нЛ џў HungKun Chenџўhkchen@inprocomm.comџў+886-3-5165106 ext 661џўInProComm, Inc.5џў5.3.313T`@ '€џўCombine the two rows.XO–”’’ocaa]VTCC+нЛ џў HungKun Chenџўhkchen@inprocomm.comџў+886-3-5165106 ext 661џўInProComm, Inc.5џў5.3.313TD@ '@+XO}{{ocaa]VTCC+нЛ џў HungKun Chenџўhkchen@inprocomm.comџў+886-3-5165106 ext 661џўInProComm, Inc.5џў5.3.313Tї@-€џўCorrect this sentence.XO—•““ocaa]VTCC+нЛ џўAlbert Youngџўayoung@ralinktech.comџў408-725-8070 x 31џўRalink Technology10џў10.2.2.6.348T$@ 'D@+XOƒsgeeaUQ>>+нЛ џўAlbert Youngџўayoung@ralinktech.comџў408-725-8070 x 31џўRalink Technology10џў10.2.2.6.1 Beacon frame format47T$@ 'D@+XO—•““‡{yyuUQ>>+нЛ"0џўJie, Liangџўjliang@ieee.orgџў2144804105џўTexas Instruments0000E,@ '€џўCorrect the typos.XO€~||\PNNNJF33' пЙѓLVAL†№ ы q fнЗ+sQэМ†М’h+This draft is generally well џўThis draft is generally well written and ready for comment.џў802.11 FH is not in the scope of the RP.џў802.11 FH is not in the scope of the RP.џўEditor's note is not consistent with document. 2Mbps is included in 5.3.6.3 and 5.4.3 Figure 10.џўIt is unclear what will happen if there is more than one AP(or perhaps STA) reserving WPAN intervals.џўPDF bookmarks could do with being reduced in number!џўThe Bookmarks in the PDF do not make any sense.џўThe word ""shall"" is not appropriate in a Recommended Practice, especially in the area dealing with service primitives, which is supposed to be infomal anyway.џўThe definition of coexistence is not giving a clear picture as to the impact to the pain it would cause. Currently, the reader could assume that neither system is being impacted in performanceџўThe sentence only refers to a single working group. Because this document is being reviewed by 2 working groups, we need to list both lists. Also the term ""At the time this standard was completed,"" is ambiguous: is that time when the standard is sent to sponsor or when sent to revcom?џўThe bookmarks in the PDF file are incorrectly extracted from the main document. They do not include the headings or subheadings of the document, but rather portions of the body text.џўAWMA will have limited benefit in the presence of overlapping cell. This is because BSS are not coordinated in an ESS. However, clause 10.1 page 41 line 51 recommends using AWMA when there is a high density of users.џўLine 15 is confusing. The sentance fragment ""but also the adjacent channels, the 22 channels susceptible channels could be increase to 24 channels."" needs to be clarified. џўThere is no group known as 802.119. џўTHe Editor's note states that 2 Mbit/s is not included, yet the paragraph just above the statement does include 2 Mbit/s. Which is it?џўInitial Page nees to be checked. When I printed mine, the ""Committe of the IEEE Society"" , "" Abstract:"" and ""Keywords "" were floating in amoungst the text.џўSpectral excision is a sub-optimal method of removing the effects of WPAN devices on WLAN devices. If a device is required to have both WPAN and WLAN receivers, an optimal receiver would make joint decisions given information from both detectors, i.e. searching the entire receive space given knowledge about the two waveforms. Furthermore, if spectral excision is used, more advanced equalization techniques will need to be used in the WLAN reciever at the hop-boundaries due to the time-variation required on the nulling filter. Using a joint detector will obviate the need for a nulling filter or an equalizer.џўThis draft is for a recommended practice, not a (supplementary) standard. However, I find that it changes many MAC operations at least from the 802.11 perspective. For example, AWMA in Clause 10.2 modifies the 802.11 MAC to time share with 802.15.1. The operations to handle the legacy (?) 802.11 stations as described in Clause 10.2.4 are not also compliant with 802.11-1999.џўIt is not clear from the text if PTA is another technique or part of AWMA. Both of them appear to have the requirement of WLAN/802.11 and WPAN/802.15.1 are collocated. Also, is there a reason to distinguish between WLAN and 802.11 as well as WPAN and 802.15.1џўGiven that a modification of PCF (called HCF) would most certainly exist in the future, I think the co-existence mechanism should cover that as wellџўThis draft is for a recommended practice, not a (supplementary) standard. However, I find that it changes many MAC operations at least from the 802.11 perspective. For example, AWMA in Clause 10.2 modifies the 802.11 MAC to time share with 802.15.1. The operations to handle the legacy (?) 802.11 stations as described in Clause 10.2.4 are not also compliant with 802.11-1999.Ѓ]Т Œ ќ l ж > Ѓ  u П9ІdЦcО#~с,џўErik Schylanderџўerik.schylander@philips.comџў+31 40 27 35585џўPhilips0000TRi@2Л@1XOvtrrfZVVVRNEE4нЙ+"0џўSoomro, Amjadџўamjad.soomro@philips.comџў914-945-6319џўPhilips10џў10.2.45020TRc@2К@1XO~|zznb^ZVNJAA3 пП*"0џўOakes, Ivanџўifo@tality.comџў+44 1223 421 025-џўTality (UK) Ltd10џў10.2Tg@/Л@1XOtrppdXVVVPL;9' џЙ)"0џўOakes, Ivanџўifo@tality.comџў+44 1223 421 025-џўTality (UK) Ltd10џў10.2.45628Tž@2e@1XO~|zznb`\XPL;9' џП("0џўOakes, Ivanџўifo@tality.comџў+44 1223 421 025-џўTality (UK) Ltd1џў1.2821E€џўtypo ""802.119""&@ 1XO‰‡……y[YUSNL;9' џП'"0џўOakes, Ivanџўifo@tality.comџў+44 1223 421 025-џўTality (UK) Ltd1џў1.2812E€џўUse of ""project""?8@ 1XOŒŠˆˆ|[YUSNL;9' џП&"0џўOakes, Ivanџўifo@tality.comџў+44 1223 421 025-џўTality (UK) Ltd01џў1.181E<@2Ž@ 1XOwussg[YWUPL;9' џП%"0џўOakes, Ivanџўifo@tality.comџў+44 1223 421 025-џўTality (UK) Ltd00011E6@/€џўSet up boomarks!XO†„‚‚dXVTRPL;9' џП$џўMaarten Hoebenџўmhoeben@intersil.comџў+31-30-2296083џўIntersil10џў10.3TТ@2Ђ@ 1XOnljj^RPPPJF<<,нЙ#џўMaarten Hoebenџўmhoeben@intersil.comџў+31-30-2296083џўIntersil0000E1@/A@ 1XOljhh\PNNNJF<<,нЙ""0џўHayes, Vicџўvichayes@agere.comџў+31 30 609 7528џў+31 30 609 7498џўAgere Systems10џў10.2.14336TЂ@ /!€џўReplace ""shall"" by ""should""XOЎЌЊЊ}qokg_[L;* џП!"0џўHayes, Vicџўvichayes@agere.comџў+31 30 609 7528џў+31 30 609 7498џўAgere Systems03џў3.1.2316TТ@ /к@1XOŠˆ††znlhf_[L;* џП "0џўHayes, Vicџўvichayes@agere.comџў+31 30 609 7528џў+31 30 609 7498џўAgere Systems00џўIntroduction10E"@ /ž@1XO‹‹sqmm_[L;* џНџўTim Godfreyџўtgodfrey@intersil.comџў913-664-2544џўIntersil0000EИ@ /N@1XOhfddXLJJJFB88*нЙџўDave Halaszџўdhala@cisco.comџў330-664-7389џўCisco Systems, Inc.10џў10.2џў41-50TRк@ /%@1XOxvtth\XXQKG22$нЛ"0џўRosdahl, Jonџўjrosdahl@ieee.orgџў801-617-2508џўMicro Linear04џў1.4815EВ@/‚@1XOtrppdXVRPKG99+ пП"0џўRosdahl, Jonџўjrosdahl@ieee.orgџў801-617-2508џўMicro Linear012221E&@/4@1XOqommaUSOMKG99+ пП"0џўRosdahl, Jonџўjrosdahl@ieee.orgџў801-617-2508џўMicro Linear01127T‰@/o@1XOomkk_SQOMKG99+ пП"0џўRosdahl, Jonџўjrosdahl@ieee.orgџў801-617-2508џўMicro Linear00E{@-Y@1XOigeeYMKKKKG99+ пИ"0џўRosdahl, Jonџўjrosdahl@ieee.orgџў801-617-2508џўMicro Linear00EЄ@/%@1XOigeeYMKKKKG99+ пИџўDavid Hunterџўhunter@timefactor.comџў 805 687 2885џў TimeFactor0000E^@ -э@!+XOmkii]QOOOKG::+нЙџўDavid Hunterџўhunter@timefactor.comџў 805 687 2885џў TimeFactorџўDocument TitleI1+E{@(*@ +XO{ywwk_]YWWG::+нОџўJames Gardnerџўjamesgardner@woodsidenet.comџўWoodside Networks10џў10.458TRg@/6@+XOtrppdXTTPJF333ЭЛџўRitter, Bennoџўbenno.ritter@philips.comџў408-474-5116џў408-768-2411џўPhilips0000TRz@/К@+XO|zxxl`\\\XTK=/§ЙиLVAL"л‚п]8ъ L r 1   Щ Ѓ > ƒ ЩфНiЅоFф2ыАo)м•*Change the sentence to state ""802.15.2 contains sysџўChange the sentence to state ""802.15.2 contains system models of 802.11b 1, 2, 5.5, and 11 Mbps modes.""џўPlease change the section head of 4.3.2 to ""collaborative methods.""џўPlease change the section heading of 4.3.1 to ""non-collaborative methods""џўadd (BER=0) to Upper limit column and (BER=.5) to Lower limit columnџўreplace with differential Replace with 'much more likely than'џўremove 'or the disturbance caused by the undesired power'џўNote that most of the analysis and simulations are for 1 and 11 Mbps.џўDevelop a revision of this document to include the impact of the newer standards under 802 (mentioned above) and suggest recommended practices and changes to those standards.џўAdd an analysis scenario using HV3 type voice, model, analyze, and compare with present results.џўSpecify the model for translating bit errors to packet errors and add a discussion of contributing factors to packet loss which have not been modeled.џўIn 5.4.2: 1) clarify that only the 5.4.4 results are limited to 1 & 11Mbps 2) add a reference to the 5.5Mbps model 3) add a new subclause for the 2Mbps model and a reference to it in the introџўRemove subclause 9.3, "802.11 1 Mbit/s frequency hopping and IEEE 802.15.1 interference"џўRemove subclause 4.1.3, "IEEE 802.15.1 in the presence of an IEEE 802.11 frequency hopping interferer"џўRemove the sentence starting with: "The scope of this document is limited to DCF"џўRemove editor's note (all of line 7).џўChange "802.11" to "802.11b" [multiple places] ***also in: (subclause,page,line) 4.1,6,23 4.2,8,28 4.4,9,28 5.4.4,28,32 6.2,30,5 9.,34,5 10.1,41,10 10.1,41,25 10.2,42,12 10.2.4,50,20 10.2.4,50,22 10.2.4,50,24 10.2.4,50,25 10.3.2,52,7 10.3.2,52,24 11.,61,26 11.,61,28 11.,61,33џўRemove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.џўRemove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.џўIt may be desirable to have a method to synchonise the WLAN intervals and so WPAN intervals to allow meaningful 802.15.1 transmissions perhaps by sychronisation of TBTT's between BSS's?џўremove the word ""other"" so implying that STAs may also send CTS to reserve the channel for WPLAN.џўReacled ""802.119"" with ""802.11b""џўReplace ""project"" with ""this recommended practice""џўChange title to ""Coexistence of Wireles Personal Area Networks with Wireless LAN Devices Operating in 2.4GHz Unlicensed Frequency Bands.""џўRefer me to the text that specifies the expected behavior or add clarifying text on how to recover, possibly based on one of the scenarios I identified above.џўReplace bookmarks with usable list or remove them all together.џўAdd appropriate text to the definition, such as adding at th eend of the sentence ""while the systems are not more degraded then 1/n th of the total of systems operating together compared to operating autonomously"".џўChange ""working group"" into ""working groups"" and change ""this standard was completed"" into ""this standard approved for submission to Sponsor Ballot""џўConfigure Acrobat properly - verify bookmarks before distributing next draftџўAWMA and clause 10.2. Leave in PTA.џўpossible correction: ""but also the adjecent channels, the 22 channels that are susceptible could be increased to 24 channels"".џўI believe the correct reference should be 802.11b.џўThe rates supported needs to be consistantly stated in the doc. I suggest that you Remove the Editor's note:џўCorrect the ""This introduction is not part of the IEEE std xx-200x, title"" statement.џўCorrect the formatting of the page.qLVAL> d  ˜ ф0Dкšj-§Щ_)пxЧœK‡БRefresh the frequency usage table is not sufficient to guide implementation. Do we mean by updating the gџўRefresh the frequency usage table is not sufficient to guide implementation. Do we mean by updating the good/bad list at the master end as per 12.1? Do we mean more in terms of updating the slave frequency lists?џўBy marking the frequencies is not sufficiently specific to guide implementation. Do we mean marking the freuqices as good or bad according to the frequency classification scheme defined in 12.1?џўWhat are the frequencies being marked here with ""yes"" and ""no"" to indicate?џўThe first setence has independent clause.џўThe information element with ID 8 has already been defined by 802.11d supplement.џўThe order 11 items in a probe response frame has already been defined by 802.11d supplement.џўThe order 11 in a beacon frame body is defined by 802.11d already and conflicts with this definition.џўIt is not clear to the reader that PTA is the second MA layer technique.џўIncorrect word processor reference ""\cite{Bluet99}.џўNo system model is presented or discussed for 802.11b 2 Mbps. Simulaiton results are displaeyd in 5.4.3.џўThe collaborative methods are no longer proposals.џўThe methods described are no longer proposals.џўcould not find an explicit expression for using td and Phidџў-15 to +20dB appears to be wrong from Figure 4џўdifferentiated In note 3 at bottom of page 'much likely that'џў'or the disturbance caused by the undesired power' seems redundantџўIn fact there are 2 Mbps simulationsџў2Mbps DSSS system model missing; results presented in 5.4.3 include 2Mbps but there is no discussion of the 2Mbps model. Also, the 5.4.2 introduction section is a little confusing; it doesn't mention the 5.5Mbps model in 5.4.2.2.џўStatement on scope is under descriptions, and is inconsistent. PCF is part of Table 24, and subclause 10.2 (as Access Point / beacon) as well as other places in the document.џўScope (coexistence of .11b & .15.1) not consistently applied; 802.11 used in place of 802.11b when referring to PHY. This occurs in other clauses as well (see note in Remedy).џўThis draft is for a recommended practice, not a (supplementary) standard. It changes too many MAC operations at least from the 802.11 perspective. For example, AWMA in Clause 10.2 modifies the 802.11 MAC to time share with 802.15.1. The operations to handle the legacy 802.11 stations as described in Clause 10.2.4 are not also compliant with 802.11-1999.џўThe CTS mechanism is not a valid protocol sequence in the current 802.11 specification. Furthermore, the use of multicast group bit by STAs for purposes other than multicast by STAs would not be in compliance with the specifications. Since this draft is for a recommended practice, not a (supplementary) standard it can not modify the current standard.џў""allows any other Access Point"" implies that this node is an AP. I don't this is the most likely scenario. A co-loctaed STa-BT device seems more likely.џўscope ""limited to coexistence of IEEE Std 802.11b-1999 Wireless Local Area Net-works (WLAN) and IEEE Std 802.15.1 Wireless Personal Area Networks (WPAN)"" is inconsistent with document title ""Coexistence of Wireles Personal Area Networks with _Other_ Wireless Devices Operating in Unlicensed Frequency _Bands_.""џўIt is not clear to me how the 802.11b MAC should recover if the PTA determined that the transmission is not allowed. I think, the following scenarios are possible: 1. Transmit immediately after the deny condition is revoked. 2. Schedule a new transmission attempt, as if the previous attempt didn't happen (e.g. don't regards it as a retry). 3. Consider the deny as a 'virtual' collision and schedule a new transmission attempt as a retry.zNžД  N š ц - t ш>ƒФн№DiА@"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.4.1.22028T=@ 2€џўProvide formula if possibleXOЙЗЕЕŒ€~zvmiQA1 џП?"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.3.6.8183E0@ 2€џўchange to -10 to +10dBXOВАЎЎŠ~|zvmiQA1 џП>"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џўTable 71734E€џўBER missing in Table 7F@1XOДВААЄ€~zvmiQA1 џП="0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.3.6.3165E@@ 2A@1XOš˜––Š~|zvmiQA1 џП<"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.3.6.21539T€џў802.15.1 is wrong€џўreplace with 802.11XOФТРРŸ€~zvmiQA1 џП;"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices04џў4.1.4815E€џўchannels is redundant€џўremove first channelsXOЦФТТŸ|zvtmiQA1 џП:"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices03џў3.2522E€џўadd symbols as in SIR and SNR €џўadd (s/i)XOРОММЅzxtrmiQA1 џП9"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices03џў3.1.8337ED@ 2;@1XO˜–””ˆ|zvtmiQA1 џП8"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices01џў1.127E&@2G@1XO”’„xvtrmiQA1 џП7"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices0000E=@/XOƒsqqqmiQA1 џ™6џўPratik MehtaџўPratik_Mehta@Dell.comџў512-723-6214џўDell0000T@4В@1XOecaaUIGGGC?99+нЙ5џўGeert Awaterџўawater@woodsidenet.comџў+31 346 259 652џў+31 6 12424094џўWoodside Networks9џў9.032џў37-38TRn@4b@1XO’ŽŽ‚vrkgb`M=,§П4џўGeert Awaterџўawater@woodsidenet.comџў+31 346 259 652џў+31 6 12424094џўWoodside Networks9џў9.134џў20-22TR!@4˜@1XO’ŽŽ‚vrkgb`M=,§П3џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor5џў5.4.2216Tь@2Ч@1XO‹‰‰}qomib`I;-§П2џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor9џў9.33821T*@/[@1XO‹‰‰}qokgb`I;-§П1џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor4џў4.1.3747T*@/i@1XO‹‰‰}qokib`I;-§П0џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor4џў4.1628EД@2T@1XO‹‰‡‡{omigb`I;-§П/џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor1џў1.1221E€џўTypographical error."€џўreplace "802.119" with "802.11b"XOУСПП‘omigb`I;-§П.џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor1џў1.127Ec@/'@1XO‰‡……ymkigb`I;-§П-џўMcClellan, Kellyџўkpm@valencesemi.comџў949-428-4157џў714-501-6874џўValence Semiconductor1џў1.1152EД@2*@1XO‹‰‡‡{omigb`I;-§ПˆLVAL п q o Є\)ЈThe text describes a method of transmitting RTS/CTS to clear the eair of non-collaborating legacy 802.11b STAs so that collaborating WPAN may transmit. Another method that works and is fullyџўThe text describes a method of transmitting RTS/CTS to clear the eair of non-collaborating legacy 802.11b STAs so that collaborating WPAN may transmit. Another method that works and is fully within the sllowed scope of the 802.11b document is to trnamist a BEACON(CF) to start a contention free period. The collaborating AP will avoid polling during the time allocated for the WPAN.џўThe draft described a method by which the 802.11b AP can sent out a false RTS/CTS to clear the air so that legacy stations will not transmit (freeing the air for the coordinated WPAN transmissions). This method may work. RTS/CTS without data transmission is not an allowed sequenced in the base document.џўThis section contains much explanatory material as well as some normative functional material. This is difficult to know exactly what the new 802.11b document should look like.џўThe contents of section 10 is making modificaitons to the 802.11 base document(s). It is very important that this material be presented in a clear format so that the base document can be very well understood by the hundreds of engineers currently extended it in all the various projects. It appears that the material in 10.2.2.1, 10.2.2.2, 10.2.2.3, 10.2.2.4, 10.2.2.5, 10.2.2.6.1, 10.2.2.6.2, and 10.2.2.6.3 make changes to the base document. 10.2.2.6.1-3 state that the base document is 802.11.џўI don't know what the sentence ""The 1 and 11 Mpbs mdoes of IEEE 802.11b are implemented"" means. 802.15.2 Models corresponding to 1, 5.5, and 11 Mbps of 802.11b are described in 5.4.2.1 through 5.4.2.3. Results of interference simulation corresponding to 1, 2, 5.5, and 11 Mbps are presented in 5.4.3. The C code models for all modes appear to be included. And finally, 802.11b is implemented fully in the industry.џўThe paragraph here describing the two collaborative approachs does not seem to use the same vocabulary or be in synch with the detailed description of the collaborative methods presented in sections 10џў802.15 is defining other standards that have bearing on coexistence in the 2.4GHz frequency bands (802.15.3, 802.15.4 are examples). In addition, this document does not address the 11g technology and coexistence aspects with the 11b and 15.1/Bluetooth.џўThe coexistence results shown assume HV1 type voice, which uses three times the air time of HV3 type voice (using 1 mbps capacity for just one full duplex 64 kbps link) voice and is more robust due to redundancy than HV3. To add realism and generality to the simulations HV3 traffic should also be treated and the results should be compared with the existing ones.џўWhile there is an extensive treatment of the calculation of bit error rate from SINR, the performance results shown in clause 9 show packet error rate. There is a dubious statement that 'the packet error rate for the WLAN corresponds to the loss of ACK messages'. In reality the packet error rate will be dominated by the loss of data packets, since they tend to be longer than ACK packets and hence more vulnerable to bit errors. This would yield more pessimistic results then those shown. On the other hand there is no discussion of the correlation of the bit errors. If there is structure in the interference (and in this case there is) then bit errors tend to be correlated. This would yield a packet error rate which is less than that for i.i.d. distributed bit errors, i.e. it would make the results more favorable. A third effect which aggravates the packet error rate is the effect of interference on packet detection, which is not modeled and which tends to dominate the probability of packet loss by decoding errors, especially at low SINRs.”`Р| и  z е 2 ‡ о3Œч!oЋ\Зsа{џўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil4џў4.1.4813To@7•@8XO|zxxl`^ZXQOE7)§ПzџўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil4џў4.1632Tn@7•@6XOzxvvj^\XVQOE7)§Пy"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD12џў12.17015Eš@7‡@6XO|zxxl`^ZVPLG9+ џПx"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD11џў11.36743TRж@2‡@6XO~|zznb^ZVPLG9+ џПw"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD11џў11.36739TRФ@2?@ 6XO~|zznb^ZVPLG9+ џПv"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD11џўFigure 476713TRQ@2a@ 6XOƒsgc_[PLG9+ џПu"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD11џў11.36646E!€џўNot a direct way to say this...H@ 6XO›™™`^ZVPLG9+ џПt"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD11џў11.2.16410E €џўUsage issue?@ 6XO‹‰‡‡{b`\XPLG9+ џПs"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD11џў11.1.26248E+@2!€џўFix the grammar error (please).XOŸ››nb`\XPLG9+ џПr"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.2.45022T@4$@ 6XO~|zznb`\XPLG9+ џПq"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.2.45022TR3@4н@6XO€~||pd`\XPLG9+ џПp"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.2.2.6.34818TRS@2@6XO„‚€€thd`\PLG9+ џПo"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.2.2.6.2483TR^@2Ѓ@6XO‚€~~rfb`\PLG9+ џПn"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.2.2.6.14742TRg@2м@6XO„‚€€thd`\PLG9+ џПm"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.24210EВ@4л@6XO|zxxl`^ZVPLG9+ џПl"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.24210TRѓ@4X@6XO~|zznb^ZVPLG9+ џПk"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD10џў10.04047EJ@2t@6XO|zxxl`^ZVPLG9+ џПj"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD06џў6.0299E6@2€џўPlease fix the reference.XO”’i][YUPLG9+ џПi"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD05џў4.22236TRj@2L@6XO}{yyma]YUPLG9+ џПh"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD05џў4.2216TRЃ@4k@!1XO{ywwk_[YUPLG9+ џПg"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD04џў3.2915TRЫ@4;@6XO{ywwk_[WUPLG9+ џПf"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD04џў3.2913E4@2G@ 1XOywuui][WUPLG9+ џПe"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD04џў3.1845E0@ 2M@1XOywuui][WUPLG9+ џП9LVALХy­ віS4W3єЌK …ўiUse the more practical bandwidth of 17 MHz for the signal and use actual џўUse the more practical bandwidth of 17 MHz for the signal and use actual SIR ratios that can be measured on any of the existing hardware available.џўPlease consider movign the material in 12.1 to a standalone subsection prior to any reference to it. (Or after all references to it).џўProvide sufficient desription to guide implementation and to ascertain interoperability between all master and slave implementations.џўAdd sufficient detail to support implementation at the slave.џўI think maybe the yes means ""good"" and the no means ""bad"" based on the information in 12.1.џўChange the sentence to ""Channel classification is described in 12.1""џўChange the start of the sentence to ""The key idea is to...""џўAdd this method to section 10.2.4.џўAdd the RTS/CTS into the allowed sequences in Table 21 of the base document. Include editing instructions to insert this sequence in section 9.7. Include this in the Annex/Appendix of the 802.15.2 Supplement to 802.11b.џўThe next available number not used in an approved 802.11 draft supplement is 11. PRoposed 802.11h has not used these (but has defined 32 to 41). I recommend that the element id as displayed in Table 18 be changed from 8 to 11. The note reserving elements should list 12-15 as reserved.џў802.11d defined element 13-n as being present in a probe response frame when the request information item (order 3) asks for them in a porbe request frame. Proposed 802.11h inserts new items 13-17 and defines 18-n as being those present in reponse to a reqeust information item. I recommend that we call the needed item for 802.15.2 order 18 and list 19-n as being present in response to the reqeust information item.џўThe first unused item in approved 802.11 ammendments is 14; however, proposed 802.11h has already brought forward proposals for 14-18. I recommend changing the order of the item displayed in Table 16 in 802.15.2 to 19.џўPlease take the functional material (plus any desired explanatory material) and gather it into an Annex or Appendix of 802.15.2. Include in this material a pro forma title Draft supplement to STandard for LAN/MAN Specific Requirements - PArt !!: MAC and PHY specifications: Specificaiton for Coexistesnce of Wireless Personal Area Networks in Unlicnesced Frequency Bands using the Alternating Wireless Medium Access (AWMA) Collaborative Method. Add pro-forma statments that ""This supplement is based on the current edition of IEEE STD 802.11b, 1999. Note -- the editing instructions chaintedin thie supplement define how to merge the material contained herein into the existing base stnadard to form a new comprehensive standard as created by the addition of this Annex. The editing instrucitons are shown in bold italic. Three editing instructions are used: chagne, delete, and insert. [explain the terms as in 802.11d] Editorial notes will not be carried over into future editions.џўAdd somewhere near the top of the document that this 802.15.2 makes changed to the 802.11b-1999 document. Add other documents if you want them modified, too. Add a statement associated with the 10.2.2.x sections that they modify the 802.11b-1999 document. Change the statement associated with 10.2.2.6 to state it is ammending 802-11b-1999.џўPlease change the first sentence to state"" In the PTA technique, the second MAC layer technique, the 802.11b...""џўPlease describe the 802.11b system model by adding a new section in 5.4.2.џўPlease review the summary paragraph contained in 4.3.2 and bring in line with the section 10. Consider writing it in the sytle of paragraph 4.3.1 which provides a nice highlevel overview of the non-collaborative methods. Please specifically use the vocabulary of section 10, namely the AWMA and the PTA technique.№LVALfј ‰ & № М N  •”Y%$qСˆС“,"On interference collision ratio formula, a ""B"" џў"On interference collision ratio formula, a ""B"" variable used. A definition of ""B"" is required."џў"There is an useless "","" after ""event""."џўThe first part of this clause repeats the scenario from Fig. 17. It is needed?џў"Figs. 43, 45 and 46 are a very low quality objects. It is very hard to appreciate any results from these figures. "џў"There is an useless additional ""t"" in the sentence."џў"The variable ""N"" is used many times without saying what it is."џў"In Description field of Tab. 23, there is a reference to section 14.1.4.6. This section does not exist."џў"All figures related to access delay (Figs. 19, 21, 23, 25, 27 and 29) present three curves only. They miss one scenario. why? There is no units for the delay values on y-axis."џў"Figs. 18-29 use a similar legend to identify curves. The legend contents are related to Tab. 10 in someway but it is not full clear. For instance what does it mean ""Scenario 2 BT Slave""? what is the difference with respect to ""Scenario 1 BT Slave""?"џў"Table 10 refers to different ""experiments"" to evaluate the interference effects. Figs. 18-29 show interference simulation results in the presence of different ""scenarios"". Apparently, they refer to the same but it is not clear from the context. Thus, to avoid confusions a unique term should be used."џў"Reference is cited with encoded data ""\cite{Bluet99}"""џў"A simple two-state Viterbi receiver is introduced for IEEE 802.15.1. Since these sections deal with coexistence models to quantify interference effects, the reference to a Viterbi receiver would be better placed in non-collaborative mechanism sections."џўIt is said that the LDI receiver design meets the IEEE 802.15.1 on IEEE 802.15.1 interference specifications. A bit confusing wording.џўAn assumption is made that the PN sequence have sufficient length. That is a laugh with 11 chips.џўWhy not use the aCWmin feature like in TGg to reserve time for the WPAN transmissions? Sending a CTS with a huge duration may break legacy implementationsџўWhy does the CCK system model have a GFSK mod?џўMost current implementations use the optimal receiver, so why is the sub-optimum receiver used in the model?џўWhy does the 802.11b system model have a GFSK mod?џўWhy does the 802.15.1 system model have a DBPSK mod?џўThere is no receive mask and if there were it would have a bandwidth of about 17 MHz, not 22 MHz.џўNumerous references are made to the DS PHY having a channel bandwidth of 22 MHz. This is not correct. all current implementations use a SAW filter of about 17 MHz or a LPF of about 8.8 MHz to constrain the emitted spectrum to fit the spectral mask. Generally speaking the 90% power bandwidth of the signal is around 11 MHz unless artificially processed to expand it. This is a result of the sinx/x nature of the waveform. Thus, the actual performance of this simulation will be in error by too pessimistic estimate of the interference potential of the DSSS signal and of the interference rejection of DSSS receivers.џўNumerous references are made to the DS PHY having a channel bandwidth of 22 MHz. This is not correct. all current implementations use a SAW filter of about 17 MHz or a LPF of about 8.8 MHz to constrain the emitted spectrum to fit the spectral mask. Generally speaking the 90% power bandwidth of the signal is around 11 MHz unless artifically processed to expand it. This is a result of the sinx/x nature of the waveform. Thus, the actual performance of this simulation will be in error by too pessimistic estimate of the interference potential of the DSSS signal and of the interference rejection of DSSS receivers.џўI would prefer to see the material in 12.1 introduced prior to the two methods that use it rather than inside the second method and after the first one.РLVAL2k. чРo’ f ; ћ  ! E  ч Z / ѓ  T л‚XзŒ[јЫ @эТ†cКoф‘aqяЖ2Explain the overall goal of the algorithm. For example, why keepџўExplain the overall goal of the algorithm. For example, why keep track of any of the bad channels (see line 31, page 75) Define Kџўadd reference clauses for 'LMP format' and 'AFH clause'џўadd - 'LMP = Link Manager Protocol' to figureџўLine 3 - should read 'case, increasing' Line 3 - should read 'to less than 1...'џўLine 49 - should read 'maintained, random bit..' Linr 51 - should read 'that uses more error protection the performance of the SCO link will be increased.'џў802.15.1. Rx activity have greater [i.e., add the Rx; I am not sure of this one]џў'As an optional ......addressed to its ......'џўTherefore the Medium is free of WLAN traffic when the Medium Free signal is True.џўLine 48 - change to As such Line 51 - another, in orderџўUse WLANinterval in place of WPANinterval in the syntax of the control signals.џўIndicate which of the 802.11b or 802.15.1 the existing curve respresentsџўModify the second row, second column equation as follows: WB(n+1) = P NBk - nWB(1)џўModify the second row, second column equation as follows: WG(n+1) = P NG - nWG(1)џўImplement exact hopping sequence.џўModify second equation to Path Loss = 58.29 + 33log10(d/8)џўNeed to have BER at least 10^-3 or lower.џўUse the same definitions for the signal-to-interference ratio in the two models.џўA reference to clause 10.2.4 would be useful to indicate that legacy STAs are covered as well.џўChange to ""Recommendation: Thus PTA...""џўChange to ""Recommendation: Thus AWMA ...""џўe.g. change to ""& can support up to three non-overlapping channels in the 2.4 GHz IMS band.""џўChange to ""& . IEEE 802.11b WLAN and & .""џўJoint investigations/considerations of 802.15.2 and .11e are recommended.џў"Apparently, you should replace ""xxx"" by 53. Please check it."џўExplain the reasons to keep bad channels in the hop sequence.џўInclude respective variable definitions.џўIndicate when a channel classification must be done and how often it should be updated.џўA minimal set of mandatory rules for channel classification should be included to ensure multi-vendor interoperability.џўRefers to Fig. 17 and minimize repetitions.џў"Improve the quality of Figs. 43, 45 and 46 to get at least the same quality of figures from previous sections."џўInclude figure with performance gain for 11 Mbit/s system.џўIndicate that the filter has (2N+1) taps.џўSome specifications for the minimum and maximum duration of the WLAN subinterval could help here to prevent forever deferred transmissions.џў"Include ""SME"" in the list of abbreviations."џў"Use sub-index to write ""WPAN"" in TWPAN."џў"Write the legend starting with Scenario 3 BT Slave (diamond), then Scenario 3 WLAN Mobile (square), Scenario 4 BT Slave (triangle) and Scenario 4 WLAN Mobile (x). Apply similar rule for all figures of this section."џўAnalyze the simulation parameters used to generate this curve and validate the simulation results with longer simulations.џў"Include the missing curves in access delay figures. Write ""seconds"" in the y-axis label."џўAdd an explanatory note defining the meaning of all scenarios.џў"Replace ""Experiment"" by ""Scenario""."џўReplace code by normal numbered reference.џўMove all references to Viterbi receiver to a new section on non-collaborative mechanism (between section 11 and section 12?)џўPerhaps it means the LDI receiver design meets the IEEE 802.15.1 interference specifications.џўConsider change to aCWmin style reservation.џўRemove the GFSK mod from figure 8џўUse the optimal receiver in the modelџўRemove the GFSK mod from figure 6џўRemove the DBPSK mod from figure 5џўUse the more practical bandwidth of 17 MHz for the receiverџўUse the more practical bandwidth of 17 MHz for the signal and use actual SIR ratios that can be measured on any of the existing hardware available.W]Иn Ч  d Љ ю < HаZžФщ)M0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џў10.4.15940ED@7+@8XO—•““‡{yuqie\I6џПœ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џўTable5320El@7€џўIndicate the right reference.XOЕГББ†zxtpie\I6џП›0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џў10.2.35017TR.@:@8XO™—••‰}yuqie\I6џПš0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џў10.2.2.1.24420€џўSME has not been defined.1@8XOДВААЄ}}yuie\I6џЗ™0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џў10.24217E€џўSub-index not used in TWPAN.-@8XOГБЏЏЃywsoie\I6џП˜0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips9џўFigure3732E @:м@8XO•“‘‘…ywsoge\I6џП—0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips9џўFigure211TRФ@:|@ 8XO•“‘‘…yusoge\I6џП–0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips9џўFigure351EГ@7^@ 8XO“‘ƒwusoge\I6џП•0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips9џўFigures3424E@7@@ 8XO–”’’†zxtpge\I6џП”0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips9џўTable3311E4@ 7+@ 8XO”’„xvrnge\I6џП“0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips6џў6.22946E€џў"Misspelling: ""Blueooth"""€џў"Replace with ""Bluetooth"""XOЭЫЩЩŸvtplge\I6џП’0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips6298E;@ 7,@ 8XO‹‰‡‡{omkgge\I6џО‘0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џў5.4.42828E@ 7~@8XO”’„xvrnge\I6џП0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џў5.4.42725Eˆ@ 7_@8XO”’„xvrnge\I6џП‚џўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil10џў10.4.16022Ed@ 7€џўReview assumptionXO”’qec_[SOE7)§ПџўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil10џў10.2.45028E@7.@8XO}}qec_[SOE7)§П€џўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil5џў5.4.2.32430E0@7#@8XO€~||pdb^ZQOE7)§ПџўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil5џў5.4.2.2234En@7'@8XO~|zznb`^ZQOE7)§П~џўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil5џў5.4.22123E4@7#@8XO~|zznb`\XQOE7)§П}џўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil5џў5.4.11918E6@7$@8XO~|zznb`\XQOE7)§П|џўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil5џў5.3.5147Ec@7=@8XO|zxxl`^\XQOE7)§П#LVAL<3  < — h Й`јєЧx-ЫŽ.Т‰'мСеŸiBoth equations on the secџўBoth equations on the second row should be the same.џўBoth equations on the second row should be the same.џўFix formating. Top equation is off the page.џў802.15.1 hopping sequence is not implemented as defined in Bluetooth standard. Frequencies were chosen randomly. This does not correct modeled the correlations between hopping frequencies.џўThis technique has only been shown to work for 1 Mbps and not sure how well it will work for higher rates. In addition, the cost of adding an 802.15.1 receiver may be prohibitive in an 802.11b receiver.џўPlace a period after the end of an equation if it is the end of the sentence.џўPath loss equation is not continuous.џўA BER of 10^-2 is not enough good.џўThe two models should be defined such that their results can be used to collaborate each other.џўIn line 14, I believe that "effect" should be "affect".џўThe order 11 in the .11 beacon frame body is already used by 802.11 and refers to the Country information.џўA reference to clause 10.2.4 would be useful to indicate that legacy STAs are covered as well.џўspace character is missing: ""Recommendation:Thus PTA ...""џўmissing space character: ""Recommendation:Thus AWMA ...""џўexact definition of ""fd"" is missingџўtypo: ""signal power at recevier"" and ""interference power at recevier""џўinexact statement: ""& can support up to three channels in the IMS band.""џўtypo: ""& . IEEE 802.119 WLAN and & .""џўThe impact of the proposed AWMA procedure on QoS performance of each involved technology is not covered yet in detail. What is the impact of QoS on TWPAN & TWLAN? How to consider/schedule the priority of services which are offered by different technologies?џўIt is said that some bad channels should be kept in the hopping sequence. why should the device do it?џў"Many variables are used without indicating their meanings, namely: NG, Nmin and p(k)."џў"There is no indication on how often the channel classification should be done. Before to reduce the classification time, an indication on the update frequency is required."џў"It is said that the channel classification implementation is up to the coexistence mechanism solution vendor. In this case, how can we guarantee interoperability between master and slaves devices from different vendors if every implementation has its own definition of ""good"" and ""bad"" channels."џў"Sentence referring to Fig. 48 says packet error arte is 24 % for DM5 and DM3, and 19% for an DM1 packets. But looking to Fig. 48, actual values are 20% and 15 %."џўThe performance gain of the adjustable transversal filtering is shown in Fig. 42 for IEEE 802.11 1 Mbit/s system. Is it possible to show the benefits of this technique (if any) for 11 Mbit/s systems.џў"It is said that if WLAN frame is too long for the WLAN subinterval, its transmission must be deferred to the next WLAN subinterval. How can we be sure that the bext WLAN subinterval is long enough for the deferred WLAN frame? May it happen that the selected WLAN subinterval is never long enough? "џў"By comparing legend between Fig. 24 and 20, it is clear that there is no a common style to assign the ""signs"" and ordering the scenarios. To help the reader in doing comparisons, it would be nice to have a general rule to build-up the legends and follow it. "џў"Figure 21 presents a rare ""peak"" in the delay curve of ""scenario 3 WLAN Mobile"". It is said that it is due extremely high packet error rate. However looking to Fig 20 (on Packet error rate), it is seen that within 2 meters the PER decays from 90% to 80% and in the same 2-meter interval, the access delay rises from 0.05 sec to 0.15 sec. How can it be that for roughly the same high PER we get variations of more than 100% in the access delay?"!&jЌ ю  T a Ÿ Фт&hŠјaЪY‹ёYВ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.1426E=@:+@8XOqommaUSQMGC>>- пПБ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.14150E;@:-@8XOsqoocWUQMGC>>- пПА"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD05џў5.4.32628E€џўtypo: ""inteference""€џўChange to ""interference""XOЇЅЃЃ{XVRNGC>>- пПЏ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD05џў5.4.3256T'@ :€џўAdd the definition of ""fd"".XO‘bVTRNGC>>- пПЎ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD05џў5.3.2, figure 312EK@ :€џўChange to ""receiver""XO’ŽŽj^\\XGC>>- пЛ­"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD04џў4.1632EO@ :c@8XOpnll`TRNLGC>>- пПЌ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD01џў1.2220E-@ :1@8XOpnll`TRNLGC>>- пПЋ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD0000TR@ :K@8XOkigg[OKKKGC>>- пЙЊ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.2.1775E"€џўUnclear reference to Figure xxx.B@8XOЗЕГГЇywuqie\I6џПЉ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.2.17644Th@:?@8XO—•““‡{yuqie\I6џПЈ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.27526EY@:*@8XO•“‘‘…ywsoie\I6џПЇ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.1.2.47339Eg@7"€џў"Include a definition of ""B""."XOЛЙЗЗ‰}{wsie\I6џПІ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.1.2.47322E.@7€џў"remove additional "","""XOДВАА‰}{wsie\I6џПЅ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.1.2.47315TRЏ@:Y@8XO›™——‹{wsie\I6џПЄ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.1.2.27215E€џў"Misspelling: ""finial"""€џў"Replace by ""final"""XOЬЪШШЄ}{wsie\I6џПЃ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips12џў12.17028TR/@:y@8XO—•““‡{wsoie\I6џПЂ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips11џў11.3.1691EЅ@: €џўReplace 24 by 20 and 19 by 15.XOЕГББ…ywuqie\I6џПЁ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips11џў11.3.16750EP@7-@8XO—•““‡{yuqie\I6џП 0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips11џўFigure6311Ew@7r@8XO—•““‡{yuqie\I6џПŸ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џўFigure611TЩ@:<@8XO•“‘‘…ywuqie\I6џПž0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips10џў10.4.36038E9@7€џў"Remove additional ""t""."XOГБЏЏ‡{yuqie\I6џП)h›л &  ё M ƒ х - шDŸњQ‰ЮчўcD"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.141E*@=9@)8XO•“‘‘…ywwsmiQA1 џЛC"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.4.32632T€џўfrom figure 12 eb/no=7€џў8->7XOИЖДДЂ~|xtmiQA1 џПB"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.4.2.22320E €џўdefine ri€џўri=received chip, i={1,7}XOТРОО—€~zvmiQA1 џПA"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices05џў5.4.22110E €џўsource. the€џўchange to 'source. The'XOРОММ—~|xtmiQA1 џПгџўBent Hessen-Schmidtџўbhessen@att.netџў(203) 972-6836џў(613) 612-478910џў10.2.2.6.1-10.2.2.6.4џўTable 16 & 17Tё@=R@(8XO”’„xvvgPLL<,НЛвџўBent Hessen-Schmidtџўbhessen@att.netџў(203) 972-6836џў(613) 612-478910џў10.3.1 Table 1951EX@=€џўCheck and correct if needed.XOЁŸsgeeaPLL<,НЛбџўBent Hessen-Schmidtџўbhessen@att.netџў(203) 972-6836џў(613) 612-47895џў5.3.6.8 Figure 418ED@=K@'8XO‚€~~rfdd`NLL<,НЛа"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments12џў12.2.3џў8082TRO@=€џўFix.XO~|zzh\XXRJF33% пЛЯ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments12џўTable 2978џў1113TR6@:U@&8XO~|zznb^XTJF33% пПЮ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments12џўTable 2978џў810TR6@:T@%8XO}{yyma]XTJF33% пПЭ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments12џў12.1.2.3731E.@:€џўFix.XO~|zzh\ZXTJF33% пПЬ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments06џў6.229џў4954TRО@:#@$8XOywuui]YSOJF33% пПЫ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments10џў10.4џў5860џў154TRЬ@:€џўRemove section 10.4.XO‘k_[VPJF33% пПЪ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments00џўGeneralEO@:€џўFix.XOwussaUSSSJF33% пЙЩ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments05џў5.3.6.215џў3334E€џўTypo.!€џўMove period to end of equation.XOЃЁŸŸr_]WSJF33% пПШ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments05џўTable 110џў4647TR'@:<@#8XO}{yyma]WSJF33% пПЧ"0џўBatra, Anujџўbatra@ti.comџў214-480-4220џўTexas Instruments05џў5.4.3256TR$@:+@"8XOwussg[WUQJF33% пПЦџўFred HaischџўHaisch@agere.comџў678 924 6600џўAgere Systems5џў5.09џў41-42Tb@:S@!8XOpnll`TRKIDB33%нПХџўFred HaischџўHaisch@agere.comџў678 924 6600џўAgere Systems4џў4.1614E9@:!€џўReplace "effect" with "affect".XOŽŒŠŠ]QOKIDB33%нПЕ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.2.2.6.1, table 1647TRl@:€џўNeeds to be clarified.XO™—••qeaa]GC>>- пЛД"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.2.64729E€џўtypo: ""accomodate""€џўChange to ""accommodate""XOІЄЂЂ{YWSOGC>>- пПГ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.2.142E`@:`@ 8XOqommaUSSOGC>>- пЛLVAL%Бm$њ Ю Ѕ u ъ Д , ђ Ф   a > - <|!сІєg3фc т{Sр} С‰_row5, column2: Quesџўrow5, column2: Question mark is missing.џў: ""& 802.15.1 activity havegreater priority & ""џўmissing space character: "" & transmit activity.The decision & ""џўThe order 11 in the .11 probe response frame is already used by 802.11 and refers to the FH parameter information.џўSimulation results are shown without indicating the parameters used for the computer simulations.џў"Caption of Figure 4 refers to 802.11b and 802.15.1 modulation types, however the curve for 802.15.1 is missing."џў"Equation (1) contains useless ""."" "џў"Paragraph ""The IEEE 802.11 MAC ... may not be tolerable"" is repeated at the end of clause 4.1.2. "џў"Double ""."" at the end of the line. "џўEnsure that the document addresses 802.11g (OFDM) interference, together with 802.11bџўBER_f is to be measured for each frequency. Commonly, the receivers cannot measure BER, just PER. Perhaps this is a misprint.џў802.11b has many more channels than 3, so the statement is perhaps incorrect.џўWords of abbreviation do not match use in documentџўThe PTA algorithm should be the recommended practice whenever SCO links need to be supported; this should be added to this section (10.1).џўThe graph of the power spectrum of the Barker code is misleading. The formula should be a series of impulses with amplitudes following the sinc2() function, except for k = 0.џў"79(23)" should be expanded to something more meaningful.џўSeveral, but not all, instances of "effect" should be "affect"џўDBPSK & DQPSK use "differentiated", but the text in the document body use "differential".џўAWMA has dramatic impact on the proposed 802.11e. Since 802.11e may be approved prior to the approval of this recommended practice, the impact on QoS operation should be addressed.џўFigure 38: This diagram makes no distinction between present collisions versus future collisions the way that Figure 37 does. What should happen when the 802.15.1 logic makes a Tx Request but the 802.11 is already transmitting?џўAWMA in Clause 10.2 modifies the 802.11 MAC to have time sharing with 802.15.1. This is not allowable for a recommended practice. In addition, the operations to handle the legacy 802.11 stations as described in Clause 10.2.4 are not compliant with 802.11-1999 as well.џўWG(n+1) should be WB(n+1) I thinkџўFigure xxx needs defining Table 29 formulas run into boarderџўI am not familiar with this algorithm and could use a little informative text. This seems more complicated than necessary; I am sure it is me but don't we need to simply find the good (non interfered with) channels and use them to set up a sequence? Also, on page 76, lines5,7,10 what is Kџў'LMP format' and 'AFH clause' not referencedџўLine 3 - 'case, by increasing' Line 8 - 'to around 1..'џўLine 49 - maintained. In this case, random Line 51 - 'that uses more error protection will increase the performance of the SCO link.'џў'Methods of adaptive packet selection' is not neededџўFrom Figure 37 since .15.1 is not transmitting it must be receiving so should the table entry (and the decision block in Figure 37) readџўChange 'An optional ....addressed its.....' toџўOrder 11 is alrady spoken for I believeџў'agAWMAgrp' may be wrong (just my feeling)џўline 48 - And such Line 51 - another, soџўPrefer WLANinterval to be listed in place of WPANinterval as this might be used/useful for other synchronizations such as quite periodes for measurements or antenna sharing/coexistence with GSM, EDGE, WCDMA mobile phones or GPS devices.џўNone and Receive seems to have been switches in the last two columns of the last row.џўOne of the 1Mbit/s curves of either 802.11b or 802.15.1 is missingџўPartition sequence parameters do not match the algorithm described in 12.2.1.У/Hr z И Ц   ;jІфNRŠЪѕV"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices12џў12.2.17824T#@=€џўchange to WB(n+1)XOЎЌЊЊ‹}yumiQA1 џПU"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices12џў12.2.1776E?@=3@?XO™—••‰}{yumiQA1 џПT"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices12џў12.2 and 12.2.1џў756T$@ =„@18XOЁŸ‘…ƒƒ~miQA1 џЛS"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices12џў12.1.2.3731E€џўHeader interfers with formula€џўmove formula down on pageXOегббЊ}{wmiQA1 џПR"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices12џў12.1.2.27220E.@ =9@08XO›™™{wmiQA1 џПQ"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices11џўFigure 4767E€џўLMP not defined/@/8XOЋЉЇЇ›~||xmiQA1 џЛP"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices11џў11.1.26338E:@ =S@.8XO›™——‹}yumiQA1 џПO"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices11џў11.1.262џў4951Eˆ@ =ž@-8XO›™™yumiQA1 џПN"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices11џў11.1.16153E6@ =€џўremove phraseXOЊЈІІ‹}yumiQA1 џПM"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.4.16038E€џўTherefore, t the€џўTherefore, theXOНЛЙЙ}yumiQA1 џПL"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.3.85730E€џўsubclaueses should read €џўsubclausesXOРОММЄ}yumiQA1 џПK"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џўTable 2555T‹@=R@,8XO™—••‰}{{wmiQA1 џЛJ"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.3.15138E€џўchange 'addition types'€џўto 'additional types'XOЫЩЧЧЄ}yumiQA1 џПI"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.2.45022E0@=0@+8XO›™——‹}yumiQA1 џПH"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.2.2.6.34810E€џўchange '9-15 to Table 20'€џўto '9-15 in Table 20'XOбЯЭЭЊƒ}ymiQA1 џПG"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џўTable 16&17џў47-48TR)@=€џўTry order 19XOЏ­ЋЋ‘…zmiQA1 џЛF"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.2.2.5.14622T,@=!€џўShould the label be 'apAWMAgrp'XOРОММƒ}ymiQA1 џПE"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices10џў10.2.1436E€џўReword sentenceS@*8XOЊЈІІš}{yumiQA1 џПŒLVALЭ„1 c:V %  г   F  ч > Ф u ЂЙ†5Ÿ[кЋ…NжRemove this option from the document or find an alternative method to achieve the bandwidth sharing without requiring changes to 802.11 standard. For example an AWMA-like mechanism can be obtained by using the upcoming 802.11e TxOPs. An 802.11 device can request additional TxOPџўRemove this option from the document or find an alternative method to achieve the bandwidth sharing without requiring changes to 802.11 standard. For example an AWMA-like mechanism can be obtained by using the upcoming 802.11e TxOPs. An 802.11 device can request additional TxOPs from the AP, to cover the bandwidth required by the co-resident 802.15 device. In this way the 802.11 standard does not need to be modified (nor the 802.11e draft) and the Master can gate it's operation based on granted TxOPs to achieve coexistence and possibly even supporting SCOs.џўChange to "" & Wireless Personal Communications & ""џўChange to "" & discusses the physical layer & ""џўChange to ""Annotated bibliography""џўChange to "" & following subclauses & ""џўInsert a space character and question mark: ""& 802.15.1 activity have greater priority than the requested 802.11b packet?""џўAdd space character "" & transmit activity. The decision & ""џў"Include grid in Fig. 11. Replace ""EbNo"" by ""SIR"" in Fig 12. Use normal horizontal x-value sin Fig. 13. Select one font for labels and keep it."џўIndicate length of simulations as well as 802.15.1 and 802.11 parameter values.џўPlease include the curve of 802.15.1 in Figure 4.џў"To understand the consequences/effects of certain system configurations, it would be helpful to have a unique, coherent and unambiguous definition of signal-to-interference ratio. The suggestion is to standardize this definition."џў"There are many valid non-collaborative proposals for IEEE 802.11 based on equalization, antenna diversity and similar which can be included in the draft. Some evaluation of these alternatives should be made."џўRemove the repetition of the paragraph and place it at the end of clause 4.1.џўAnalyze the impact of mandating PCF for IEEE 802.11 implementations in terms of system performance and interoperability.џўFurther work is required to complete the quantification of the interference problems. More detailed specification can be included in described coexistence mechanisms.џўInclude results of the analysis and simulation.џўPlease reverse the order of 4.3.1 and 4.3.2.џўPlease change the wording to ""can support 3 non-overlapping channels in the ISM band.""џўChange to signal to interference plus noise ratioџўRemove all the mechanisms and operations which are not compliant with 802.11-1999 specification. Otherwise, reclassify this draft specification as a draft for a supplementary standard.џўSpecify the model for translating bit errors to packet errors and add a discussion of contributing factors to packet loss which have not been modeled.џўAdd text to recommend PTA for SCO link support.џўEither remove the sinc2 envelope imposed over the series of impulses or else change its line type to a light gray halftone to distinguish it from the power spectrum function itself.џўChange appropriate instances to "affect".џўChange all instances to "differential".џўIt appears that AWMA is incompatible with QoS operation. If so, that should be explicitly stated, similar to the statement that AWMA is incompatible with SCO links..џўUpgrade Figure 38 for this condition.џўRemove those mechanisms and operations which are not compliant with 802.11-1999.џўDefine the LMP commands and enter the op codes in Tables 34, 35, 37, 38џўxxx -> 53(?) move formulas down or enlarge table{Žд  j М ь + u Ш9œџbЉZ–н$iЕŠ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5942TR@Hщ@?XO‹‰‰}qmigge\I6џО‰0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips4џў4.3.1845TR›@Hг@?XO”’„xtpnge\I6џПˆ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips4џў4.1.1712Eg@=O@?XO’ŽŽ‚vtpnge\I6џП‡0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips4џў4.1628TRM@Hz@?XO’ŽŽ‚vrnlge\I6џП†0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips464E)@=€џў"Delete one ""."""XO›™™ymkigge\I6џО…0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips0щ@HЉ@?XOƒsggggge\I6џА„џўDorothy Stanleyџўdstanley@agere.comџў630-979-1572џў404-307-4277џўAgere Systems0000TRX@=1@?XO~|zznb^^^ZVG9+§ЙƒџўCarl Andrenџўcandren@intersil.comџў321-724-7535џў321-223-9657џўIntersil11џў11.36738E@=€џўChange BER to PERXO’ŽŽoca]YSOE7)§Пd"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD043845E@H.@ ?XOvtrrfZXTRPLG9+ џПc"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD031633TO@=Z@ ?XOvtrrfZXTRPLG9+ џПb"0џўCole, Terryџўterry.cole@amd.comџў512-602 2454џў512 543 2650џўAMD032520T4@=3@ ?XOvtrrfZXTRPLG9+ џПaџўGarg, Atulџўatul.garg@philips.comџў408-474-7987џўPhilips0000TRz@HК@ ?XOhfddXLHHHD@77)нЙ`џўPartho Mishraџўparthomishra@woodsidenet.comџў650 475 1983џўWoodside Networks9џў9.134џў20-22TR@H˜@ ?XO†„‚‚vjf_[VTAA3нП_џўJim Lansfordџўjim.lansford@mobilian.comџў+1 405 377 6170џў+1 405 747 5229џўMobilian Corporation10џў10.1T@=1@?XO‹‹sqqqkgQ@/§Й^џўEdward Reussџўed.reuss@plantronics.comџў831-458-7483џў831-588-5864џўPlantronics, Inc.5џў5.4.2.1 Figure 722џў10-24EВ@=Й@?XOš˜––Š~|uq_]J<.§П]џўEdward Reussџўed.reuss@plantronics.comџў831-458-7483џў831-588-5864џўPlantronics, Inc.5џў5.4.1191E;@=€џўDescribe what "79(23)" means.XOЉЇЅЅznljf_]J<.§П\џўEdward Reussџўed.reuss@plantronics.comџў831-458-7483џў831-588-5864џўPlantronics, Inc.4џў4.1џў6-8E@@=+@?XO‡…ƒƒwkiid_]J<.§Л[џўEdward Reussџўed.reuss@plantronics.comџў831-458-7483џў831-588-5864џўPlantronics, Inc.3џў3.24џў38 & 41E[@=)@?XO‹‰‰}qofd_]J<.§ПZџўEdward Reussџўed.reuss@plantronics.comџў831-458-7483џў831-588-5864џўPlantronics, Inc.10џў10.255џў3-44TР@=Ї@?XO‹‹sqkga]J<.§ПYџўEdward Reussџўed.reuss@plantronics.comџў831-458-7483џў831-588-5864џўPlantronics, Inc.10џў10.3.656џў3-44TRё@='@?XO“‘ƒwsmia]J<.§ПXџўChiu Ngoџўchiu.ngo@philips.comџў914-945-6475џўPhilips10џў10.2TR@=S@?XOgeccWKGGGA=44&нЙW"0џўHillman, Garthџўgarth.hillman@amd.comџў(512) 602-7869џў(512) 415-8400џўAdvanced Micro Devices12џў12.38211TR"€џўThe LMP commands are not definedI@?XOНЛЙЙ­{wsmiQA1 џП №LVALањN  џџ џ MR2Ž€ FilterOrderByOrderByOnColumnWidthColumnOrderColumnHiddenValidationRuleValidationTextDescription FormatInputMaskCaptionDefaultValueRequiredAllowZeroLengthDisplayControlDecimalPlacesЙ Є œlb34_r0.Clause, lb34_r0.Subclause, lb34_r0.Page, lb34_r0.Line, lb34_r0.Comment[CommentID џџџџ      mc CommenterName џџџџ      me"CommenterEmail џџџџ      me"CommenterPhone щ      maCommenterFax џџџџ      m_CommenterCo џџџџ      m[Subclause џџџџ      m_CommentType џџџџ      mYResponse џџџџ      mc CommentStatus џџџџ      me"ResponseStatus џџџџ      mMComment >     ]$SuggestedRemedy      AAutonumber џџџџ  U Clause џџџџ      mQPage џџџџ      mQLine џџџџ      m`LVALу i й №Ѓx*ўЦ•h5§ŒAlthough the AWMA mechanism is interesting, I'm not sure whether it is valid for a Recommended Practice document as it requires modification to existing standards. If the 802.11 stџўAlthough the AWMA mechanism is interesting, I'm not sure whether it is valid for a Recommended Practice document as it requires modification to existing standards. If the 802.11 standard is modified to add the Element in the Beacon and Probe Response, then it ceases to be a recommended practice, and probably becomes a "shall" if the WPAN option is implemented..& џўtypo: "" & Wireless Personnal Communications & ""џўtypo: "" & discusses the physcial layer & ""џўreference is missing: ""IEEE Std XXX-2002""џўreference is missing: ""Figure xxx shows & ""џўmissing space characters: ""& 1.6ms to 2.6ms & ""џўtypo: "" & following subclaueses & ""џў"Some uniformity in the figure style is required. Fig. 11 presents no grid in contrast with all others. Fig. 12 shows ""EbNo"" x-label while the other figures use ""SIR"" x-label. Fig. 13 uses x-values with inclination, while the other figures present normal horizontal text. Fonts in all figure labels need to be standardized."џўIt is said that results provided by the two models are not directly compared because of different definitions of signal-to-interference ratio.џўNon-collaborative proposals are described only for IEEE 802.15.1. Why were non-collaborative proposals for IEEE 802.11 excluded from the recommendations?џўIt is said that the scope of the document is limited to DCF implementations of IEEE 802.11. Has it been considered seriously the alternative to mandate PCF in next WLAN generations? Having a single node as IEEE 802.15.1 master and IEEE 802.11 Point coordinator would help a lot to reduce interference problems between both systems.џў"Overall the draft is a good effort to analyze the interference problem in 2.4 GHz indicating possible solutions. However, it presents some areas to be enhanced in terms of quality of presentation and completeness of the contents."џўThe order of the collaborative and non-collaborative discussion in the overview does not match the order of the material in the main sections.џўThis draft is for a recommended practice, not a (supplementary) standard. However, I find that it changes many MAC operations at least from the 802.11 perspective. For example, AWMA in Clause 10.2 modifies the 802.11 MAC to time share with 802.15.1. The operations to handle the legacy (?) 802.11 stations as described in Clause 10.2.4 are not also compliant with 802.11-1999.џўWhile there is an extensive treatment of the calculation of bit error rate from SINR, the performance results shown in clause 9 show packet error rate. There is a dubious statement that 'the packet error rate for the WLAN corresponds to the loss of ACK messages'. In reality the packet error rate will be dominated by the loss of data packets, since they tend to be longer than ACK packets and hence more vulnerable to bit errors. This would yield more pessimistic results then those shown. On the other hand there is no discussion of the correlation of the bit errors. If there is structure in the interference (and in this case there is) then bit errors tend to be correlated. This would yield a packet error rate which is less than that for i.i.d. distributed bit errors, i.e. it would make the results more favorable. A third effect which aggravates the packet error rate is the effect of interference on packet detection, which is not modeled and which tends to dominate the probability of packet loss by decoding errors, especially at low SINRs.(jБ г  R А  X МњPЁщRЙrУ1’єKжџўPeter Ecclesineџўpetere@ieee.orgџў408-527-0815џў925-443-2406џўCisco Systemsџў5,6,7,8,9џў9-39Ez@KJ@JXO‚€~~rfdd^^SD6(§КеџўAli RaissiniaџўAliRaissinia@woodsidenet.comџўWoodside Networks10џў10.4џў58-68TR‚@K3@JXOwussg[WWPJF333ЭЛдџўBent Hessen-Schmidtџўbhessen@att.netџў(203) 972-6836џў(613) 612-478910џў10.3.8.1T@K&@JXOxvtth\ZZZPLL<,НЙФџўFred HaischџўHaisch@agere.comџў678 924 6600џўAgere Systems4џў4.16TR5@KM@JXOkigg[OKKIDB33%нЛУџўJagannatha L Venkateshaџўjagannath@agere.comџў+1 - 678-924-6534џўAgere Systems10џў10.2.45021T}@K6@JXOˆ†„„xljfbZVGG4нПТџўJagannatha L Venkateshaџўjagannath@agere.comџў+1 - 678-924-6534џўAgere Systems0000TR@Ke@JXO~|zznb^^^ZVGG4нЙСџўTom Tsoulogiannisџўtomt@neesus.comџў416-754-8007џўNeesus Datacom Inc.10џў10.2.2.6TRq@H=@?XO{ywwk_[[[QM88*нЙР"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMDBџўB.3.29818E8@ H;@?XOrpnnbVTPLEC>>- пПП"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMDBџўB.3.1989E3@ H7@?XOpnll`TRPLEC>>- пПО"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMDBџўB.3.1984E!€џўtypo: ""Annotated biliography""&@?XO‘TRPLEC>>- пПН"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMDAџўheader of all pagesE-@ H€џўAdd reference.XOˆ†„„h\ZZZEC>>- пЙМ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD12џў12.2.1775E1@ H€џўAdd reference.XOƒcWUSOGC>>- пПЛ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD11џў11.3.1696E8@ H(€џўChange to ""& 1.6ms to 2.6ms & ""XO›™——cWUSOGC>>- пПК"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.3.85730E,@H/@?XOusqqeYWSOGC>>- пПЙ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.3.5, table 2555E*@$=€џўAdd question mark.XO‹‹k_]]YGC>>- пЛИ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.3.5, table 2555E8@#=@?XO{ywwk_]]YGC>>- пЛЗ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.3.3, table 2152EH@"=D@?XO{ywwk_]]YGC>>- пЛЖ"0џўMEYER, KLAUSџўklaus.meyer@amd.comџў+49(351)2776063џўAMD10џў10.2.2.6.2, table 1748TRt@!=€џўNeeds to be clarified.XOš˜––rfbb^GC>>- пЛ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џў"11, 12, 13"269EN@H–@?XO™—••‰}{yuge\I6џПŽ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џў5.4.3263E €џўreceiver€џў"Replace by ""receiver"""XOЗЕГГŒvtrnge\I6џП0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џў5.4.3251Tc@ =Q@?XO’ŽŽ‚vtrnge\I6џПŒ0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џўFigure1828TRs@=3@?XO—•““‡{wsoge\I6џП‹0џў"Kerry, Stuart J."џўstuart.kerry@philips.comџў+1 (408) 474-7356џў+1 (408) 348-3171џўPhilips5џў5.3.6.21533E(@=€џў"Remove additional ""."""XOБЏ­­†zxtpge\I6џПLVAL›eђПu? O „ п K z гžBсГ"Н}NЭInclude a systematic overview of scenarios of mutual interferenџўInclude a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.џўAppropriately remove all dashes in referencesџўChange the language and structure to acknowledge 4 mechansims.џўDelete 'respectively'. It doesn't apply and, anyway, there is clarification in the next paragraph.џўReplace all occurences of OPNET with an appropriate description of the functionalities that have been used.џўAdd this shortcoming to the text.џўAdd results on optimal receiver performance.џўLine 32 should read ..... sub-optimal system provides a BER of 10-3 for an Eb/N0 of 7 dB ......џўAdd BER=0 in Upper Limit column heading, and add BER>/= 0.5 in Lower Limit column heading.џўchange to ..... three non overlapping channels ....џўAdd sentence: The PTA technique only works well if the WPAN device also uses adaptive frequency hopping to avoid interfering with other WLANs in the same location. џўAdd sentence: Alternating Wirless Medium Access Control Area (AWMACA). All devices entering into the AWMACA shall adopt the rules of the area. 1. All WPAN master devices must role-switch to a AWMA master in the area. 2. Only piconets with a AWMA master are allowed 3. IBSS networks must adopt the timing parameters and synchronize its clock with the AWMACA. 4. All WLANs in the AWMACA shall adopt the timing parameters and synchronize its clock with the AWMACA. џўAdd sentence: Additionally, in an environment where there are multiple WLANs in the same coverage area the clocks of all WLANs are synchronized. џўRe-word sentence: These two parameters are programmable over the WLAN and can be allowed to change dynamically according to the load of the two wireless systems. џўCharts and text to reflect the ubiquitous coverage and the density issues in the interference in the non-collaborative environment.џўRewrite 12.1.1.2 to use RxQuality instead of or in addition to PER.џўRewrite 12.1.1.1 to use RSSI as specified in 802.11b 15.4.5.10џўMove clause 10.4 to be the clause that follows the collaborative scheduling clause, and create a figure like Figure 30, but including both Figures 39 and 40 as blocks within.џўadd simulation results for 2, 5.5 and 11Mbps 802.11bџўMove clauses 6-9 to a first informative Annex and renumber the document.џўRemove spectral nulling as a recomended practice.џўInsert a recommended priority table.џўInclude 802.11g in the analysis and in the proposed coexistence approaches.џўMention this shortcoming in the document. included.џўAnalysis and simulation material addressing 802.15 and 802.11G coexistance needs to be included.3LVALцi4 $ Ђ ( ™ A gžzW,эzЄiEН@ЪqElement ID 8 is already used by the hoppingџўElement ID 8 is already used by the hopping pattern parameters element in 802.11D-2001.џўShould there be an entry in the bottom right of the table?? or does the same value apply to both column 3 and other?џўThe long dash at the end of every figure or table reference is non-standard, annoying and seems to serve no useful purpose.џўT1 is also required in order to do an accurate calculation of the two periods.џўT1 could possibly be better expressed in 802.11 TU's.џўUndefined reference \cite{Bluet99}џўTypo: c7 should be -e^(j phi1+phi2). (c = [c1 c2 ... c8])џў5.5 Mbit/s CCK has already been specified in the IEEE standards so the reference to Halford[B13] can be removed.џўThe definition of GFSK signal can be found in most textbooks. It is not necessary to have it here.џўDo you need this Clause? Although Spectrum factor is shown in Figure 3, it doesn't seem to be used anywhere else.џўIt should read ""In the case of a 802.11b 1 Mbit/s chip ...""џўThe Eb/N0 is incorrect for a BER of 10-3.џўNeed to show BER values in table.џўStatement not technically correct.џўRxQuality is a much better indicator of 802.11b channel reception than packet error rate(PER), and is available in all commercial 802.11b chipsets. It should be used instead of PER for this function.џўIn 802.11b, RSSI is defined to be valid: 15.4.5.10.3 When generated This primitive shall be generated by the PMD when the DSSS PHY is in the receive state. It shall be continuously available to the PLCP, which, in turn, provides the parameter to the MAC entity. but it represents the energy at the moment in time when a valid 802.11b header checksum is received, not just anytime. You have to use the Energy Detect apparatus: 15.4.5.13 PMD_ED.indicate 15.4.5.13.1 Function This optional primitive, which is generated by the PMD, shall indicate to the PLCP layer that the receiver has detected RF energy indicated by the PMD_RSSI primitive that is above a predefined threshold.to measure as described in page 71 of the draft.џўAll of 10.4 is independent of 10.1-10.3, and should be presented as a separate clause.џўSimulation results for 1,2,5.5 and 11Mbps are necessary to form a recommendation to be practiced. The 1Mbps case is insufficient in practice.џўThese clauses belong in an informative annex to the Recommended Practice, as there is nothing within them to 'practice.'џўNulling filters can be used in WLAN systems to remove the WPAN interference given that the interferer does not hop during the WLAN packet. If the interferer hops, either into or out of, the WLAN bandwidth during the packet, the nulling filter transients must be carefully considered. A better approach would be to use a joint detection algorithm that does not require nulling filters.џўWould like to see priority to all network control and management functions, for example Beacons, Slave ACL, ID, FHS emphasized. Highest priority to be given to Master and AP. Then Slave and STA. After that: Synchronious communications such as SCO. Finally other data.џўThis document addresses only 802.11b, but 802.11g is being standardized for the 2.4 GHz ISM band and will be more susceptible to 802.15 interference at the higher speeds. Most new developments for the 2.4 GHz band will focus on 802.11g, and thus any coexistence development must be applicable to 802.11g.џўControl of legacy systems will not work when a legacy device is not in power save mode and wakes up to transmit a packet.џўThis Document gives details on 802.11B interference while current standardization in 2.4 GHz Band is covered in 802.11G Annex. The new modulation methods mentioned in 11G needs to be taken into consideration in the analysis on mutual interference and in proposed solutions.TЌў P Є № O Ќ f ЙWnЙ`­ь5kЧь"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.418TR@O.@JXO}{yyma]]YTPGG9 пЛы"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џўFigure 1226TЇ@O"€џўAdd figure for 5.5 Mbps 802.11b.XOЃЁŸŸqecc_TPGG9 пЛъ"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.4.2.32337E;@K €џўcorrect it.XOŽŒŒsgea]TPGG9 пПщ"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.4.2.22240Er@K€џўRemove the reference.XOš˜––sgea]TPGG9 пПш"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.4.1.119Ed@K €џўShorten it.XOŒŠˆˆocaa]TPGG9 пЛч"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.3.313Ts@KП@NXO}{yyma__[TPGG9 пЛц"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.3.6.2157E?@ K €џўcorrect it.XOŽŒŠŠqeca]TPGG9 пПх"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens05џў5.3.313EВ@O€џўRearrange them.XOŽŒŠŠma__[TPGG9 пЛфџўCarl R. Stevensonџўcarl.stevenson@ieee.orgџў610-965-8799џў610-704-2349 (may change before Sydney if new cellphone arrives in time)џўAgere Systems0000TRд@Oн@NXOТРООВІЂЂЂžš‹@2§Йу"0џўGreen, Patrickџўpatrick.green@amd.comџў408-749-4948џўAdvanced Micro Devices05џў5.4.32632TR+@ Ka@JXOŠˆ††znjfb[W??1 пПт"0џўGreen, Patrickџўpatrick.green@amd.comџў408-749-4948џўAdvanced Micro Devices05џўTable 71737E#@ K\@JXOŠˆ††znlhd[W??1 пПс"0џўGreen, Patrickџўpatrick.green@amd.comџў408-749-4948џўAdvanced Micro Devices04џў4.0633TR$@ K5@JXO†„‚‚vjfb`[W??1 пПр"0џўSmith, Daveџўdave_smith4@hp.comџў916-785-2639џўHewlett Packard10џў10.04050TR†@MЇ@JXO|zxxl`\XTNJ99+ пПп"0џўSmith, Daveџўdave_smith4@hp.comџў916-785-2639џўHewlett Packard10џў10.14149TRH@Mб@ JXO|zxxl`\XTNJ99+ пПо"0џўSmith, Daveџўdave_smith4@hp.comџў916-785-2639џўHewlett Packard10џў10.14146TR<@M”@ JXO|zxxl`\XTNJ99+ пПн"0џўSmith, Daveџўdave_smith4@hp.comџў916-785-2639џўHewlett Packard10џў10.1422TR@MЅ@ JXOzxvvj^ZXTNJ99+ пПм"0џўSmith, Daveџўdave_smith4@hp.comџў916-785-2639џўHewlett Packard10џў10.458TR€@M€џўRemove section 10.4XO‹‰‰h\XXTNJ99+ пЛлџўRichard H. Paineџўrichard.h.paine@boeing.comџў425-865-4921џў206-854-8199џўBoeing9џў9.23623T @M†@ JXO…ƒuigc_ZXPB4§ПкџўPeter Ecclesineџўpetere@ieee.orgџў408-527-0815џў925-443-2406џўCisco Systems12џў12.1.1.27110TЩ@ KE@ JXO‡…ƒƒwkieaWSD6(§ПйџўPeter Ecclesineџўpetere@ieee.orgџў408-527-0815џў925-443-2406џўCisco Systems12џў12.1.1.17054Tк@K@@JXO‡…ƒƒwkieaWSD6(§ПиџўPeter Ecclesineџўpetere@ieee.orgџў408-527-0815џў925-443-2406џўCisco Systems10џў10.4588EX@KА@JXO}}qeca]WSD6(§ПзџўPeter Ecclesineџўpetere@ieee.orgџў408-527-0815џў925-443-2406џўCisco Systems10џў10.4.26047E@K6@JXO…ƒuigc_WSD6(§П?LVALї w c'пYIn order for AWMA to work and to not burden low cost WPAN devices with the need for WLAN radios, the term Alternating Wirless Medium Access Control Area needsPTA can only work if the WPAN device also uses apative frequency џўPTA can only work if the WPAN device also uses apative frequency hopping to avoid interfering with other WLANs in the same location.џўIn order for AWMA to work and to not burden low cost WPAN devices with the need for WLAN radios, the term Alternating Wirless Medium Access Control Area needs to be defined (AWMACA). As such all devices entering into the AWMACA shall adopt the rules of the area. 1. All WPAN master devices must role-switch to a AWMA master in the area. 2. Only piconets with a AWMA master are allowed 3. IBSS networks must adopt the timing parameters and synchronize its clock with the AWMACA. 4. All WLANs in the AWMACA shall adopt the timing parameters and synchronize its clock with the AWMACA. џўAWMA is recommended for high density WLAN/WPAN area. As such there will be 3 non-overlapping WLANs in the same area. For AWMA to be effective, all the WLANs need to share the same time sharing parameters and have the same clock timing. A method needs to be developed that allows all the WLANs to coordinate timing.џўAWMA is the best of the collaborative techniques, but it has a few flaws. If an AP is AWMA capable then it should be able to determine the traffic flow of the WLAN and WPAN that it has control over. A method of dynamically changing the timing allocation needs to be created.џўDeterministic spectral excision is a poor recommended practice. 1. WLAN devices still interfere with WPAN deviced 2. WPAN devices still interference with other WLAN devices unless those device have scatternet capable WPAN receivers 3. WPAN device needs to be scatternet capable 4. Overlapping piconets will transmit simultaneously on different WPAN channels within the WLAN channel џўThere is a missing analysis in this section. The campus-wide ubiquitous coverage deployment of 802.11b (at least b, if not 802.11 1Mbps DSSS and 802.11 2Mbps DSSS) is not addressed and needs to be. Ubiqitous coverage campuses in enterprises like Boeing and Microsoft are becoming commonplace. This continuous non-collaborative environment includes the need to use 802.11b channelization for alternating cells. Take the instance of several ubiquitous-coverage 802.11b Boeing campuses - overlapping cells are the norm and full channelization is in effect in those campuses that have ubiquitous coverage. The analysis of this environment with bleeding between cells needs to be in the document or its value is diminished. What is the recommended practice for the campus ubiquitous coverage environment. In addition, consider the conference room. In that conference room with perhaps 30 people, with a mix of Bluetooth and 802.11b, what studies have been done to show and model the effects of the dense use of 2.4GHz radios. What is the recommended practice for the conference room model? Also consider the effects of being on an airplane and half of the airplane's passengers use mobile computing devices with half of those using Bluetooth and half using 802.11b.LVAL# d Ž Ѕ|ј9Include analysis and simulation material addressing the 802.15 and 802.11G coexistance. InclџўInclude analysis and simulation material addressing the 802.15 and 802.11G coexistance. Include outcome of those analysis and simulation in proposed schemes for interference reduction.џў Use a non-allocated element ID, taking into account those presently assigned for provisional use in the TGe, TGh, and TGi drafts.џўUpdate the simulation-based analyses of 802.11b to take account of short preamble vs. long preamble and to consider whether the susceptibility/interference source characteristics of PBCC modulation are the same as CCK or not. If not include analysis of PBCC as well in the appropriate sections.џўModify these statements to indicate that ARQ improves reliability, not insures reliability, and remove the statement about little chance of data loss, replacing it with a quantative statement of simulated chance thereof if desired.џўUpdate the simulation-based analyses of 802.11(b) traffic to also include error analyses with PCF traffic. I believe the OPNET 802.11 model now includes a point coordinator. If not, you should be able to get a copy of the one developed by the TGe simulation subgroup from Matthew Sherman of AT&T and/or Sunghyun Choi of Phillips, both of whom worked on developing that model and have presented results of simulations performed using that model in submissions to TGe.џўThis Clause needs some clarification. Add another Figure or Table showing the BER with different frequency offsets (spectrum factors) with a fixed value of transmit power and/or path loss.џўProvide a quantifiable definition of "coexistence" and methods of evaluation of the interactions between ALL 802 wireless standards that share a common frequency band, allowing those combinations of systems to be evaluated in a sensible, measurable manner and defining what is "good enough" to constitute acceptable coexistence and what is not. Include analysis and simulation models of 802.11g, 802.15.3, 802.15.4 so that the COMPLETE coexistence picture of current and "in development" 802 standards in the 2.4 GHz band can be evaluated. Propose (or, in the case of "in development" standards, insist that the developing workgroups propose and provide) coexistence mechanisms for ALL combinations of systems, with the onus on the "newcomer" to propose and provide coexistence mechanisms that can be shown to provide reasonable protection to incumbent systems, accoarding to the aforementioned definition of "what is good enough" to constitute acceptable coexistence.OLVAL , z г П 0 aкWNqComment: Ignoring the PCF completely in the analysis of 802.11(b) traffic patterns brings many of the conclusions into question. The PCF traffic patterns are considerably different than the ones discussed in subsequent sections, and whџўComment: Ignoring the PCF completely in the analysis of 802.11(b) traffic patterns brings many of the conclusions into question. The PCF traffic patterns are considerably different than the ones discussed in subsequent sections, and while point-coordinated networks are relatively uncommon today, the HCF in the MAC extensions for QoS being developed in TGe will have many characteristics in common with PCF traffic, including multi-MPDU bursts separated by SIFS intervals.џўThe structure and language confuse me. Why has it been decided that there are three coexistence mechanisms? Surely we have two in Non-collaborative (AFH and APSS) and two (SCO over ACL priority and TDMA) in Collaborative. How is it that we describe these as 3?џўThe text lists three models (RF, MAC, PHY) and says 'developed in OPNET and ANSI C, respectively"". I can't parse this sentence.џўThe Editor's note says 2 Mbit/s is not included, yet there are simulatiosn for this rate and the document seems to apply to 2 Mbit/s.џўThe simulation tool OPNET is mentioned several times throughout the draft. I am just wondering whether it is appropriate and conforms to the IEEE rules to refer to a commercial tool within this document.џўThe proposed control of legacy systems will not work when a legacy device is operating in power save mode and wakes up to transmit a packet.џўTo better compare performance degradation of 802.11b (11 and 5.5 Mbps) due to Bluetooth interference, there should be a comparison using the same receiver architecture (ie, optimal receiver - correlator). It is hard to do the comparison with different sub-optimal receivers.џўThere should be a comparison for 5.5 Mbps 802.11b as well because the sub-optimal receiver is used instead of the optimal one. Comparison with QPSK is not necessary.џўThe transmit and receive masks (Clause 5.3.5) should appear before Spectrum factor (Clause 5.3.3) because the spectrum factor is calculated using Table 6 given in Clause 5.3.5.џўWhile this document does reasonable job of characterizing interference potential between 802.11 FH and 802.11b WLANs and 802.15.1 (Bluetooth) WPANs and proposing some methods of improving coexistence, I think it falls short of what is currently needed in the following respects: First, it will be obsolete in short order because it does not address the proposed 802.11g extension at all. Second, neither does it address 802.15.3 WPANs. Third, neither does it address 802.15.4 WPANs. Finally, while it offers a definition of "coexistence," that definition is very "fuzzy" and essentially ignores the pressing need to quantify just what constitutes acceptable coexistence between systems and what does not. What is needed is a "figure of merit" or "measure of goodness" that defines both how much a system is affected by other systems and how much it affects them, and that should apply to ALL 802 wireless standards that operate in a given band, not just a subset.'OmН  ) ‰ э & ; fДќI‚ШI‡ё]ћџўWillem Mulderџўwmulder@agere.comџў+31 3060 97526џўAgere Systems0000TŒ@Q@JXOmkii]QOOOKG88(нЙњџўWillem Mulderџўwmulder@agere.comџў+31 3060 97526џўAgere Systems0000TRШ@QП@NXOomkk_SOOOKG88(нЙљџўMichael Fischerџўmfischer@choicemicro.comџў+1-210-492-6036џў+1-210-240-4096џўIntersil Corp.10џў10.2.2.6.34818TRY@K„@NXO›™——‹{wsgcSB1§ПјџўMichael Fischerџўmfischer@choicemicro.comџў+1-210-492-6036џў+1-210-240-4096џўIntersil Corp.5џў5.4.221џў6-11TRИ@Q)@NXO–”’’†zvplecSB1§ПїџўMichael Fischerџўmfischer@choicemicro.comџў+1-210-492-6036џў+1-210-240-4096џўIntersil Corp.4џў4.1.17џў12-13 & 42-43Tk@Qщ@NXO›™——‹}nlecSB1§ПіџўMichael Fischerџўmfischer@choicemicro.comџў+1-210-492-6036џў+1-210-240-4096џўIntersil Corp.4џў4.16џў27-29TRн@ Oж@NXO“‘ƒwsljecSB1§Пѕ"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems5џў5.3.3 Table 31321Ev@K €џўClarifyXO žœœ‡{yuqb`Q@/ џПє"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems00џўmultipleE}@K/@JXOŒŠˆˆ|pnnnd`Q@/ џЙѓ"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems04џў4.3.29џў3233E @O@@JXO‘usmkd`Q@/ џПђ"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems4џў4.2826Eƒ@Oe@JXO‹‰‡‡{omigb`Q@/ џПё"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems044.64E€џўrepeated period€џўdelete one periodXOЎЌЊЊ‹nljhd`Q@/ џП№"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems04џў4.1.3749E!€џў""Both"" should not be repeated€џўremove second bothXOФТРР sqmkd`Q@/ џПя"0џўSkellern, Davidџўskellern@cisco.comџў+1 408 527 0776џў+61 409 468 404џўCisco Systems1џў1.127E‡@O€џўRemove editor's note.XO žœœymkigb`Q@/ џПџўGeorg Dickmannџўgeorg.dickmann@bridgeco.netџў+41 1 8023349џўBridgeCo AG0000EЯ@On@JXOusqqeYWWWSOBB3нЙџџўWillem Mulderџўwmulder@agere.comџў+31 3060 97526џўAgere Systems10џў10.2.45021T@O#@JXOywuui][WSKG88(нПўџўWillem Mulderџўwmulder@agere.comџў+31 3060 97526џўAgere Systems10џў10.2.2.6.14740T€џўT1 is essemntial information.€џўAdd T1 as extra field.XOДВААŒa_[WKG88(нП§џўWillem Mulderџўwmulder@agere.comџў+31 3060 97526џўAgere Systems10џў10.2.2.143џў453TQ@K€џўAdd T1 as parameter.XO’ŽŽl`^YUKG88(нПќџўWillem Mulderџўwmulder@agere.comџў+31 3060 97526џўAgere Systems10џў10.24247T7@K€џўExpress T1 in TUXO‰‡……g[YUQKG88(нПю"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens11џўFigure 43, 45, 46џў63-66E €џўThese Figures are hard to read€џўreplace them.XOЛЙЗЗœpnngTPGG9 пЛэ"0џўChindapol, Aikџўaik.chindapol@icm.siemens.comџў858-521-3546џўSiemens06џў6.0298E$@K €џўCorrect it.XOŠˆ††ma_]YTPGG9 пПs LVAL• н  ‰ The document only addresses 802.11B interference while current standardization in the The document lacks a systematic overview of scenarios of mutual inteџўThe document lacks a systematic overview of scenarios of mutual interference and which solutions address which scenario of interference.џўThe document only addresses 802.11B interference while current standardization in the 2.4 GHz band is covered in the 802.11G annex. The new modulation schemes proposed in 11G need to be taken into account in the analysis on mutual interference and in proposed solutions. Any new development in this band is likely to address 802.11G rather than just 11B. Any investment in collaborative schemes must have applicability for 11G to be of interest.џўNeither the short preamble option of 802.11b (which ought to improve the mutual interference situation when used) nor the PBCC modulation option of 802.11b are mentioned or analyzed.џўThe statements that ARQ "insures" reliable delivery is an overstatement, even in the absense of interference from 802.15.1 transmissions. What the ARQ in the 802.11 MAC does is to attempt to make the incidence of packet loss sufficiently low that the higher layer protocols can treat 802.11 as a LAN rather than as some other sort of intermediate-s the assertions that there is "little chance of data loss" is highly questionable, especially at lower 802.11 data rates such as 1 or 2Mb/s because the probablility of 802.15.1 hops within the 22MHz occupied bandwidth of 802.11 during each frame transmission attempt. яYAccessNSSY ˜Y DataIDƒџџџџџџџџџџџџџџџџџџSX.Џ‰YџџџџAOIndexџџЛv1№KR[  €€€@  Т ЈТ”ЧЪ‡ВwcctLLS@LL0јEИ№Eџ№cpeАd cфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEфіEАg hџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ0f№fPш їEџџџџџџџџџўџџџџџMSysAccountsћяИXђџџџџџџџџџџџџ?ЋрЯHшF4ўE 0ўEџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџP@ #  3њИXђ!!АJEРFlFFФFpFFШFžšKR[аЯрЁБс>ўџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ§џџџ ўџџџ ўџџџ ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџRoot Entryџџџџџџџџ EЮ Т€ VBAџџџџџџџџEЮ ТEЮ ТVBAProjectџџџџEЮ ТEЮ ТVBAџџџџџџџџEЮ ТEЮ Тdirџџџџџџџџт_VBA_PROJECTџџџџџџџџџџџџ PROJECTџџџџ-+PROJECTwmџџџџџџџџџџџџ2ўџџџ  !"#$%&'()*+,ўџџџ./01ўџџџўџџџўџџџўџџџўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџоБ€0* pH‚dфlb14_r0Q(@=­ l €пЩ@> J"< DAO>BDA O ™*\G{0002 5E01-0C  0046}#5.0#0#D:\Program Files€\Common Microsoft Shared\w350.DLL#‡ 3.51 Object Library€HUstdole>‚fstdole5^f€\€^04V3„[W-^2^WINNT\Sys@tem32\ƒ12.tlb#OLE Automat˜ion/СVBIDE> VBIDдECЗ€­€C0E157ŸC5.B3яPVBA\Р6E6EXT.OLBHRVisual Basic for Applic1s ExtensibiliИty РР+€‚›ˆТ7Ў‚Ьamџ  фњ*\G{000204EF-0000-0000-C000-000000000046}#4.0#9#D:\PROGRA~1\COMMON~1\MICROS~1\VBA\VBA6\VBE6.DLL#Visual Basic For Applications*\G{4AFFC9A0-5F99-101B-AF4E-00AA003F0F07}#9.0#0#D:\Program Files\Microsoft Office2000\Office\msacc9.olb#Microsoft Access 9.0 Object Library*\G{00025E01-0000-0000-C000-000000000046}#5.0#0#D:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL#Microsoft DAO 3.51 Object LibraryИ*\G{00020430-0žšKR[000-0000-C000-000000000046}#2.0#0#D:\WINNT\System32\stdole2.tlb#OLE AutomationZ*\G{0002E157-0000-0000-C000-000000000046}#5.3#0#D:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB#Microsoft Visual Basic for Applications Extensibility 5.3 џџџџџџџџпЩ@>џџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ7Ўџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџx€ џ%AccessVBAїтWin16С~Win32MacГВVBA6­#lb14_r0uЪDAOž‚stdole“`VBIDEAџџџHџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџџ џџџџ џџџџџџ ID="{7C6F6A2F-E8D8-4835-9DFD-B0A5435629D5}" Name="lb14_r0" HelpContextID="0" VersionCompatible32="393222000" CMG="8183828286828682868286" DPB="020001828383838383" GC="8381800500060006FF" [Host Extender Info] &H00000001={3832D640-CF90-11CF-8E43-00A0C911005A};VBE;&H00000000 [Workspace] ijфMSysDbAcessVBADataџџџџџџџџџџџџ3Forms  џџџџEЮ ТEЮ ТCmdbarsџџџџџџџџџџџџEЮ ТEЮ ТModules џџџџEЮ ТEЮ ТReportsџџџџџџџџџџџџEЮ ТEЮ ТScripts џџџџEЮ ТEЮ ТPropDataџџџџџџџџџџџџ4DatabasesEЮ ТEЮ Т0џџџџEЮ ТEЮ ТBlob џџџџџџџџџџџџўџџџDirDataџџџџџџџџџџџџ5CustomGroupsџџџџџџџџEЮ ТEЮ ТDataAccessPages џџџџџџџџџџџџEЮ ТEЮ ТџџџџџџџџџџџџžšKR[џџџџџџџџџџџџџџџџџџџџџџџџžšќ R€T€U€V€WonnectDatabaseDateCreateDateUpdate FlagsForeignNameIdLvLvExtraLvModule LvPropName OwnerParentIdRmtInfoLongRmtInfoShortTypeƒџџџџnџџџџiџџџџџџџџфіEƒџџџџEџџіџџфџџџџEџџіџџфџџфіEYџџџџYџџџџIdParentIdName        џџ‡ qYnnect NZZY Y  Y €Y Y Y Y Y AttributesDataTypeFieldNameIndexTypeSkipColumn SpecID Start WidthƒџџnџџџџCџџџџџџџџtџџZ[€ƒџџџџџџIџџџџeџџџџџџџZ\us‰YџџџџYџџџџ Index1PrimaryKeyџџжЛv1ь Y      €€€€€€R Yм YN  ^^ Y џџY Y Y  Y $ Y FY Y $ Y $€Y  Y  F Y  $ Y  $DateDelim"DateFourDigitYear DateLeadingZerosDateOrderDecimalPointFieldSeparatorFileType SpecIDSpecNameSpecTypeStartRowTextDelimTimeDelimƒџџџџ$џџџџFџџџџ$џџџџFџџ^_F$‰YџџџџPrimaryKeyџџЛv1€ ]љIэvcP=*Г z№ н Ъ З @ -  Ѓ  } j ѓ р Э К C 0  ї € m Z G а Н Њ — њƒp]цг\хв[HбОЋ4!—„ њƒp]цгРI6#Ќ™  Y oў Y 8ўY  Y ўAttributeExpressionFlagLvExtra Name1 Name2ObjectId Orderƒ €џџ{‹  €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp  €џџz‹  €џџ{‹  €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp  €џџz‹ {‹ xQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp z‹ {‹ xQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp z‹ @xOVKНлS$4ХdІIhЫqЖ•4 RЊС#qшфFс† ƒaгЧ6eeŠС“VЉ:К‹…бцсЋ*Б‚$;ђЖыƒмe!…YžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp {‹ TxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp z‹ ]ў {‹ ]ў xQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp ]ў z‹ Yў {‹ Yў xQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp Yў z‹ TxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp z‹ TxOVKНлS$4ХdІIhЫqЖ•4 RЊС#qшфFс† ƒaгЧ6eeŠС“VЉ:К‹…бцсЋ*Б‚$;ђЖыƒмe!…YžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp RџџxOVKНлS$4ХdІIhЫqЖ•4 RЊС#qшфFс† ƒaгЧ6eeŠС“VЉ:К‹…бцсЋ*Б‚$;ђЖыƒмe!…YžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp Rџџ{‹ RџўxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp Rџџz‹ џў{‹ џўxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp џўz‹  €џџ{‹  €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp  €џџz‹ €{‹ €{‹ xQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp {‹ z‹ џў{‹ џўxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp џўz‹ ў{Ž €џџ{Ž €џџz‹ €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp €џџ{‹ €џџ{Ž €џџz‹ €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp €џџ{‹ €џџ{Ž €џџz‹ €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp €џџ{‹ џџ{‹ џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp z‹ ў{Ž €џџ{Ž €џџz‹ €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp €џџ{‹ €џџ{Ž €џџz‹ €џџxQдї(^–|4ХdІIhЫІнcI`Ч)бlюzџ„Њ ƒaгЧ6eeŠС“VЉ:К‹…бцсt%uк˜+Є0Ž:nЎ5оžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp €џџ{‹ z‹ €џџ{Ž €џџz‹ €џџxOVKНлS$4ХdІIhЫqЖ•4 RЊС#qшфFс† ƒaгЧ6eeŠС“VЉ:К‹…бцсЋ*Б‚$;ђЖыƒмe!…YžcІKŒHъuM•\‰f-;?[­*њЏ‘ˆКШp €џџ{‹ JLVALа $ b @€ @€ @€ @€````````` ` ` ` ````````````````` ```ЪОџџџџџџџџџџџџџџџџџџџџlb34_r0clause_sortЪОџџџџџџџџџџџџџџџџџџџџlb34_r0clause_sort#џџџџ^Щ3ўџz/џџџџV&q lb34_r0џџџџM &†qlb34_r0(’Gџџџџc&†qlb34_r0LVALњtЅ ЅЭж 4 z№ н Ъ З @ -  Ѓ  } j ѓ р Э К C 0  ї € m Z G MR2Ž€ FilterOrderByOrderByOnColumnWidthColumnOrderColumnHiddenValidationRuleValidationTextDescription FormatInputMaskCaptionDefaultValueRequiredAllowZeroLengthDisplayControlDecimalPlacesA , $lb34_r0.Autonumber[CommentID џџџџ      mc CommenterName џџџџ      me"CommenterEmail џџџџ      me"CommenterPhone щ      maCommenterFax џџџџ      m_CommenterCo џџџџ      m[Subclause џџџџ      m_CommentType џџџџ      mYResponse џџџџ      mc CommentStatus џџџџ      me"ResponseStatus џџџџ      mMComment >     ]$SuggestedRemedy      AAutonumber џџџџ  U Clause џџџџ      mQPage џџџџ      mQLine џџџџ      mMR2Ь€RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOnColumnWidthColumnHidden1  <  E*$lb34_r0.Autonumber X ="lb34_r0.Clause   9lb34_r0.Page v 9lb34_r0.Line С G,&lb34_r0.CommentType б ?$lb34_r0.Comment ю O4.lb34_r0.SuggestedRemedy +/ MR2š€RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOn1    MR2š€RecordLocksODBCTimeoutMaxRecordsRecordsetType FilterOrderByOrderByOn1    MR20€ Title AuthorCompanyR lb14_r0 David Cypher NISTMR2Д€AccessVersion Build6Track Name AutoCorrect Info0Perform Name AutoCorrectCpgConversionN 08.50 Ÿ   ф