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

Re: [802.3_SPEP2P] Proposed clarification text for 'MAC Merge' as a proper name



Thank you, Geoff.  I believe that helps.  The only change I’d offer, is that I think there is a ‘the’ missing before “Clause 99” on the last line. Do you agree, or was that intentional?

 

From: thompson@xxxxxxxx <thompson@xxxxxxxx>
Sent: Wednesday, June 9, 2021 5:17 PM
To: stds-802-3-spep2p@xxxxxxxxxxxxxxxxx; George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>
Cc: George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: [802.3_SPEP2P] Proposed clarification text for 'MAC Merge' as a proper name

 

George-

 

My version:

"(Sec 2.1) While ‘MAC’ (Medium Access Control) is an acronym, the term 'MAC Merge' in the title is the proper name of a function within IEEE Std 802.3 and the term used in the title of the candidate clause for amendment, Clause 99, "MAC Merge sublayer.""  Using it as a proper name, not expanded, improves clarity and the ability of the reader of the PAR to find the appropriate clause in IEEE 802.3 which is being modified, as named above. The proposed project would consider amendments to Clause 99 specification for this function in IEEE Std 802.3 to support 10 Mb/s single-pair Ethernet point-to-point PHYs. “

 

I hope this helps.

 

Geoff

 

 

On Wednesday, June 9, 2021, 04:39:03 PM PDT, George Zimmerman <george@xxxxxxxxxxxxxxxxxxxx> wrote:

 

 

All –

As mentioned in the study group meeting today, below is the text I was currently thinking of adding to 8.1 Additional Explanatory Notes

 

"(Sec 2.1) While ‘MAC’ (Medium Access Control) is an acronym, the term 'MAC Merge' in the title is the proper name of a function within IEEE Std 802.3.  Using it as a proper name, not expanded, improves clarity and the ability of the reader of the PAR to find the appropriate clause in IEEE 802.3 which is being modified, of the same name.    The proposed project would consider amendments to the (Clause 99) specification for this function in IEEE Std 802.3 to support 10 Mb/s single-pair Ethernet point-to-point PHYs. “

 

Please send any proposed edits on this either to me or to the reflector. It would be helpful to converge on this quickly so that we can let other working groups know.

 

 

George Zimmerman, Ph.D.

President & Principal

CME Consulting, Inc.

Experts in Advanced PHYsical Communications

george@xxxxxxxxxxxxxxxxxxxx

310-920-3860

 


To unsubscribe from the STDS-802-3-SPEP2P list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPEP2P&A=1


To unsubscribe from the STDS-802-3-SPEP2P list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-SPEP2P&A=1