Thread Links | Date Links | ||||
---|---|---|---|---|---|
Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
Hello Raj
When you say "ultimate destination
entity connected to an RPR MAC" are you talking about the client connected
to the RPR network (and therefore connected to the egress RPR node)? If
so, if the headers are corrupted, why
wouldn't we prevent the misrouting as soon as we detect it (instead of
allowing the destination to do it)? That would avoid BW to be wasted with
packets that will be dropped at the destination (since I believe they make no
use of that...). In addition it would be better to localize a possible fault
(i.e., the segment where it went bad), and would help to correlate with other
packets that also had some sort of error in that segment...
Am I missing something in here?
Angela
----- Original Message -----
|