WPC 2B!J W3|xCourierTimes RomanCourier Bold @Apple Laserwriter PlusAPLASPLU.PRSx6X@Ka~2)9I23|xCourierTimes RomanusAPLASPLU.PRSx6X@KhhhhuфX@"S^*8DSS888S^*8*.SSSSSSSSSS..^^^Jxooxf]xx8Axfxx]xo]fxxxxf8.8NS8JSJSJ8SS..S.SSSS8A.SSxSSJP!PZ8*88888ooooo888888oo8S.oxJxJxJxJxJooJfJfJfJfJ8.8.8.8.xSxSxSxSxSxSxSxSxSxSxJxSxSxSxSooooxoxJxJoJoJoJoJxSfJfJfJfJxSxoxSxSxSxSxSxS8S8S888SooA8xSf.f8f8f8f.xSxoxSxSxSxSxo8o8o8]A]A]A]Af8f8f8xoxSxSxSxoxSxxSfJfJK:oo*oLS8JSSSSoS.4ooSooSoooooJJS88ooSSoooooooooooo]]ooooo8Jooooooooooot^\\\oooooooooooooooo^oeeeoooooo*oooCoo\.owR)Eooooooooooooooooowooooooooooooooooonooooooooooooooooooooooooo\1oooooooofoooooooooooy\r\o`{ooooooooooooooooooov\r\rCourierTimes RomanCourier BoldTimes Roman Bold2` CC11-08-91 06:43a  +sgxxxX~x  @u@\E*e7\4 PCsgxxxX~x  @[u@\E*e7\4 PC0sgxxxXpx  `Zy[:!py4 p(AC1sgxxxX~x  @[u@\E*e7\4 PC0sgxxxXpx  `dCdCdCCCdNCdz8zCzCz8dddddCCCoNoNoNoNzCzCdddddzYzYNF2[dCYddddd7>d<d<$YYdCCddooCYd<d<$YYdCCddooCYoodoodooo$ooYYdCCooddoooooooooooooooooooCYoooooooooootqnnnooooooooooooooooqoyyyoooooo2oooPoon7oc1Rooooooooooooooooooooooooooooooooooooooooooooooooooooooooooon1oooooooozooooooooooonnosooooooooooooooooooonsgxxxX~x  @[u@\E*e7\4 PC0sgxxxXpx  `\Zy[:!py4 p(ACMoS2Xdo4 PC2ZsgxxxX~x  @[u@\E*e7\4 PC0sgxxxXpx  `\Zy[:!py4 p(AC]MoS2Xdo4 PC\]  @sgxxxX~x  @[u@\E*e7\4 PC0sgxxxXpx  `\Zy[:!py4 p(AC]MoS2Xdo4 PC\]  @0R]  ` February, 1992 Doc: IEEE P802.1192/19 bis 20 k920 #]\  PCe7P#Printed: Feb 06,1992'Page `.(#6By: Wim Diepstraten  ug    p4  p(AC  $IEEE 802.11 Wireless Access Method and Physical Layer Specifications 2 Title:XIEEE Requirements Document comments on doc # 92/01 (#  o\  PCd  Presented by: X X` X Wim Diepstraten(#  `  NCR SEUtrecht  `  NCR/AT&T Network Product Group  `  Nieuwegein  `  Netherlands  `  31340276482 (V)  `  31340239125 (Fax)  `  Wim.Diepstraten@Utrecht.ncr.com (Email) 2 Abstract:` The following is a list of comments, questions or remarks on the IEEE Project 802.11 "Wireless Local Area Network Requirements" document.(#` C1:XIntroduction(# Q  How living is the document after signoff.  .` Synchronous exported services to be specified.(#` Q X Should several conformance levels be specified, to cover for instance different moving speed ranges.(# p4:X Need a reference MSDU size specification for the transfer delay numbers. Note: 2 msec transfer delay for a 64 byte octet is much different from a 2 msec transfer delay for a 1024 octet MSDu size. Suggest reference to be 128 octets, as suggested in page 24.(# p4X Is it correct that "Service Initiation Time" is only applicable for connection oriented services?(#   p7X Clarification of "Interference distance" needed. Is this the "SignaltoInterference" ratio (SIR) in dB?(# X We need to have a term for the SIR at which a good service quality can be obtained. (# p10XThe Multicast/Broadcast transfer reliability cannot be guaranteed in a wireless environment. When is this deviation from the general 802 MAC service definition to be covered and how?(# X QX` What kind of applications use group/Multicast addressing?(#` p11:XHow about IEEE 802.9 IVD LAN draft standard reference?(# C2:General Requirements p14:XWhat are distribution system standards for Sync traffic? No 802 equivalent standard available?(# p14:XSecurity/Integrity(# X The method used should be worldwide applicable without restrictions.(# p14:XIsn't "Roaming" support a to be specified general requirement?(# p15:XShouldn't the 802.2 "Bridge" functions be limited to "single leave" support only. We should prevent bridging from one network to another via the wireless medium.(# X Q: X` What should this mean for a Directional Antenna pointtopoint link and its coexistence with the 802.11 LAN.(#` p15:XWhat kind of "Bridge" functionality is supported? I Would expect that the "Access Point" would use a MAC Bridge approach.(# p15:XPerhaps delete the "Complete Architectural Scope" (Fig 2.2) from this document altogether to keep it general enough. To cover also sync and bridging services, much more pictures are needed.(#   C3:Media Access Control Layer X Sections 3.2.1 through 3.2.3 should better be deleted, because they relate to implementation, rather than requirements.(# X Also section 3.3 could better be deleted because it does relate too much to implementation.(# p19:XAll "To be supplied" sections should be specified before "ballot".(# p20:XShouldn't support for the different NOS's and protocol stacks be a prime requirement? Why is NDIS and ODI referenced here? They are more interface specifications than NOS protocol stacks.(# p23:XDon't see the median jitter conclusion?(# p25:XSync maximum transfer delay of 10 msec is equal to the nominal delay specification. I would expect 20 msec.(# p27:XInternetworking: Does this sufficiently cover the Sync internetworking requirements. Suggested extension:(# X "belonging to a given LAN. However, this requirement does not apply to interconnection with other networks e.g. those using ISDN protocol stacks." (JK)(# p28:Add Arcnet  Also SNMP is a industry standard C4 Physical Media Layer: p29:XSuggest to delete end p29, p30 and p31, because they are not requirements, but more implementation details.(# p32:Delete 4.3.2 if possible X Delete 4.3.4 because 18 GHz requires license, so is not in accordance with the general requirements.(#  \  Appendices: A:X Education: Video anticipated for "Field Study", why then not for other education applications.(# B: Finance: Only trading floor application described. X Need description of Bank/Branch transaction applications, or at least a reference to possible "office" requirements covering this type of traffic characteristic.(# C:X Industrial: No Comments (# D: Medical: No Comments E: Meetings: No Comments F:X Office:(# X ©X` F2.3 SNA and DECNET are no NOS's. Suggest to generalize to mention support for different protocol stacks.(#`  ` Why no Banyan support?(#` X ©X` F2.6 use # of stations per hectare(#` G:X Retail:(#  ` Change "enterprise" to premises/store(#`  ` Need hypermarket application with much higher station density.(#`  ` Need to cover different (future) applications related to automatic shelf labeling. This is documented in contribution # IEEE P802.1192/15 (#` H: Warehousing: No comments I: Multi Media: No comments   Issue's in deleted sections: p18:Xend of section 3.2.2. Why full duplex characteristic required?(# p19:XQuality of Service info should also include receive level information.(# p20:XTxClock should be supplied by PHY. Usually needed for synchronous sampled systems to keep sampling clock in sync with the bit and symbol clocks.(# p31:X©X` Point 5 statement is not clear in defining the "Interference distance".(#`  ` Point 9 should be much stronger. A measurement of interference level at one station is no indicator of the interference level of another station.(#` p32:XSection 4.3.3 item 1. I don't understand why item 9 can be removed from the general PHY characteristics.