Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
2.1 Typically titles begin with "Standard for...", "Guide for..." or "Recommended Practice for...". If a general term is used to represent ranges (e.g. high, medium, low) within the title, scope, or purpose, numerically define such ranges where they first appear (title, scope, or purpose, as applicable). From the PAR submission instructions.
We were confused, as it is a profile, is that a standard/guide/recommended practice?
2.1 and 5.2 the use of “profile” vs “profiles” the plurality should be the same.
5.2 “The profiles select” seems to imply a Guide or Recommended practice… harmonizing the title and 5.2 should be done.
5.4 “This standard provides profiles” if we need to change 2.1 and 5.2, make similar changes to 5.4.
5.4
“support the entire range of aerospace onboard application” …”Entire”
really.
Suggest changing to “broad” .
5.5 – “use of IEEE 802 standards” – this may be overly broad as it does not include 802.11 in the descriptions. Suggest change to “use of IEEE 802.1 and IEEE 802.3 standards”, or you could include the use of 802.11 in the scope.
8.1 The note for 5.2 seems to imply that this would be a guide or recommend practice.
8.1 the note for 5.2 and 5.4 notes 802.3, but if you expand the scope for 802.11 it should be noted.
8.1 IEEE 802.3 Ethernet networks, IEEE 802.1 Time-Sensitive Networking (TSN) and IEEE 802.1 All cited Standards should be fully expanded and noted here in 8.1.
The example of 802.1CM may be used for title and scope issues noted.
Note that the title in CSD is not quite the same as the PAR…” Standard for Local and Metropolitan Area Networks” is not included in the PAR.
1.2.4 - “IEEE 802 standards” why is 802.11 excluded? If it is technically feasible, it should be included. If not included, then why is it excluded?
Note in general, where it states “IEEE 802 standards” if we do not exclude 802.11, then the statement would be valid and true.
Colleagues,
802.1 is proposing the following PAR and CSD for review and potential approval at the November plenary.
P802.1DP - Time-Sensitive Networking Profile for Aerospace Onboard Ethernet Communications
PAR: https://www.ieee802.org/1/files/public/docs2020/dp-draft-PAR-0920-v01.pdf
CSD: https://www.ieee802.org/1/files/public/docs2020/dp-draft-CSD-0920-v01.pdf
Cheers,
Glenn.
--
Glenn Parsons
Chair, IEEE 802.1 WG
+1-613-963-8141
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1
To unsubscribe from the STDS-802-SEC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-SEC&A=1