Subject: [COFF] OSI stack
Date: Thu, 7 Feb 2019 19:28:21 +0000 [thread overview]
Message-ID: <20190207192821.7hjsf6atfyi747sb@h-174-65.A328.priv.bahnhof.se> (raw)
In-Reply-To: <0572e855-9aac-337f-4f1b-66dda3839e14@spamtrap.tnetconsulting.net>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On 7 Feb 2019 11:07 -0700, from coff at minnie.tuhs.org (Grant Taylor via COFF):
> The only thing that comes to mind is IPsec's ESP(50) and AH(51) which—as I
> understand it—are filtered too frequently because they aren't ICMP(1),
> TCP(6), or UDP(17). Too many firewalls interfere to the point that they are
> unreliable.
While different, I think that the introduction of the more advanced
IPv6 address formats into DNS also qualifies. I don't recall off hand
if bit-string labels (which were used for reverse lookups) or the A6
RRtype (for forward lookups) was the more problematic one, but I do
recall that both had issues that made real-world adoption non-trivial
in the best of cases.
--
Michael Kjörling • https://michael.kjorling.se • michael at kjorling.se
“The most dangerous thought that you can have as a creative person
is to think you know what you’re doing.” (Bret Victor)
next prev parent reply other threads:[~2019-02-07 19:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190206174913.E518318C07B@mercury.lcs.mit.edu>
[not found] ` <CAK7dMtBuLv+62LKknOKAYxCBwLBF2zBJ8TLTXAqnHGekGgAPFA@mail.gmail.com>
2019-02-07 18:07 ` [COFF] [TUHS] OSI stack (Was: Posters) gtaylor
2019-02-07 18:22 ` akosela
2019-02-07 18:33 ` crossd
2019-02-13 3:20 ` dave
2019-02-07 18:50 ` lm
2019-02-07 19:28 ` [this message]
2019-02-08 2:41 ` [COFF] OSI stack gtaylor
[not found] ` <CAK7dMtBQgfNsXnzV_gdQ8BxdiRv__AmBp-LGQMTEOvyNSyKkAA@mail.gmail.com>
2019-02-08 3:43 ` [COFF] [TUHS] OSI stack (Was: Posters) gtaylor
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=20190207192821.7hjsf6atfyi747sb@h-174-65.A328.priv.bahnhof.se \
--to=coff@minnie.tuhs.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).