Presentation is loading. Please wait.

Presentation is loading. Please wait.

Comments to 802_15 from 802_11 on Pending PARs November Plenary

Similar presentations


Presentation on theme: "Comments to 802_15 from 802_11 on Pending PARs November Plenary"— Presentation transcript:

1 Comments to 802_15 from 802_11 on Pending PARs November Plenary
doc.: IEEE /1351r0 November 2008 Comments to 802_15 from 802_11 on Pending PARs November Plenary Date: Authors: Jon Rosdahl, CSR Jon Rosdahl, CSR

2 November 2008 doc.: IEEE /1351r0 November 2008 Abstract At the November Plenary, proposed 3 new PARS for 802 EC approval. This File is extracted from r1 that lists those PARs and those from other WGs for discussion. This submission attempts to provide the comments from members regarding the proposed PARs. It should be noted that WG authorized a group to collect and provide the feedback on the proposed PARs. R1 of this file has been corrected to clarify a discrepancy that was noted by after the original file was posted. Jon Rosdahl, CSR Jon Rosdahl, CSR

3 November 2008 Proposed PARs (1) IEEE f Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low Rate Wireless Personal Area Networks (WPANs) - Amendment: Active RFID System PHY Draft PAR [ Draft 5C [ Jon Rosdahl, CSR

4 November 2008 Proposed PARs (2) IEEE f Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications for Low Rate Wireless Personal Area Networks (WPANs) - Amendment: Physical Layer (PHY) Specifications for Low Data Rate Wireless Neighborhood Area Networks (WNAN) Draft PAR [ Draft 5C [ Jon Rosdahl, CSR

5 November 2008 Proposed PARs (3) IEEE PHY and MAC standard for short-range wireless optical communication using visible light Draft PAR [ Draft 5C [ Jon Rosdahl, CSR

6 802.15.4 RFID PAR and 5C Comments Received from 802.11
November 2008 RFID PAR and 5C Comments Received from The RFID PAR & 5C are incomplete and should not be approved because: The 5C & PAR incorrectly claim there is no existing international standard  The 5C & PAR need to include evidence that there is user demand for yet another RFID standard  The 5C & PAR need explain what technical deficiencies of existing systems the proposed standard will address  The 5C & PAR need to provide a better justification of technical feasibility for a unified standard that addresses the requirements of all market segments The 5C & PAR need to acknowledge the use of in this space today and explain why a based solution will be significantly better Jon Rosdahl, CSR

7 802.15.4 RFID PAR and 5C Comments (2)
November 2008 RFID PAR and 5C Comments (2) The RFID 5C & PAR incorrectly claim there is no existing international standard The 5C asserts that there is a need for an international standard for active RFID, and the PAR asserts that is there in no international standard. However, the 5C indicates that an international standard does exist, and even quotes the number of an ISO standard.  There are also other quasi international standards in this space that need to be acknowledged explicitly in the PAR The 5C and PAR need to be modified to correct this error. Is it the intention to state that there are no suitable international standards? If so, then such a statement needs justification in the PAR. Jon Rosdahl, CSR

8 802.15.4 RFID PAR and 5C Comments (3)
November 2008 RFID PAR and 5C Comments (3) The RFID 5C & PAR need to include evidence that there is user demand for yet another RFID standard. The 5C and PAR assert that active RFID tags have not been successful so far because there are too many options available, which has reduced interoperability and economies of scale. That may be true  However, the PAR & 5C do not explain how the development of yet another standard will solve this problem, particularly in a context where does not have much scale today, certainly in comparison with, say, The 5C and PAR need to be modified to include evidence that there is user demand for yet another standard. Jon Rosdahl, CSR

9 802.15.4 RFID PAR and 5C Comments (4)
November 2008 RFID PAR and 5C Comments (4) The RFID 5C & PAR need to explain what technical deficiencies of the existing systems the proposed standard will address. One reason that would justify a new standard is that all the existing mechanisms are missing functionality from a technical perspective If this is not the case, why not just submit one of the existing mechanisms to EPCGlobal, IEEE or ISO? However, the PAR & 5C do not address the issue of whether existing systems are technically deficient The PAR & 5C need to be modified to explain what technical deficiencies of existing systems the proposed standard will address  Jon Rosdahl, CSR

10 802.15.4 RFID PAR and 5C Comments (5)
November 2008 RFID PAR and 5C Comments (5) The RFID 5C & PAR need to provide a better justification of feasibility for a unified standard that addresses the requirements of all market segments One reason that the active RFID market is segmented today is that each market segment has different requirements However, the 5C and PAR assume that a unified standard can achieve the goals of every market segment It incorrectly bases technical feasibility for the unified standard on an argument that each of the existing standards are technically feasible It is possible that the market requirements for the various segments are contradictory. The 5C and PAR need to demonstrate technical feasibility for the unified standard, not just a subset Jon Rosdahl, CSR

11 802.15.4 RFID PAR and 5C Comments (6)
November 2008 RFID PAR and 5C Comments (6) The RFID 5C & PAR need to acknowledge the use of in this space today and explain why a based solution will be significantly better It is asserted in the 5C that the proposed active RFID functionality is not addressed in any existing 802 standard. However, there is a growing opinion among some in the industry that based systems could dominate this space There are already several start-ups that are showing Wi-Fi based sensor chips with very low power and cost – and of course with Wi-Fi you don’t require a separate infrastructure. The PAR & 5C needs to be modified to recognize the existing use of in the active tag space, and explain why offers significant benefits over   The answer should account for the fact that based solutions exist today, whereas based solutions may not exist for some years (5 years?) Jon Rosdahl, CSR

12 802.15 NAN PAR & 5C Comments Received from 802.11
November 2008 NAN PAR & 5C Comments Received from 1) This amendment proposes operation within at least the 2.4 GHz band, including ranges of up to 5 km with omni antennas, and simultaneous operation for at least 3 co-location orthogonal networks. Further, at the NAN tutorial proponents advocated a frequency hopping PHY technology. In 8.1, a transmit power up to 1W is indicated. Yet 2.4 GHz is a crowded band with dense WLAN deployments and regular Bluetooth usage, each offering tremendous value to their users. We have seen that coexistence with frequency hoppers is difficult as they consume the whole band making frequency planning impossible. Jon Rosdahl, CSR

13 November 2008 NAN PAR & 5C Comments (2) This Page contains comments that are from a member of , but the broader has agreed with the coexistence statement as listed on slide 15. Accordingly, coexistence is a grave concern: the PAR is for a latecomer to a mature band, the technology's impact will be at high TX power and over a wide area, and the technology's proponents favor a technology with poor coexistence characteristics. In this context, the language in the scope "This amendment also addresses coexistence with other 802 wireless standards operating in the same bands." is inadequately weak. The 2.4 GHz band should be removed from the PAR scope, or the PAR language should be strengthened. Proposed substitute language is "Devices complying with this amendment shall minimally impact the operation of and devices, along with other 802 wireless devices, already operating in the same bands.“ Jon Rosdahl, CSR

14 November 2008 NAN PAR & 5C Comments (3) 2) The PAR does not acknowledge that either or is likely a better home for this work than a) 5km range is wildly outside the scope of Personal Area Networking (through 11y) and both have far greater expertise in outdoor channel models, and systems for same. b) Contrary to 5.5 "The standards have been optimized for high data rates along with support for star network topologies with centralized control.", is already providing a mesh amendment that addresses this assertion also has work in this area. Jon Rosdahl, CSR

15 November 2008 NAN PAR & 5C Comments (4) Suggest that a change to the last sentence of PAR 5.2 similarly to what the EC has requested in the past of other groups indicating that the phrase “it addresses” is not sufficient: From: “This amendment also addresses coexistence with other 802 wireless standards operating in the same bands.” To: “This amendment also provides mechanisms that enable coexistence with other systems in the band including IEEE 802 devices operating the the same band.” Jon Rosdahl, CSR

16 November 2008 NAN PAR & 5C Comments (5) When the tutorial discussions were held, it seemed that the use of the 700 MHz ( e.g. Whitespaces) to 1GHz bands provided the range/power that seemed most reasonable, but in the 2.4 GHz band, the range/power does not seem practical. Why not focus the group on the 700 to 900 MHz bands? If the new devices use the 2.4GHz band, how will they coexist with the existing devices in the band? If the new devices use 2.4GHz, why develop a new MAC and PHY? There is a FH PHY defined in the standard, as well as a DSS PHY, so maybe a new amendment would be more appropriate? Jon Rosdahl, CSR

17 802.15.7 PAR Comments Received from 802.11
November 2008 PAR Comments Received from RF stands for Radio Frequencies, as an acronym, you should spell it out on first usage in 5.5 purpose. Why call out RF interference when you state that the band in use is outside the RF band? Visible light is free of non-visible interference, but that should not be used in the definition of the scope and purpose. The Scope and Purpose should deal specifically with the stated spectrum and not counter examples. All the semicolons in the scope statement should be commas. Have you considered the Mirror in the Middle attack?  Jon Rosdahl, CSR


Download ppt "Comments to 802_15 from 802_11 on Pending PARs November Plenary"

Similar presentations


Ads by Google