Submission doc.: IEEE 14-22/0098r0 July 2014 Slide 1 P PAR and CSD Comment Resolution Date: Authors:

Submission doc.: IEEE 14-22/0098r0 Comments from the Working Group 2.1 Title – Consider that “SOS” is a internationally recognized acronym for emergency requests. Consider changing or eliminating the acronym… 5.2 The Scope should not talk about the “project”, but rather describe the document that will be created. Please remove project specific definitions and instead describe what the standard will be defining. 5.2 “initially” defines? The Standard will have a set definition that as far as this revision is concerned is the only one that will exist. Do not describe or promise future enhancements. 8.1 is for extra explanation for identified clauses. The clause id is not included. Generally a history is not included in 8.1 CSD: – Cite standards correctly. CSD: Seems the History is repeated for several responses. CSD: Seems overly verbose Slide 2 July 2014

Submission doc.: IEEE 14-22/0098r0 Comments from the Working Group Your title is too long. Please shorten the title to something more concise Since the scope of the project will become the scope of the actual standard, you should delete comments about the “SOS Project” since when the standard is published, there will no longer be an SOS Project, just and SOS standard. The standard should not specify “measurement devices” it should specify “measurement parameters and device behaviors” The phrase “means that enable coalescing the results from multiple such devices” is quite wordy and does not seem to convey a clear message. Is this intended to say “the standard includes protocols for exchanging measurement information?” Slide 3 July 2014

Submission doc.: IEEE 14-22/0098r0 Comments from the Working Group Since when the standard is published the project scope will be the standard scope, you should delete the word “initially” from the scope, so that the scope specifies what is in the standard. In an amendment this could be expanded. The sentence “This standard may specify interfaces and primitives to provide value added sensing information to various spectrum sharing database services” seems to describe some commercial benefits that might fit better into the Need section rather than the Scope section of the PAR. In the Need section of the PAR change “low cost sensors” to ““low-cost spectrum occupancy sensors” The Explanatory Notes Section is used to provide additional information about specific sections in the PAR above. Instead in this PAR it seems to provide a lot of other information but does not explain a specific section above. Slide 4 July 2014

Submission doc.: IEEE 14-22/0098r0 Comments from the Working Group For the PAR: For the PAR: We suggest to delete the phrase “creation of low cost sensors for”. in the following line. Low cost would be vendor sensitive. From: “5.5 Need for the Project: This project will enable creation of low cost sensors for improved spectrum utilization and other shared spectrum applications.” To: “5.5 Need for the Project: This project will enable improved spectrum utilization and other shared spectrum applications.” For the CSD we have a couple of suggestions: In a) b. IEEE P1900.6a, should not have the ‘P’, should say “ b. IEEE a… Also further down in paragraph 3, the same. “… emerging P1900.6a Standard.” should read: “… emerging a Standard.” Slide 5 July 2014

Submission doc.: IEEE 14-22/0098r0 Comments from the Working Group In a) we suggest the term “Companies” be changed to “Organizations” when referring to NICT, ETRI, etc. Also in a) the paragraph starting with: “Systems simiar to the proposed SOS has been…” should read: “Systems similar to the proposed SOS have been…” In a), the first line should remove ‘low cost’ to be consistent with comment above. From: “This standard aims at creating economies of scale through uniform and consistent operation of low cost spectrum sensors.” To: “This standard aims at creating economies of scale through uniform and consistent operation of spectrum sensors.” Slide 6 July 2014

Submission doc.: IEEE 14-22/0098r0 Comments from David Law : This PAR has a very long 8.1 that does not point to any PAR item (as indicated in the parenthetical instruction). I guess it could point to 5.5 Need. Slide 7 July 2014

Submission doc.: IEEE 14-22/0098r0July 2014 Slide 8 References