70 likes | 80 Views
This amendment enables the use of Sub-GHz bands in various regions and aligns channel parameters with regional requirements for IEEE Std 802.15.4-2015. It includes MAC changes for regional compliance.
E N D
802.15.4v PAR and CSD comments March 15, 2015 Kunal Shah SG4v Chair Kunal Shah (Silver Spring Networks)
15.4v Comments from Dr. Gilb PAR comments: 5.2 - What are the anticipated data rates and ranges? Without the target data rates and ranges it is not possible to determine the technical feasibility of the proposed amendment. - 802.15.4 has many PHYs, will all of them be re-mapped into these bands or just specific ones. No, just the SUN PHYs and the PHYs for Low Energy Critical Infrastructure Monitoring (LECIM), and the TV Whites Spaces (TVWS) PHY I think the easiest thing here is to reference the PHYs in the standard that be enabled to use the indicated bands. This would resolve range and rate questions as the PHYs have already been shown to have technical feasibility for their intended ranges and rates. Scope has been modified to reference the SUN, LECIM, AND TVWS PHYs (See next slide) I don't think the WG is intending that all 20 some PHYs are mapped into these bands. CSD comments: No comments Kunal Shah (Silver Spring Networks)
Modified Scope for 15.4v PAR • This amendment defines changes to the IEEE Std 802.15.4-2015 SUN PHYs clauses enabling the use of the 870-876 MHz & 915-921 MHz bands in Europe, the 902-928 MHz band in Mexico, the 902-907.5 MHz & 915-928 MHz bands in Brazil, the 915-928 MHz band in Australia/New Zealand and Asian regional frequency bands that are not in IEEE Std 802.15.4-2015. This amendment also changes the channel parameters listed in the SUN PHYs, Low Energy Critical Infrastructure Monitoring PHY and the TV White Space PHY for the 470-510 MHz band in China and the 863-870 MHz band in Europe, and aligns these channel parameters with regional requirements. The amendment includes channel access and/or timing changes to the MAC necessary for conformance to regional requirements for these bands. Kunal Shah (Silver Spring Networks)
15.4v comments from Paul Nikolich • 802.15.4v project item 5.1. Please provide justification for the approximately 100 participants identified for this project. Approximately how many man-years of effort will be required to complete the project over its projected 18 month duration? Which classes of entities (e.g., silicon vendor, system vendor, service provider, etc.) do you believe will sponsor for these individuals over the project's lifetime? A large portion of these individuals will be new additions to the 802.15 roster and I'm wondering if you can provide the rationale that will attract new participants given the high cost of participation. Perhaps a reduction in the estimate for the approximate number of people to be actively involved will be more realistic? • We used to show project estimates but then the pendulum seemed to move in the direction of showing WG voters. We are fine with making this a project estimate. 15.4v is essentially a clean-up. We expect to see around 10 active participants from the existing 802.15 voter group (many of the same suspects active in the revision). It is not going to be a lot of work. It just one of those things that needs doing. 5.1 will be adjusted to read 10. Kunal Shah (Silver Spring Networks)
802.3 comments on the 802.15.4v PAR and CSD PAR, 5.1 -100 active participants seems a bit optimistic, though the PAR instruction has moved back to a very liberal wording (our WGs are different than the WGs in most of IEEE-SA). How many will be actively involved in development of the draft (perhaps starting with anticipated TG members), don’t include those submitting a meaningless WG ballot just to keep working group voting rights. Number being modified to reflect 10 expected active participants. See response to Paul’s comment on the previous slide Kunal Shah (Silver Spring Networks)
802.3 comments on the 802.15.4v PAR and CSD CSD, 1.1.1 –If you are adding a new PHY you probably are at least adding enumerations to managed objects. I management doesn’t know which PHY is attached, why not. Answer has been changed to read: “While no new managed objects are anticipated any managed objects that are required will be defined as part of the project” CSD, 1.2.1,b -Minor readability: line 4, remove "and many more". Agree, removed CSD, 1.2.5,c -The answer is unresponsive. Manufacturing methods are not installation cost. Please answer the question. Answer has been changed to read: “Installation costs are not affected by this amendment.” Kunal Shah (Silver Spring Networks)
802.11 comments on the 802.15.4v on PAR and CSD 2.1 Title: delete “Approved Draft” Suggested title replacement: “Standard for Low-Rate Wireless Personal Area Networks (WPANs) Amendment: Enabling/updating the use of Regional Sub-GHz bands” This MyProject field is not under our control. 5.2.b Scope of the project: delete “PHY clauses” We were able to delete the word “clauses” but needed to clearly specify which PHYs to satisfy Dr. Gilb’s comment CSD – No comments or concerns Kunal Shah (Silver Spring Networks)