From: Michael Richardson <mcr@sandelman.ca>
To: Alexander Aring <alex.aring@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net 0/2] net: ipv6: seg6: headroom fixes
Date: Wed, 05 Feb 2020 13:21:37 +0100 [thread overview]
Message-ID: <26689.1580905297@dooku.sandelman.ca> (raw)
In-Reply-To: <20200204173019.4437-1-alex.aring@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1771 bytes --]
Alexander Aring <alex.aring@gmail.com> wrote:
> This patch series fixes issues which I discovered while implementing RPL
> source routing for 6LoWPAN interfaces. 6LoWPAN interfaces are using a MTU
> of 1280 which is the IPv6 minimum MTU. I suppose this is the right fix to
> do that according to my explanation that tunnels which acting before L3
> need to set this headroom. So far I see only segmentation route is affected
> to it. Maybe BPF tunnels, but it depends on the case... Maybe a comment
> need to be added there as well to not getting confused. If wanted I can
> send another patch for a comment for net-next or even net? May the
> variable should be renamed to l2_headroom?
I had discussed this with Alex over the past few days.
I had not looked closely at the code during that discussion, and maybe my
comments in chat were wrong. So these patches don't look right to me.
I think that the issue we have here is that things are big vague when it
comes to layer-2.5's, and fatter layer-3s. Maybe this is well established in
lore...
My understanding is that headroom is a general offset, usually set by the L2
which tells the L3/L4 how much to offset in the SKB before the ULP header is
inserted. TCP/UDP/SCTP/ESP need to know this.
MPLS is a layer-2.5, and so it quite weird, because it creates a new L2
which lives upon other L2 and also other L3s.
Segment routing, and RPL RH3 headers involve a fatter L3 header.
Of course, one could mix all of these things together!
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-05 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 17:30 [PATCH net 0/2] net: ipv6: seg6: headroom fixes Alexander Aring
2020-02-04 17:30 ` [PATCH net 1/2] net: ipv6: seg6_iptunnel: set tunnel headroom to zero Alexander Aring
2020-02-06 12:54 ` David Miller
2020-02-08 17:34 ` Alexander Aring
2020-02-04 17:30 ` [PATCH net 2/2] net: ipv6: seg6_local: don't set headroom Alexander Aring
2020-02-05 12:21 ` Michael Richardson [this message]
2020-02-06 18:22 ` [PATCH net 0/2] net: ipv6: seg6: headroom fixes Alexander Aring
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=26689.1580905297@dooku.sandelman.ca \
--to=mcr@sandelman.ca \
--cc=alex.aring@gmail.com \
--cc=netdev@vger.kernel.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 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).