From: Jonathan Martin <workspace.public@icloud.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-toolchains@vger.kernel.org
Subject: Re: A few proposals, this time from the C++ standards committee
Date: Sun, 17 Mar 2024 16:46:28 -0700 [thread overview]
Message-ID: <00E51206-C20A-4DAC-8DDB-71D2B74C8F55@icloud.com> (raw)
In-Reply-To: <CAHk-=wheP_yuuurG=pJJM1tEXq5oidUqcKhhv0C9zOp4bh7QCQ@mail.gmail.com>
Hello;
I doubt I have any reason to speak on this but I am compelled to try. I have been thinking this over for a long time and this may be an appropriate entry point.
If the OSI model is combined with the six-tier hierarchy of controls used in safety for industrial systems, you get something that can permutate by substituting the application layer with any other position in the ring. I’ve named this as a substitute for the clamoring of idiocy that is DevOps Tree(3).0 to be “Developemnt of Secure Applications,” and “Secure Operations Development Authority.” Dosa with Soda.
The OSI model is obvious enough that I might as well be handing over a toddler's puzzle cube, but I don’t know if you are aware of the six tier hierarchy of controls since the five-tier model has better advertising:
ELIMINATION, SUBSTITUTION, ISOLATION;
ENGINEERING CONTROLS, ADMINISTRATIVE CONTROLS, Personal Protective Equipment;
Additionally:
PRESENTAITON, SESSION, TRANSPORT;
NETWORK, DATA-LINK, PHYSICAL;
<< APPLICATION -> ROLE
If it follows naturally through the maxim of “God Programmers Create God Programs,” actual and real implementation of this model would lead to a massive reduction in lead time for the Five stages of Project Management.
~A9
next prev parent reply other threads:[~2024-03-17 23:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-17 9:14 A few proposals, this time from the C++ standards committee Paul E. McKenney
2024-03-17 18:50 ` Linus Torvalds
2024-03-17 20:56 ` Paul E. McKenney
2024-03-17 20:50 ` Linus Torvalds
2024-03-17 21:04 ` Paul E. McKenney
2024-03-17 21:44 ` Linus Torvalds
2024-03-17 22:02 ` Paul E. McKenney
2024-03-17 22:34 ` Linus Torvalds
2024-03-17 23:46 ` Jonathan Martin [this message]
2024-03-18 0:42 ` Paul E. McKenney
2024-03-18 1:49 ` Linus Torvalds
2024-03-18 2:44 ` Paul E. McKenney
2024-03-18 2:57 ` Randy Dunlap
2024-03-18 4:42 ` Paul E. McKenney
2024-03-18 4:45 ` Randy Dunlap
2024-03-18 16:32 ` Linus Torvalds
2024-03-18 16:48 ` H. Peter Anvin
2024-03-19 7:41 ` Marco Elver
2024-03-19 8:07 ` Jakub Jelinek
2024-06-05 13:52 ` Paul E. McKenney
2024-06-05 18:08 ` Linus Torvalds
2024-06-05 18:24 ` Linus Torvalds
2024-06-05 19:16 ` Paul E. McKenney
2024-06-05 19:12 ` Paul E. McKenney
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=00E51206-C20A-4DAC-8DDB-71D2B74C8F55@icloud.com \
--to=workspace.public@icloud.com \
--cc=linux-toolchains@vger.kernel.org \
--cc=torvalds@linux-foundation.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).