July 2014
doc.: IEEE 11-10/0897r0
802-11 PAR Review – July 2014
Date: 2014-07-15
Authors:
Name
Affiliations
Address
Phone
Jon Rosdahl CSR Technologies Inc. 10871 N 5750 W
+1-801-492-4023
Highland, UT 84003
Submission
Slide 1
email
jrosdahl@ieee.org
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
Abstract
Review of the PARS for consideration for July 2014.
http://grouper.ieee.org/groups/802/PARs.shtml
Submission
Slide 2
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
2.3 II PARs for review this week
802.1ARce - Secure Device Identity, Amendment 1: Amendment 1: SHA-384
and P-384 Elliptic Curve, PAR and CSD
802.1AEcg - Media Access Control (MAC) Security - Amendment: Ethernet
Data Encryption devices, PAR and CSD
802.3bv- amendment, 1000 Mb/s Operation Over Plastic Optical Fiber , PAR
and CSD
802.3bw - amendment, 1 Twisted Pair 100 Mb/s Ethernet , PAR and CSD
802.11ah, Sub 1 GHz, PAR extension request, PAR and CSD
802.11ai, Fast initial link setup, PAR extension request , PAR and 5C
(grandfathered)
802.15.4, amendment enabling Spectrum Resource Measurement Capability,
PAR and CSD
802.22.3, Specifying Spectrum Occupancy Sensing (SOS) Measurement
Devices and Means that Enable Coalescing the Results from Multiple
Such Devices, PAR and CSD
Submission
Slide 3
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.24 Charter Change
In the proposed process for creating Task Groups (TGs)
under 802.24, a proposed TG scope document is
circulated 30 days in advance of a plenary to solicit
comments from the WGs. According to the proposed
process, this follows the PAR process in that comments
are due by 5 pm Tuesday of the plenary week and
responses are due by 5 pm on Wednesday.
The 802.24 Smart Grid TAG approved a TG scope
document for a Smart Grid TG, 24-14-0015-01-0000Smart-Grid-TG-Scope.pdf, which can be found at:
https://mentor.ieee.org/802.24/dcn/14/24-14-0015-010000-smart-grid-tg-scope.pdf
Submission
Slide 4
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
Comments from 802.11 PAR AdHoc Committee
COMMENTS FOR JULY 2014
PARS FOR CONSIDERATION.
Submission
Slide 5
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.1ARce - Secure Device Identity, Amendment 1:
Amendment 1: SHA-384 and P-384 Elliptic Curve, PAR
and CSD
1. Expand Acronyms for first usage in Scope/Title/Purpose.
“SHA-384, P-384, ECDSA”
Submission
Slide 6
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.1AEcg - Media Access Control (MAC) Security Amendment: Ethernet Data Encryption devices, PAR
4.1 and 4.2: Check the Start of Sponsor Ballot and the Submission to
RevCom dates…They do not seem reasonable.
Note that the dates that are listed seem to be close to date that a new
revision is needed. Have you considered just getting this amendment
done in conjunction with a Revision PAR?
5.5 Change “separate bridging systems (Ethernet Data Encryption devices,
EDEs) “ to separate bridging systems, Ethernet Data Encryption
devices, (EDEs)
8.1 Add the full name of the 802.1AE, 802.1X, and 802.1Q standards.
8.1: Where is “#7.3”? This comment may be a hold over, or miss labeled.
5.6 – consider making the Stakeholders: Developers and users of secure
networking equipment.
Submission
Slide 7
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.1AEcg - Media Access Control (MAC) Security Amendment: Ethernet Data Encryption devices, CSD
1.2 Broad Market Potential: “…number of significant users…” what number?
Who are these significant users?
1.2.2/1.2.3 missing “Std” on several of the standards cited.
1.2.5 change “802.1AE-2006” to “IEEE Std 802.1AE-2006”
Please check in the CSD for other instances of missing proper citation.
Submission
Slide 8
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.3bv- amendment, 1000 Mb/s Operation Over Plastic
Optical Fiber , PAR
5.6 change Stakeholder list: “Stakeholders identified to date
include but are not limited to: user…s” to “Users…”
7.1 expand the acronym “VDE”… (not sure what VDE is).
7.1 From the 802.3 CSD – “There are standardized specifications
for data transmission over POF…leveraging those…” need to
indentify the “other” standards that are similar that make up
“those”.
8.1 suggest a bit of explanation on what is being stated…
“. Its specifications” is this the VDE Document?
Is the withdrawn standard being incorporated into this
amendment?
Submission
Slide 9
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.3bv- amendment, 1000 Mb/s Operation
Over Plastic Optical Fiber , CSD
From the title page
“The following are the CSD Responses in relation to the IEEE P802.3xx
PAR”
this seems a bit Generic..Was the correct CSD provided?
Submission
Slide 10
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.3bw - amendment, 1 Twisted Pair 100 Mb/s Ethernet , PAR and
CSD
No Comment
Submission
Slide 11
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.11ah, Sub 1 GHz, PAR extension request, PAR and CSD
No comment
Submission
Slide 12
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.11ai, Fast initial link setup, PAR extension request , PAR and 5C
(grandfathered)
No comment
Submission
Slide 13
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.15.4, amendment enabling Spectrum Resource Measurement
Capability, PAR and CSD
1.3.4 b) needs a response:
b)Proven similar technology via testing, modeling, simulation, etc.
Submission
Slide 14
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.22.3, Specifying Spectrum Occupancy Sensing (SOS)
Measurement Devices and Means that Enable Coalescing the Results
from Multiple Such Devices, PAR and CSD
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: 1.2.2 – Cite standards correctly.
CSD: Seems the History is repeated for several responses.
CSD: Seems overly verbose
Submission
Slide 15
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.24 Charter Change
In the proposed process for creating Task Groups (TGs)
under 802.24, a proposed TG scope document is
circulated 30 days in advance of a plenary to solicit
comments from the WGs. According to the proposed
process, this follows the PAR process in that comments
are due by 5 pm Tuesday of the plenary week and
responses are due by 5 pm on Wednesday.
The 802.24 Smart Grid TAG approved a TG scope
document for a Smart Grid TG, 24-14-0015-01-0000Smart-Grid-TG-Scope.pdf, which can be found at:
https://mentor.ieee.org/802.24/dcn/14/24-14-0015-010000-smart-grid-tg-scope.pdf
Submission
Slide 16
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
802.24 Comments
Concern:
Not seen large numbers interested in attending 802.24
If we are creating White papers instead of Standards,
then are we needing to create a new process.
Can the Industry Connection be a process that is
sufficient rather than change 802.24?
Submission
Slide 17
Jon Rosdahl, CSR
July 2014
doc.: IEEE 11-10/0897r0
References
Submission
Slide 18
Jon Rosdahl, CSR