IETF Logo Mail Archive

[dispatch] Re: Proposal for New Work: OODA-HTTP — Adaptive Security Framework for HTTP/HTTPS

Rachid Bouziane <contact@secroot.io> Thu, 03 July 2025 01:44 UTC

Return-Path: <contact@secroot.io>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AABB23D31BC3; Wed, 2 Jul 2025 18:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.868
X-Spam-Level:
X-Spam-Status: No, score=-1.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.232, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=secroot.io
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kVjHpz9m1EdB; Wed, 2 Jul 2025 18:44:18 -0700 (PDT)
Received: from out-02.shared.jellyfish.systems (out-02.shared.jellyfish.systems [63.250.43.109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 38E613D31BAF; Wed, 2 Jul 2025 18:44:18 -0700 (PDT)
Received: from prod-lbout-phx.jellyfish.systems (unknown [198.54.114.69]) by shared.jellyfish.systems (Postfix) with ESMTPA id 4bXfh06yLgz6yjj; Thu, 03 Jul 2025 01:44:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=secroot.io; s=default; h=Content-Transfer-Encoding:Content-Type:Message-ID:Subject:Cc:To: From:Date:MIME-Version:Sender:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=plceTkf6uVeyr6XMpcVNvWGmIcEWrfCey5MzAZN6JLc=; b=SBwabT+MCLsqvTHKuFN+nFu8yW NDGbwxMXgNP3QKlD610ruLi/ctUe88LtpIBQdifuNhZpukl+sT7gnGTE7u7YqQegprXq/lEv5eIb1 3N6jGGtYl798jHRbCXAJcDLRooj3TEbu1iL9yWyxZj/meA8YMBlXDOOLEsMbi5NdvjHQS3cyRcF0I zHnP9vMk53ZavwXZHtaCrVOMbrOK2JgcyhxhvJBgaDgrYfWsBlzfD87UHs0z/pJlVL9NV9ZtbGBOV W40k4z5jThA5ICHIaeD5B1rPJJ06ggGX+/rYEv3fIad5iGInN4GZfvoEjR0i11Oa7ohPtQDdU56ES 3/jTL8kA==;
Received: from [::1] (port=46670 helo=server190.web-hosting.com) by server190.web-hosting.com with esmtpa (Exim 4.98.2) (envelope-from <contact@secroot.io>) id 1uX8zo-00000003Oap-2tBB; Wed, 02 Jul 2025 21:44:16 -0400
MIME-Version: 1.0
Date: Wed, 02 Jul 2025 21:44:16 -0400
From: Rachid Bouziane <contact@secroot.io>
To: Lucas Pardue <lucas@lucaspardue.com>
User-Agent: Roundcube Webmail/1.6.11
Message-ID: <0fb1b438f095cd9288772754a2396b78@secroot.io>
X-Sender: contact@secroot.io
Organization: SecRoot
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: DTWTNMIWFAKR63A3TQW5M3EP2TN24V5T
X-Message-ID-Hash: DTWTNMIWFAKR63A3TQW5M3EP2TN24V5T
X-MailFrom: contact@secroot.io
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Dispatch <dispatch@ietf.org>, Dispatch Chairs <dispatch-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Re: Proposal for New Work: OODA-HTTP — Adaptive Security Framework for HTTP/HTTPS
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Qa_XIaSeQXe1XJ8wiTkulvgNmUo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>

Thanks a lot for your question.

DOTS focuses on signaling volumetric DDoS attacks to a mitigation 
server, typically via a dedicated control channel.
OODA-HTTP, in contrast, introduces a behavioral layer directly inside 
HTTP/HTTPS to allow each HTTP request to carry lightweight telemetry 
(via the X-OODA-Action header), enabling real-time context-aware 
response at the edge (block, challenge, rotate TLS keys, etc.).

It's more about individual behavioral defense (e.g. against bots, 
anomalous clients) than large-scale DDoS signaling.
We see it as complementary to DOTS, acting inside the HTTP/TLS runtime, 
not outside.

Happy to elaborate further if helpful.

Best regards,
Rachid Bouziane
SecRoot.io — OODA-HTTP Initiative

v2.39.1 | Report a Bug | By Email | System Status