[dispatch] Proposal: OODA-HTTP — Behavioral Extension to HTTP with TLS Coordination
Rachid Bouziane <contact@secroot.io> Wed, 02 July 2025 20:09 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 0363D3D14ECC; Wed, 2 Jul 2025 13:09:28 -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 zBS7hhUC4S8e; Wed, 2 Jul 2025 13:09:27 -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 621A73D14EC7; Wed, 2 Jul 2025 13:09:27 -0700 (PDT)
Received: from prod-lbout-phx.jellyfish.systems (unknown [198.54.114.69]) by shared.jellyfish.systems (Postfix) with ESMTPA id 4bXWFc3JR6z705b; Wed, 02 Jul 2025 20:09:24 +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:To: From:Date:MIME-Version:Sender:Reply-To:Cc: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=xcsnPqtlMPidZzTNobYqR/LVpepkBGQBhn0lbZeMgJs=; b=kTzaWeJIQGglxboZyAJn5NW09S kJ0DC15srqh61wwNt3JQomF0qMAbFzCrwyzCKgVUGMJcDOr7BEf5nDV79C0O3JSLWp4iuuFwmHke9 P+3k7HyyzDbS4CGtrhoTAQKG8upxM/yLL92SOqRbSec7mddariRHMZxPSHdzMWY5igrSoJ1uL0D8w sHdDeKOwglcn0Gu9XTNGxj18465xV+/pWvRHuCQ2/QkdFDJrAptv+bOQRyM1T9bY3vs6w9DEUeZSX uO+XQ2U1+bhhmxD7k9C7vW9jSj3OMvTiIDZIdDr7Bryjq7MDYzTYOZ/mZyWq0JQwttrDUGmgKCVkU m9kveYog==;
Received: from [::1] (port=34404 helo=server190.web-hosting.com) by server190.web-hosting.com with esmtpa (Exim 4.98.2) (envelope-from <contact@secroot.io>) id 1uX3lk-0000000FxSS-0gTy; Wed, 02 Jul 2025 16:09:24 -0400
MIME-Version: 1.0
Date: Wed, 02 Jul 2025 16:09:24 -0400
From: Rachid Bouziane <contact@secroot.io>
To: dispatch@ietf.org, dispatch-chairs@ietf.org
User-Agent: Roundcube Webmail/1.6.11
Message-ID: <1985eae0d547f4319de10186ea07b06b@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: HNDSNEQNPX4YVL37T7Q3SENP6TBCIFRL
X-Message-ID-Hash: HNDSNEQNPX4YVL37T7Q3SENP6TBCIFRL
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Proposal: OODA-HTTP — Behavioral Extension to HTTP with TLS Coordination
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/Zu7UUgLW7q1SZiVegNApVCrILmo>
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>
Hello Dispatch WG, I'd like to propose OODA‑HTTP as a candidate for new work in the ART area. OODA‑HTTP is a behavioral extension to HTTP/HTTPS and HTTP/3, adding dynamic runtime decisions communicated via the X‑OODA‑Action header, coordinated with TLS context (quantum resistance, key rotation, etc.). Key points: - Problem: current HTTP/TLS lacks mechanisms for real‑time adaptive defense. - Motivation: bot mitigation, behavioral anomaly response, TLS adaptive policies. - Deliverables: HTTP spec extensions + integration guidance with TLS environment. - Interest already received from experts (Rich Salz, Eric Rescorla). - OODA‑HTTP draft is available: https://datatracker.ietf.org/doc/draft-secroot-ooda-http/ Could this be added to the agenda for dispatching at IETF 123? Thanks, Rachid Bouziane
- [dispatch] Proposal: OODA-HTTP — Behavioral Exten… Rachid Bouziane