Without taking a position on the merits of this technology, it's not clear to me what this has to with TLS. It seems to me that this is layered on top of HTTPS but doesn't entail any changes to TLS itself. Am I misunderstanding?
-Ekr On Tue, Jul 1, 2025 at 5:32 PM rachid bouziane <[email protected]> wrote: > Dear Rich, > > Thank you again for your thoughtful reading and constructive feedback. > > You are absolutely right — this first draft focuses on the strategic and > architectural positioning of OODA-HTTP, with implementation details > intentionally deferred. > We are currently finalizing a dedicated technical section (12.1) that > introduces the semantic vector engine and its temporal memory. This is > not a heavyweight AI module but a lightweight behavioral vectorization > layer. It enables each HTTP request to be interpreted within the OODA > loop (Observe → Orient → Decide → Act), allowing real-time, > context-aware defense. > Key point: HTTP packets only become semantically quantifiable — and > thus defensive — once observed and contextualized. This is the foundation > of active behavior in OODA-HTTP. > > This loop enables HTTPS to act rather than just transport. > The more OODA-HTTP is fed, the more defensive it becomes. > > We’d be glad to share this section with you before it is integrated into > the next draft, and would highly value your feedback. > > Please find attached a technical preview of Section 12.1, detailing the > semantic vector engine and its role in turning HTTP signals into > actionable defense vectors. > > Best regards, > Rachid Bouziane > [email protected] > SecRoot.io – OODA-HTTP Protocol Initiative > _______________________________________________ > TLS mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ TLS mailing list -- [email protected] To unsubscribe send an email to [email protected]
