Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Agree. To Roger’s point –every reference to IEEE 802.3bs or IEEE P802.3bs needs to be checked. Sometimes it is IEEE P802.3bs-2017, but in most cases should be IEEE Std 802.3bs-2017. In the one place where it should be IEEE P802.3bs it isn’t
(“John D’Ambrosia, chair, IEEE P802.3bs Task Force and senior…”) John’s quote is a bit wordy, but that’s actually how he talks
😊. I’ll leave it to him to tighten up if he likes – its style. -george From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org]
On Behalf Of Roger Marks David, I like it. Please remember to replace "P802.3bs™-2017" with "IEEE Std 802.3bs-2017". Just a thought: would it be an opportune time to mention any other ongoing activities in 802.3? I know that the last paragraph says that 802 is always evolving, but it might
help people to know whether, regarding the markets addressed by 802.3bs, you are taking a break or are already laying the groundwork for another step forward. Cheers, Roger On February 20, 2018 at 6:08:52 AM, Law, David (dlaw@hpe.com) wrote:
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 |