netdev
[Top] [All Lists]

Re: SCTP path mtu support needs some ip layer support.

To: kuznet@xxxxxxxxxxxxx, Jon Grimm <jgrimm2@xxxxxxxxxx>
Subject: Re: SCTP path mtu support needs some ip layer support.
From: Andi Kleen <ak@xxxxxxx>
Date: Mon, 13 Jan 2003 22:07:08 +0100
Cc: davem@xxxxxxxxxx, sri@xxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <200301132048.XAA09194@sex.inr.ac.ru>
References: <3E1CCD72.6020100@us.ibm.com> <200301132048.XAA09194@sex.inr.ac.ru>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.4i
> Support of pmtu discovery as described in rfc means possibility of semantic
> fragmentation to retransmit any data bits. If SCTP is not ablet to do this,
> then you should not support pmtu discovery at all like most of people make
> for UDP or to follow UDP pattern, fragmenting frames when their size exceeds
> mtu. It is not necessary to cripple ip_queue_xmit calling conventions
> to make this, just add a flag to socket to clear DF on oversized
> frames.

Some recent incidents have shown that ip fragmentation/defragmention
at gigabit speed is rather worthless. The reason is that it has no PAWS
and the 16bit ipid can wrap many times in the standard reassembly
timeout, leading to lots of misassembled packets on a busy network.
Mostly that can be catched by computing the transport layer
checksum, but often enough a misassembled packet can slip through.
While in SCTP it may work a bit better because it supports stronger 
checksums (but only optionally afaik) it is still too dangerous.
So in short clearing DF is near always a bug these days.

-Andi


<Prev in Thread] Current Thread [Next in Thread>