[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
stds-802-16: SYSREQ COMMENT: Proposed Title Change
[Submitter's Last Name]
Marks
[Submitter's First Name]
Roger
[Starting Page #]
i
[Starting Line #]
2
[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E
[Detailed Description of Proposed Insertion, Deletion, Change]
Change title from:
"Preliminary Draft Working Document for 802.16 Broadband Wireless
Access System Requirements"
to:
"802.16.1 Functional Requirements, Rev. 0"
[Reason for Edit]
(1) Drop language indicative of a preliminary status.
(2) Use "Rev. 0" to allow easy migration path.
(3) Use the new PAR number (802.16.1) to refer to the Air Interface standard.
(4) Replace "System Requirements" with "Functional Requirements" because:
-The document specifies the functions that the network provides
rather than requirements concerning the system implementation.
-Consistent with "IEEE 802 Functional Requirements"
<http://grouper.ieee.org/groups/802/11/fureq6-8.html>.
-Consistent with "802.14 Cable-TV Functional Requirements and
Evaluation Criteria" <http://www.walkingdog.com/catv/94-002.pdf>
-"Functional Requirements" was used in several contributions in
support of the development of this document, including:
*802.16sc-99/7
Functional Requirements for the 802.16 Standard
*802.16sc-99/5
Functional Requirements for Broadband Wireless Access Networks
*802.16sc-99/2
802.6 Functional Requirements
[Submitter's Last Name]
Marks
[Submitter's First Name]
Roger
[Starting Page #]
misc.
[Starting Line #]
misc.
[(T)echnical for Content-Related Material; (E)ditorial for typos,
grammar, etc.]
E
[Detailed Description of Proposed Insertion, Deletion, Change]
Global replacement of "System Requirements" with "Functional Requirements".
[Reason for Edit]
For consistency with proposed change of title to "802.16.1 Functional
Requirements, Rev. 0".