IETF Logo Mail Archive

[rfc4082-update] Re: Welcome to rfc4082-update

Robert Moskowitz <rgm-sec@htt-consult.com> Mon, 01 December 2025 20:47 UTC

Return-Path: <rgm-sec@htt-consult.com>
X-Original-To: rfc4082-update@mail2.ietf.org
Delivered-To: rfc4082-update@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3481F938C3EB for <rfc4082-update@mail2.ietf.org>; Mon, 1 Dec 2025 12:47:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_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=htt-consult.com
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 T0IVzerQqrBI for <rfc4082-update@mail2.ietf.org>; Mon, 1 Dec 2025 12:47:33 -0800 (PST)
Received: from klovia.htt-consult.com (klovia.htt-consult.com [23.123.122.149]) (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 45A57938BDB4 for <rfc4082-update@ietf.org>; Mon, 1 Dec 2025 12:46:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=htt-consult.com; s=mail; t=1764622007; bh=+/7HOuxJG4wOSGW1ogqwXJ+5EZIHhBuH9df7H173NqE=; h=Date:Subject:To:References:From:In-Reply-To:From; b=UmzoMtPjDu/ZCA4lSd1oP+XS1aLRixffrpPJIBd8Pplj5sURKLQkQfKk1tetUNob2 uvzJBWdpa/BRHKmLsiUzDEHC/bjBVODhrcFhuazyfmAf7MKn7OkxjG/VMMAim9YDuZ YuJlexO+sYVRuYaLyJ4BfBREyCEVZ4sq53e5oQfaOGwtwZcua4qtqCxXt5sAGu9TpH fzx9sUeUQsfvyWJiGz+vqDOwN2ruSqe94LcV55/SsFfvFMHmiMZ8/mZkOw7uBVMfZI 7AGkLlqKdvsOi2Z0qC54I4fbfOEeZkkcUOV7WAqK2yg7iaaatq2S8yCzW5WOgE/XlF ZoRxJfsiFlXgg==
Received: from authenticated-user (klovia.htt-consult.com [23.123.122.149]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by klovia.htt-consult.com (Postfix) with ESMTPSA id D65C04A0327; Mon, 1 Dec 2025 15:46:47 -0500 (EST)
Message-ID: <f943fa58-8c13-4a4f-a306-4687c6371494@htt-consult.com>
Date: Mon, 01 Dec 2025 15:46:47 -0500
MIME-Version: 1.0
Content-Language: en-US
To: Michael Richardson <mcr+ietf@sandelman.ca>, rfc4082-update@ietf.org
References: <d11bcaf6-e2b2-4428-87e1-f4a6beaddb16@htt-consult.com> <30929.1764263220@obiwan.sandelman.ca> <e91984da-535d-4b15-9372-27d260bb2d7c@htt-consult.com> <18110.1764380600@obiwan.sandelman.ca>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
In-Reply-To: <18110.1764380600@obiwan.sandelman.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: XICU4RN36SAKCWLLZFIWEOOQXR4OUX32
X-Message-ID-Hash: XICU4RN36SAKCWLLZFIWEOOQXR4OUX32
X-MailFrom: rgm-sec@htt-consult.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; 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: [rfc4082-update] Re: Welcome to rfc4082-update
List-Id: "Discussions for updating TESLA (Timed Efficient Stream Loss-Tolerant Authentication), RFC 4082." <rfc4082-update.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc4082-update/9rrYJKd0DO73KSzum2ALevQNm20>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc4082-update>
List-Help: <mailto:rfc4082-update-request@ietf.org?subject=help>
List-Owner: <mailto:rfc4082-update-owner@ietf.org>
List-Post: <mailto:rfc4082-update@ietf.org>
List-Subscribe: <mailto:rfc4082-update-join@ietf.org>
List-Unsubscribe: <mailto:rfc4082-update-leave@ietf.org>


On 11/28/25 8:43 PM, Michael Richardson wrote:
> Robert Moskowitz <rgm-sec@htt-consult.com> wrote:
>      > On 11/27/25 12:07 PM, Michael Richardson wrote:
>      >> Bob, Who is using RFC4082 today, and what for?
>
>      > I only know for sure its planned use for SBAS Authentication.  So receivers
>      > can put trust into GNSS messaging.
>
> Planned use is not installed base.

You have been to ICAO and have a glimering of their processes.  :)

It would take some major (cheaper!) better way for this not to happen.  
EU/Galileo is really committed to it.

>
>      >> That is, how important is bits-on-the-wire compatibility?
>
>      > It will tend not to be.  Each use will have its own hash size support and key
>      > reveal protocol.  Of course each hash will have its own construction.  Thus
>      > the rfc has to be general enough with good use cases in appendices to help
>      > potential users.
>
> Good to understand.... it means we have no obligation to make anything
> backwards compatible.

that is how I see it.

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