[FE] Comment on 3.1.2

[Pat Thaler <pat_thaler@xxxxxxxxxxx>]

Since I may not be able to attend the FE meeting, I'd like to submit a comment on 3.1.2.

 

The current figure is inaccurate because it shows an FCS sourced from the MA_DATA.request with a PAD not sourced from the MA_DATA.request.

 

There are at least two ways this could be resolved

Make the arrow for frame check sequence a dotted line, make the Pad sides dotted, add a statement that FCS may only be sourced from the MA_DATA.request when there is no PAD.

 

or do two figures - one with PAD and no arrow from MA_DATA.request to PAD and one with no PAD and MA_DATA.request providing FCS.

 

Regards,

Pat

-----Original Message-----
From: **** IEEE 802.3 Frame Expansion Study Group **** [mailto:STDS-802-3-FE@LISTSERV.IEEE.ORG]On Behalf Of Kevin Daines
Sent: Friday, 11 March, 2005 5:21 PM
To: STDS-802-3-FE@LISTSERV.IEEE.ORG
Subject: [FE] Atlanta materials uploaded

All,

 

The meeting materials for the next week's plenary meeting in Atlanta have been uploaded to our web site. The URL below contains a direct link to the webpage:

 

http://www.ieee802.org/3/as/public/0503/index.html

 

Many thanks to Glenn Parsons, Editor, for pulling together an unofficial D0.1. It contains proposed changes to Clauses 2, 3, 4, 31, and 31B. We'll review this draft and hopefully come out of Atlanta with plans for our first Task Force ballot.

 

 

 

Kevin Daines

Chair, P802.3as Frame Expansion Task Force