From: Larry McVoy <lm@mcvoy.com>
To: Ben Kallus <benjamin.p.kallus.gr@dartmouth.edu>
Cc: John Levine <johnl@taugh.com>, tuhs@tuhs.org
Subject: [TUHS] Re: OT: LangSec (Re: A fuzzy awk.)
Date: Mon, 20 May 2024 14:57:40 -0700 [thread overview]
Message-ID: <20240520215740.GG27662@mcvoy.com> (raw)
In-Reply-To: <CAB6pCSbFDabCiRpvx0uk=5BMR1=2F-ATJRWW2kHDz7VYE10=Yw@mail.gmail.com>
Those would be the stupid people and you can't fix stupid. Seriously,
people can twist anything into anything. Just because dumb people
didn't understand his principle doesn't mean it was a bad principle.
On Mon, May 20, 2024 at 05:46:48PM -0400, Ben Kallus wrote:
> My point was that, regardless of Postel's original intent, many people
> have interpreted his principle to mean that accepting garbage is good.
> *This* interpretation is incompatible with LangSec.
>
> See RFC 9413 for an exploration of the many interpretations of
> Postel's principle.
>
> -Ben
--
---
Larry McVoy Retired to fishing http://www.mcvoy.com/lm/boat
next prev parent reply other threads:[~2024-05-20 21:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-20 13:06 [TUHS] A fuzzy awk. (Was: The 'usage: ...' message.) Douglas McIlroy
2024-05-20 13:14 ` [TUHS] " arnold
2024-05-20 14:00 ` G. Branden Robinson
2024-05-20 13:25 ` Chet Ramey
2024-05-20 13:41 ` [TUHS] Re: A fuzzy awk Ralph Corderoy
2024-05-20 14:26 ` Chet Ramey
2024-05-22 13:44 ` arnold
2024-05-20 13:54 ` Ralph Corderoy
2024-05-20 15:39 ` [TUHS] OT: LangSec (Re: A fuzzy awk.) Åke Nordin
2024-05-20 16:09 ` [TUHS] " Ben Kallus
2024-05-20 20:02 ` John Levine
2024-05-20 20:11 ` Larry McVoy
2024-05-20 21:00 ` Ben Kallus
2024-05-20 21:03 ` John R Levine
2024-05-20 21:14 ` Larry McVoy
2024-05-20 21:46 ` Ben Kallus
2024-05-20 21:57 ` Larry McVoy [this message]
2024-05-20 16:06 ` [TUHS] Re: A fuzzy awk. (Was: The 'usage: ...' message.) Paul Winalski
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=20240520215740.GG27662@mcvoy.com \
--to=lm@mcvoy.com \
--cc=benjamin.p.kallus.gr@dartmouth.edu \
--cc=johnl@taugh.com \
--cc=tuhs@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).