[dispatch] Re: OODA-HTTP — Standard Header Naming Consideration
Rachid Bouziane <contact@secroot.io> Thu, 03 July 2025 23:39 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 6D7FE3DD8F85 for <dispatch@mail2.ietf.org>; Thu, 3 Jul 2025 16:39:00 -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 g3MsOB3hhLBg for <dispatch@mail2.ietf.org>; Thu, 3 Jul 2025 16:39:00 -0700 (PDT)
Received: from out-12.shared.jellyfish.systems (out-12.shared.jellyfish.systems [63.250.43.78]) (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 E82153DD8F80 for <dispatch@ietf.org>; Thu, 3 Jul 2025 16:38:59 -0700 (PDT)
Received: from prod-lbout-phx.jellyfish.systems (unknown [198.54.114.69]) by shared.jellyfish.systems (Postfix) with ESMTPA id 4bYCry6JWGzHtT4; Thu, 03 Jul 2025 23:38:58 +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=UQ6f6PDrVmvo6KhKgoUvae9c4ws53qXvbOo/7FFKlE0=; b=WDTyQWvd9sqYaLJMqQ2fhpv9Z6 YivREPLpGbEqOlSWNFmY37wVKbRNC2uVIozRotcqvUHsURZot+7y9SVXe5iPrp6l5bPxGMIKXwGzK kNwKlLcJKLanpDGhAQiKhBgtoZkzOOijXPkFP6LW3c2zIQStQQ94u/lrLmyN2ZBq81ksxl06jmNoM 3x4BX/ZVm92ieDpNXPnmMQmMOL+M5snnfeRugJaMBlTuzRS2I84FUF9CvAfgNP80qJkBCLYj82WFw yD89KcJ5fYKD/Vfdy1aI6riEjXUvlY2DSsj8JGYcFKx8y/oz3mc39cAwm28RX9iMlmJPcISNbNufT 3c+23aPQ==;
Received: from [::1] (port=42672 helo=server190.web-hosting.com) by server190.web-hosting.com with esmtpa (Exim 4.98.2) (envelope-from <contact@secroot.io>) id 1uXTW6-00000005B5L-2cfU; Thu, 03 Jul 2025 19:38:58 -0400
MIME-Version: 1.0
Date: Thu, 03 Jul 2025 19:38:58 -0400
From: Rachid Bouziane <contact@secroot.io>
To: worley@ariadne.com
User-Agent: Roundcube Webmail/1.6.11
Message-ID: <8098bbb70b18b27cfbc67b9952e2a200@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: R3IFFIGEAGYQB6EBXLHR6VFJQXZZDN3S
X-Message-ID-Hash: R3IFFIGEAGYQB6EBXLHR6VFJQXZZDN3S
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>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Re: OODA-HTTP — Standard Header Naming Consideration
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/spilHDgsAa1ciV8XKCGhUGpf_cw>
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>
Dear Dale, Thank you very much for your thoughtful remarks and for sharing your experience regarding the use of "X-" headers in IETF protocols. You're absolutely right: the X-OODA-Action header was introduced in the early drafts of OODA-HTTP as a non-standard placeholder — precisely to avoid confusion during the exploration and prototyping phase. Now that the protocol is under discussion as a potential Working Group item, we fully agree that the use of the "X-" prefix is no longer appropriate. As you clearly pointed out, standardized headers should be properly named to reflect their intended status, and we will revise the header in future versions accordingly — possibly adopting OODA-Action or an alternative consistent with IETF conventions. Thank you again for your helpful insight. Your input helps us align the draft with IETF norms and community expectations. Warm regards, Rachid Bouziane SecRoot.io — OODA-HTTP Initiative
- [dispatch] Re: OODA-HTTP — Standard Header Naming… Rachid Bouziane