[rfc4082-update] Re: Welcome to rfc4082-update
Robert Moskowitz <rgm-sec@htt-consult.com> Fri, 28 November 2025 13:38 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 978A89214036 for <rfc4082-update@mail2.ietf.org>; Fri, 28 Nov 2025 05:38:46 -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=unavailable 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 4xx76_atiZgm for <rfc4082-update@mail2.ietf.org>; Fri, 28 Nov 2025 05:38:45 -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 239BD921402A for <rfc4082-update@ietf.org>; Fri, 28 Nov 2025 05:38:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=htt-consult.com; s=mail; t=1764337124; bh=dvQ5esHE3lTHFlzI37GRuT17HnogSMpz2p0Y1qAtIQg=; h=Date:Subject:To:References:From:In-Reply-To:From; b=UAYJV8DPYd+CSOrgMGNEzUSUMlqpiHrd/o4a4/YSb909zsJLQ+0aKwDPofEqHuCFN MqQjr7XYDIWbz+G5ElwNGgMj16TNmmQ8ZPJick6KeoSBMoTV0Q53pDErQjwxcd1i9I v8vhrKuW8Vr+unXn9F3pACAjka1913r8P59od9xPnxmITInVyE/rz7zgYPArVKQ2X8 DYtO8APd+uwXNc0Nh3bT7naaGt2Oed0EfZJYNsgUzR0P9tNjok5nQ1vY4wnVqF0YEZ hBPFEJdSirYm9sHC0YoFjD17IYk47HBh0Nt4o5KZE7VRLhBQEtRbPaW5rSK0MVbplF vdD1wiZJY3irA==
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 27B774A0125; Fri, 28 Nov 2025 08:38:44 -0500 (EST)
Message-ID: <e91984da-535d-4b15-9372-27d260bb2d7c@htt-consult.com>
Date: Fri, 28 Nov 2025 08:38:43 -0500
MIME-Version: 1.0
Content-Language: en-US
To: Michael Richardson <mcr+ietf@sandelman.ca>, Robert Moskowitz <rgm-sec=40htt-consult.com@dmarc.ietf.org>, rfc4082-update@ietf.org
References: <d11bcaf6-e2b2-4428-87e1-f4a6beaddb16@htt-consult.com> <30929.1764263220@obiwan.sandelman.ca>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
In-Reply-To: <30929.1764263220@obiwan.sandelman.ca>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: XUGGR3WGG2DVZZAOJ5PFWMTKMFBQZRRS
X-Message-ID-Hash: XUGGR3WGG2DVZZAOJ5PFWMTKMFBQZRRS
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/Ij_1j05WZAKYZTHXPJpVVpegsBg>
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/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. I hear soft talk of uses in NORM. Maybe some of those users will devulge enough information that we can reference that. There are a number proposals for its use in ADS-B. I am working on figuring out which to use in my ADS-B proposal.... I would like to think that we will make enough traffic here to draw them in. > 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. > I remember trying to come up with some security for wi-fi beacons back in > 2003, and somehow, I never knew about this protocol. (My creation was > conceptually the same) I was aware of it then. It was in msec around that time already. I think... Briscoe was really pushing it. At least in hall talks. I probably had conversations with other 4082 authors back then. > > -- > Michael Richardson <mcr+IETF@sandelman.ca> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > > > _______________________________________________ > rfc4082-update mailing list -- rfc4082-update@ietf.org > To unsubscribe send an email to rfc4082-update-leave@ietf.org
- [rfc4082-update] Welcome to rfc4082-update Robert Moskowitz
- [rfc4082-update] Re: Welcome to rfc4082-update Michael Richardson
- [rfc4082-update] Re: Welcome to rfc4082-update Robert Moskowitz
- [rfc4082-update] Re: Welcome to rfc4082-update Michael Richardson
- [rfc4082-update] Re: Welcome to rfc4082-update Robert Moskowitz