Re: Fw: [RPRWG] CRC check in each node?
Pankaj, the reason a bit is set in the packet by the station that first sees
the bad CRC, is so that the downstream stations know the error occurred
somewhere upstream from their feeding links. Therefore, they know not to
store the error as an event that occurred somewhere between their upstream
station and their receiver.
Best regards,
Robert D. Love
Chair, Resilient Packet Ring Alliance
President, LAN Connect Consultants
7105 Leveret Circle Raleigh, NC 27615
Phone: 919 848-6773 Mobile: 919 810-7816
email: rdlove@xxxxxxxx Fax: 208 978-1187
----- Original Message -----
From: "Pankaj K Jha" <pkj@xxxxxxxxxxx>
To: "RDLove" <rdlove@xxxxxxxxx>
Cc: "Angela T. Faber" <afaber@xxxxxxxxxxxxx>; "ieee 802.17 list"
<stds-802-17@xxxxxxxx>
Sent: Monday, July 02, 2001 11:42 AM
Subject: Re: Fw: [RPRWG] CRC check in each node?
> I've one doubt I'd like to clarify. If it is only for the local station to
> record statistics, why would it have to set a bit in the packet to do so?
It
> already knows there is a CRC error and it can update its statistics
locally. As
> far as other other downstream nodes are concerned, they too will find the
CRC
> errors during reception because they'll be checking for CRC errors anyway.
What
> exactly does the bit setting help in? It doesn't help in node
identification in
> a series of nodes. Please advise.
> Regards,.
> Pankaj
>
> RDLove wrote:
>
> > Pankaj, the reason to set a bit when a station sees a CRC error, is so
that
> > the station that first sees the error can record the "error created"
event.
> > It is that station, and not the destination station with the information
> > available for transmitting to a station that gathers statistics.
> >
> > Best regards,
> >
> > Robert D. Love
> > Chair, Resilient Packet Ring Alliance
> > President, LAN Connect Consultants
> > 7105 Leveret Circle Raleigh, NC 27615
> > Phone: 919 848-6773 Mobile: 919 810-7816
> > email: rdlove@xxxxxxxx Fax: 208 978-1187
>