From: Mika Liljeberg <mika.liljeberg@welho.com>
To: Sridhar Samudrala <sri@us.ibm.com>
Cc: kuznet@ms2.inr.ac.ru, jgrimm2@us.ibm.com, davem@redhat.com,
netdev@oss.sgi.com
Subject: Re: SCTP path mtu support needs some ip layer support.
Date: 14 Jan 2003 22:11:06 +0200 [thread overview]
Message-ID: <1042575066.2610.26.camel@devil> (raw)
In-Reply-To: <Pine.LNX.4.33.0301140946230.1978-100000@dyn9-47-18-86.beaverton.ibm.com>
On Tue, 2003-01-14 at 20:44, Sridhar Samudrala wrote:
> Frankly, i haven't thought of IPV6 in detail. I was under the impression that
> it is simpler in ipv6 as only source is allowed to do fragmentation and as there
> is no DF bit, it will automatically fragment any packets larger than the pmtu.
> But looking at ip6_xmit(), i realize that ICMPV6_PKT_TOOBIG error is generated
> forcing the transport layer to do the fragmentation. TCP can handle this, but
> SCTP cannot.
IPv6 is simpler, because the specification asserts that every IPv6
capable link must support a MTU of at least 1280 bytes. If you don't
generate packets larger than this you don't have to worry about
fragmentation.
If you want larger data chunks, then you have to solve this for IPv6 as
well.
MikaL
next prev parent reply other threads:[~2003-01-14 20:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3E1CCD72.6020100@us.ibm.com>
2003-01-13 20:48 ` SCTP path mtu support needs some ip layer support kuznet
2003-01-13 21:07 ` Andi Kleen
2003-01-13 21:21 ` Nivedita Singhvi
2003-01-13 21:25 ` kuznet
2003-01-13 23:34 ` Jon Grimm
2003-01-13 22:54 ` Sridhar Samudrala
2003-01-13 23:03 ` Mika Liljeberg
2003-01-14 0:56 ` Sridhar Samudrala
2003-01-14 6:46 ` Mika Liljeberg
2003-01-13 23:22 ` kuznet
2003-01-14 0:49 ` Sridhar Samudrala
2003-01-14 1:22 ` kuznet
2003-01-14 18:44 ` Sridhar Samudrala
2003-01-14 20:11 ` Mika Liljeberg [this message]
2003-01-14 22:15 ` Sridhar Samudrala
2003-01-14 21:16 ` kuznet
2003-01-08 23:04 Sridhar Samudrala
2003-01-08 23:06 ` David S. Miller
2003-01-08 22:48 ` Jon Grimm
2003-01-08 23:45 ` David S. Miller
2003-01-08 23:56 ` Nivedita Singhvi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1042575066.2610.26.camel@devil \
--to=mika.liljeberg@welho.com \
--cc=davem@redhat.com \
--cc=jgrimm2@us.ibm.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=sri@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).