Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: [802SEC] Responses to IEEE 802.11 / Jon Rosdahl comments on IEEE P802.3df PAR and CSD



Jon,

If you feel I should be there – please let me know.

802.3 has its closing plenary this morning – which I need to be present for regarding this PAR, but if you feel I should be present I will rearrange things as much as possible.

 

John

 

From: Jon Rosdahl <jrosdahl@ieee.org>
Sent: Thursday, November 18, 2021 12:22 AM
To: John D'Ambrosia <jdambrosia@gmail.com>
Cc: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] Responses to IEEE 802.11 / Jon Rosdahl comments on IEEE P802.3df PAR and CSD

 

Thanks John,

I will review with the 802.11 PAR Review SC on Thursday Morning.

Regards,

Jon


-----------------------------------------------------------------------------

Jon Rosdahl                             Engineer, Senior Staff
IEEE 802 Executive Secretary   Qualcomm Technologies, Inc.
office: 801-492-4023
                  10871 North 5750 West
cell:   801-376-6435                   Highland, UT 84003


A Job is only necessary to eat!
A Family is necessary to be happy!!

 

 

On Wed, Nov 17, 2021 at 6:09 AM John D'Ambrosia <jdambrosia@gmail.com> wrote:

Hi Jon,

David has delegated responding to the comments you submitted on behalf of 802.11 and yourself.

Thank you very much for the IEEE 802.11 comment and the comment you submitted.

Please see the responses below.

Based on these comments and issues raised during the IEEE 802.3 Beyond 400 Gb/s Ethernet Study Group electronic meeting on 11/16/21, the PAR was updated and can be accessed at < https://mentor.ieee.org/802-ec/dcn/21/ec-21-0224-02-00EC-par-ieee-p802-3df.pdf>, and the CSD was updated and can be accessed at < https://mentor.ieee.org/802-ec/dcn/21/ec-21-0225-01-00EC-csd-ieee-p802-3df.pdf >. 

Best Regards,

John D’Ambrosia

Comment #1 (from 802.11):

·       PAR

·       5.2.b – Change “;” to ,” (This is a simple list of 3 items and a comma should be ok.  -- Use a semicolon to join two related independent clauses in place of a comma and a coordinating conjunction (and, but, or, nor, for, so, yet). Make sure when you use the semicolon that the connection between the two independent clauses is clear without the coordinating conjunction.)

·       CSD: No Comments

·       Response

·       Accept.  In PAR 5.2.b change “ ; ” to “ , “

Comment #2 (from Jon Rosdahl)

·       PAR

·       If 5.2a, you define MAC and PHY acronyms, so in 5.2b you could use MAC and PHY rather then spell them out... 

Also I note that you do repeat the MAC definition, but did not for the PHY (physical Layer).  Also not sure why the semicolon, (I note that I am not expert on the use.)

What is in 5.2b: 

"Define Ethernet Media Access Control (MAC) parameters, physical layer specifications; and management parameters"

Suggest:

"5.2b: Define Ethernet MAC and PHY layer specifications and management parameters....."

·       CSD – No comments

·       Response

·       Accept in principle.

It is correct that the MAC acronym is spelled out, but the use of  “physical layer” in 5.2.b is referring to the physical layer of the ISO/IEC Open Systems Interconnection (OSI) reference model.  In IEEE Std 802.3TM-2018, a PHY is the portion of the Physical Layer between the Medium Dependent Interface (MDI) and the Media Independent Interface (MII).  Making the proposed change for PHY would substantially reduce the proposed scope of the project.

Change the text in PAR 5.2.b

The text “Define Ethernet Media Access Control (MAC) parameters, physical layer specifications; and management parameters for the transfer of Ethernet format frames at 800 Gb/s and 1.6 Tb/s over copper, multi-mode fiber, and single-mode fiber, and use this work to define derivative physical layer specifications and management parameters for the transfer of Ethernet format frames at 200 Gb/s and 400 Gb/s.”

to read

“Define Ethernet MAC parameters, physical layer specifications, and management parameters for the transfer of Ethernet format frames at 800 Gb/s and 1.6 Tb/s over copper, multi-mode fiber, and single-mode fiber, and use this work to define derivative physical layer specifications and management parameters for the transfer of Ethernet format frames at 200 Gb/s and 400 Gb/s.”




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