IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 29 November 2025 01:43 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 AD7EB9248A38 for <rfc4082-update@mail2.ietf.org>; Fri, 28 Nov 2025 17:43:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.4
X-Spam-Level:
X-Spam-Status: No, score=-4.4 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_MED=-2.3, SPF_HELO_NONE=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=sandelman.ca
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 ov6nNXGY4tll for <rfc4082-update@mail2.ietf.org>; Fri, 28 Nov 2025 17:43:24 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 32D3E9248A30 for <rfc4082-update@ietf.org>; Fri, 28 Nov 2025 17:43:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C0E5918014 for <rfc4082-update@ietf.org>; Fri, 28 Nov 2025 20:43:23 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id 1iApTA3LDNrT for <rfc4082-update@ietf.org>; Fri, 28 Nov 2025 20:43:21 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1764380601; bh=zDqcPFnx7MvmuHPZZZFulbSsB/F19CdwvpGxkUVf5YA=; h=From:To:Subject:In-Reply-To:References:Date:From; b=bBJN1foJpx/uaQZ8vGQFJx3YnasjOJZCLHOmspzQgl/VvKkvAQuZvWI2/H1eBS1lz I6C9O3jdlQhPDczot/N2CYYwdPOpVAR5FR8m0Poy6ChGPjT7LqhfDjRQtSp1+0ufVh UzcuBrtrCs1CMpnsdpdsoE8LL5LtmXYJlfU36wayHexGQNJ5ncdZkuvRNr5JJ/wRY+ 7cHZ1rYCNt/sd/qZ5Od+BJAJ3nrsRmDCG2Que1Xt/bwLwrVkUyEBkYIJsS2qpl16ud EAcpHjdXcrHfenK9gYj6GeY9Yl4aPllSbTCJsZknVMD9KsDAPBR7lCQHyyoKcLHS+v c3l8YFY8P4FjQ==
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 095C918010 for <rfc4082-update@ietf.org>; Fri, 28 Nov 2025 20:43:21 -0500 (EST)
Received: from obiwan.sandelman.ca (obiwan.sandelman.ca [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id E747C18B for <rfc4082-update@ietf.org>; Fri, 28 Nov 2025 20:43:20 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: rfc4082-update@ietf.org
In-Reply-To: <e91984da-535d-4b15-9372-27d260bb2d7c@htt-consult.com>
References: <d11bcaf6-e2b2-4428-87e1-f4a6beaddb16@htt-consult.com> <30929.1764263220@obiwan.sandelman.ca> <e91984da-535d-4b15-9372-27d260bb2d7c@htt-consult.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; Emacs 30.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Fri, 28 Nov 2025 20:43:20 -0500
Message-ID: <18110.1764380600@obiwan.sandelman.ca>
Message-ID-Hash: CXWXAT2IAEWI3H2OU6WYFMG2BPCYKRO7
X-Message-ID-Hash: CXWXAT2IAEWI3H2OU6WYFMG2BPCYKRO7
X-MailFrom: mcr+ietf@sandelman.ca
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/f_C42vYVI4PzlytF-CG8OocKXhk>
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>

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.

    >> 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.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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