-----Original Message-----
From: Yerang Hur [mailto:yehur@posdata-usa.com]
Sent: Thursday, December 23, 2004 6:21 PM
To: STDS-802-16@listserv.ieee.org
Cc:
mthomas@AIRSPAN.COM; yehur@posdata-usa.com
Subject: RE: [STDS-802-16] Is the Ethernet CRC included in the MAC PDU?
Dear Mark,
If there’s no convincing reason we need to take the Ethernet CRC out from the Ethernet PDU, we may keep the Ethernet CRC in the 16 payload.
Regarding PHS, CS is in charge of suppressing the payload header and rebuilding the suppressed payload header information. The roles of CS should be transparent to computing the Ethernet CRC.
If individual Ethernet CRC checks fail, responses will vary depending on what service flow is associated with the connection.
Yerang Hur
------
E-mail: yehur@posdata-usa.com
Posdata America R&D Center
Santa Clara, CA 95054, USA
-----Original Message-----
Mark Thomas <mthomas@AIRSPAN.COM> wrote:
Date: Thu, 23 Dec 2004 08:17:50 -0000
From: Mark Thomas
Subject: [STDS-802-16] Is the Ethernet CRC included in the MAC PDU?
To: STDS-802-16@listserv.ieee.org
Hi,
The 802.16-2004 standard does not appear to specify clearly which
Ethernet fields are to be included in the MAC layer PDU when the
convergence sublayer type is Ethernet or IP over Ethernet. For instance,
I assume that the Ethernet preamble and start frame delimiter should not
be included. Should the Ethernet CRC be included? The DOCSIS standard
does include a four-octet CRC on each packet and fragment, but as far as
I can see, DOCSIS does not have the possibility of an over!
all MAC
CRC to
protect the payload. 802.16 has an optional CRC on the whole MAC PDU.
If 802.16 includes the Ethernet CRC, then should we recalculate the CRC
after payload he ader suppression? What response is required if the MAC
CRC on a MAC PDU is correct, but individual Ethernet CRCs within the PDU
fail?
Mark