From: Mikael Abrahamsson <swmike@swm.pp.se>
To: David Lang <david@lang.hm>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Wicked OT: 240.0.0.0/4 netblock
Date: Mon, 22 Oct 2018 11:05:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1810221103380.26856@uplift.swm.pp.se> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1810211541180.4351@qynat-yncgbc>
On Sun, 21 Oct 2018, David Lang wrote:
> leaking to the outside in e-mail headers or other payload is no different
> from the current RFC local addresses
Well, it is. For instance spam detection software might think that class-E
in mail header means obligatory SPAM. I don't know, I'm just speculating.
> The problem would be if you allowed the address to leak in the IP headers.
There can be problems outside of just IP headers. The SIP people have IPv6
problems even if they're not doing IPv6 (since it can pop up in the
SIP signaling payload). There are lots of protocols that carry this kind
of information within the protocol, and it does leak.
--
Mikael Abrahamsson email: swmike@swm.pp.se
next prev parent reply other threads:[~2018-10-22 9:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 18:36 Rich Brown
2018-10-19 18:53 ` Dave Taht
2018-10-19 19:09 ` valdis.kletnieks
2018-10-19 19:13 ` Dave Taht
2018-10-19 18:54 ` Jonathan Morton
2018-10-19 19:04 ` Mikael Abrahamsson
[not found] ` <alpine.DEB.2.02.1810191115190.4973@nftneq.ynat.uz>
2018-10-21 16:26 ` Mikael Abrahamsson
[not found] ` <nycvar.QRO.7.76.6.1810211541180.4351@qynat-yncgbc>
2018-10-22 9:05 ` Mikael Abrahamsson [this message]
2018-11-15 3:28 ` Stephen Hemminger
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1810221103380.26856@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=david@lang.hm \
/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