From: Juliusz Chroboczek <jch@pps.jussieu.fr>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<public-b.a.t.m.a.n-ZwoEplunGu2X36UT3dwlltHuzzzSOjJt@plane.gmane.org>
Subject: Re: [B.A.T.M.A.N.] BATMAN-Adv and MTU handling
Date: Sun, 15 Nov 2009 18:08:43 +0100 [thread overview]
Message-ID: <87fx8fvhpg.fsf@trurl.pps.jussieu.fr> (raw)
In-Reply-To: <20091112005149.GA2879@Linus-Debian> ("Linus Lüssing"'s message of "Thu, 12 Nov 2009 01:51:49 +0100")
>> I think you underestimate the performance impact. AFAIK IPv6 does not
>> support the clasical IPv4 fragmentation anymore (intermediate routers
>> won't fragment the packets but drop them).
> Hmm, yes, true, IPv6 does not support fragmentation at all...
It does, but it's done end-to-end, not at intermediate routers. See
Section 5 of RFC 2460.
Juliusz
next prev parent reply other threads:[~2009-11-15 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-09 19:02 [B.A.T.M.A.N.] BATMAN-Adv and MTU handling Linus Lüssing
2009-11-10 10:34 ` Marek Lindner
2009-11-10 22:16 ` Simon Wunderlich
2009-11-12 0:51 ` Linus Lüssing
2009-11-12 3:28 ` Marek Lindner
2009-11-15 17:08 ` Juliusz Chroboczek [this message]
2009-11-23 14:21 ` Linus Lüssing
2009-12-11 13:45 ` Linus Lüssing
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=87fx8fvhpg.fsf@trurl.pps.jussieu.fr \
--to=jch@pps.jussieu.fr \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=public-b.a.t.m.a.n-ZwoEplunGu2X36UT3dwlltHuzzzSOjJt@plane.gmane.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.