|
A
header error correction (HEC) in the header solves this problem. this is
useful to support some services which require the data to be
transported without being dropped even if it has corrupted data. (Refer to Raj
Sharma's presentation, May meeting)
Ashwin
Hi All
Obviously, if TTL is part of the header and protected by CRC then CRC
check/update has to be done at every node. There can be a CRC for the
header alone. That might mitigate Angela's concerns.
Regards
Ajay Sahai
"Angela T. Faber" wrote:
Folks One question regarding CRC check: are we assuming
CRC will be checked at every node (as the frame is forwarded) or it will be
checked only at the destination/source node?My initial thought on this is that, if we don't do
it at every node, than how do we remove the frame from ring if the source
and destination addresses are corrupted? On the other hand I assume that if
every node checks it, more time is spent with forwarding
it.... Any insights are
welcomed.Thanks! Angela
|