nope, FECN and BECN are bits strictly in the frame relay header. ICMP
will have nothing to do with this. These bits will only be set by frame
relay switches in the cloud that don't know a thing about layer 3, IP,
or ICMP. When they can't process frames fast enough, they'll set these
bits to ease congestion on their hardware (and buffers, etc.). It's then
up to the endpoint stations' higher layer protocols to initiate
retransmission, as they will never see the discarded frames.
I'm actually not sure what source-quench does myself, and I want to
leave work NOW, so I'm not going to look it up ;)
David
Dale Cantrell wrote:
>
> Evening all,
> I'm reading about Frame Relay on Protocols.com and a question arises.
> When the network becomes congested to the point that it cannot process
> new data transmissions, it begins to start discarding frames. Two bits are
> changed in the F.R. header..FECN bit and BECN bit. In this way all
> downstream nodes and the attached user device learn about congestion on the
> line.
> Does this not mean that ICMP would send a "buffer full" message, and
> I thought that was the job of a "source-quench message"? Any movement of the
> definition lines would be gladly received.
> Ya'lls truly, :>)
> Dale
> ________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com
>
> ___________________________________
> UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
> FAQ, list archives, and subscription info: http://www.groupstudy.com
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
___________________________________
UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html
FAQ, list archives, and subscription info: http://www.groupstudy.com
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
