MIME-Version: 1.0
References: <0fb1b438f095cd9288772754a2396b78@secroot.io>
In-Reply-To: <0fb1b438f095cd9288772754a2396b78@secroot.io>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 3 Jul 2025 10:34:50 +0100
Message-ID: 
 <CA+9kkMB22zbfHXrzC61GqbkrafsD8q33bxhZCL=Ba_dCnFqBQA@mail.gmail.com>
To: Rachid Bouziane <contact@secroot.io>
Content-Type: multipart/alternative; boundary="0000000000005d217a0639031897"
Message-ID-Hash: 34A5O44IW45XY7VNSKN6RXY66ELJC6FR
CC: Lucas Pardue <lucas@lucaspardue.com>, Dispatch <dispatch@ietf.org>,
 Dispatch Chairs <dispatch-chairs@ietf.org>
Precedence: list
Subject: =?utf-8?q?=5Bdispatch=5D_Re=3A_Proposal_for_New_Work=3A_OODA-HTTP_=E2=80=94_?=
	=?utf-8?q?Adaptive_Security_Framework_for_HTTP/HTTPS?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/dispatch/eUMkLjkDucJPYYwWRGBqJANdsec>

--0000000000005d217a0639031897
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Rachid,

Without comment on the broader proposal, may I draw your attention to RFC
6648: https://datatracker.ietf.org/doc/html/rfc6648.  This is a BCP
recommending against the use of X- headers and similar constructs.
Whatever the dispatch outcome, I suggest you consider its advice in updates
to your design.

best regards,

Ted Hardie

On Thu, Jul 3, 2025 at 2:45=E2=80=AFAM Rachid Bouziane <contact@secroot.io>=
 wrote:

> 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 =E2=80=94 OODA-HTTP Initiative
>
> _______________________________________________
> dispatch mailing list -- dispatch@ietf.org
> To unsubscribe send an email to dispatch-leave@ietf.org
>

--0000000000005d217a0639031897
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">Hi =
Rachid,</div><div class=3D"gmail_default" style=3D"font-size:small"><br></d=
iv><div class=3D"gmail_default" style=3D"font-size:small">Without comment o=
n the broader proposal, may I draw your attention to RFC 6648:=C2=A0<a href=
=3D"https://datatracker.ietf.org/doc/html/rfc6648">https://datatracker.ietf=
.org/doc/html/rfc6648</a>.=C2=A0 This is a BCP recommending against the use=
 of X- headers and similar constructs.=C2=A0 Whatever the dispatch outcome,=
 I suggest you consider its advice in updates to your design.</div><div cla=
ss=3D"gmail_default" style=3D"font-size:small"><br></div><div class=3D"gmai=
l_default" style=3D"font-size:small">best regards,</div><div class=3D"gmail=
_default" style=3D"font-size:small"><br></div><div class=3D"gmail_default" =
style=3D"font-size:small">Ted Hardie</div></div><br><div class=3D"gmail_quo=
te gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul=
 3, 2025 at 2:45=E2=80=AFAM Rachid Bouziane &lt;<a href=3D"mailto:contact@s=
ecroot.io">contact@secroot.io</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">Thanks a lot for your question.<br>
<br>
DOTS focuses on signaling volumetric DDoS attacks to a mitigation <br>
server, typically via a dedicated control channel.<br>
OODA-HTTP, in contrast, introduces a behavioral layer directly inside <br>
HTTP/HTTPS to allow each HTTP request to carry lightweight telemetry <br>
(via the X-OODA-Action header), enabling real-time context-aware <br>
response at the edge (block, challenge, rotate TLS keys, etc.).<br>
<br>
It&#39;s more about individual behavioral defense (e.g. against bots, <br>
anomalous clients) than large-scale DDoS signaling.<br>
We see it as complementary to DOTS, acting inside the HTTP/TLS runtime, <br=
>
not outside.<br>
<br>
Happy to elaborate further if helpful.<br>
<br>
Best regards,<br>
Rachid Bouziane<br>
SecRoot.io =E2=80=94 OODA-HTTP Initiative<br>
<br>
_______________________________________________<br>
dispatch mailing list -- <a href=3D"mailto:dispatch@ietf.org" target=3D"_bl=
ank">dispatch@ietf.org</a><br>
To unsubscribe send an email to <a href=3D"mailto:dispatch-leave@ietf.org" =
target=3D"_blank">dispatch-leave@ietf.org</a><br>
</blockquote></div>

--0000000000005d217a0639031897--