IETF Logo Mail Archive

[rfc4082-update] Welcome to rfc4082-update

Robert Moskowitz <rgm-sec@htt-consult.com> Wed, 26 November 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 309939156EA1 for <rfc4082-update@mail2.ietf.org>; Wed, 26 Nov 2025 12:47:30 -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 by_Y3rR-WlJB for <rfc4082-update@mail2.ietf.org>; Wed, 26 Nov 2025 12:47:29 -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 F0BA69156E91 for <rfc4082-update@ietf.org>; Wed, 26 Nov 2025 12:47:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=htt-consult.com; s=mail; t=1764190045; bh=5r0M8LhCGqtCQhuh91tZkv2YPbYH4ZwlY4Vi1KMufKg=; h=Date:To:From:Subject:From; b=pqqJnY5ppCo8Jiyg5Nn460CPtxUrGnRX8Gk1iqyBKUsn5j4dRmWmmtYMZsSeWwSm/ xohf4O7IniUO1iVfXTliWR4GvAHO6imIODseDkV6cxVt4AyW5dPGTUKM28Uik1zexj 4oonYAVKfwn8/sQGKeAwrRrcG9EsPnhmq6ntyrVG8h46DQx2F4ckylYIRjlqrgll5l OjugbI8AXXIocmC/EfTt6PL7QFrqHqo/cWqcW0KvPbI6fz5NuSaY3iE598GNJBOkOT 34iB/D8zO4/fMQNnEcKJXVsiSkTfRBLffMZ/IStM0dBkyCebItyRUy4tR0GhL2gJ2y E+MjLjgTUr8ag==
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 221B54A0125 for <rfc4082-update@ietf.org>; Wed, 26 Nov 2025 15:47:25 -0500 (EST)
Message-ID: <d11bcaf6-e2b2-4428-87e1-f4a6beaddb16@htt-consult.com>
Date: Wed, 26 Nov 2025 15:47:24 -0500
MIME-Version: 1.0
To: rfc4082-update@ietf.org
Content-Language: en-US
From: Robert Moskowitz <rgm-sec@htt-consult.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: BKRTVGXHHSQAXCBKINLOOZG5SSFCTLU3
X-Message-ID-Hash: BKRTVGXHHSQAXCBKINLOOZG5SSFCTLU3
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] 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/GT7bhpX3vTSpp0PJJgQwJzE1sN8>
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>

Welcome to rfc4082-update.

This list's purpose is to discuss updating rfc4082 in light of current 
uses, starting with the ICAO GNSS SBAS Authentication.

The current draft is:

https://datatracker.ietf.org/doc/draft-moskowitz-tesla-update-gnss-sbas/

In light of discussions with the IESG on setting up this list I will be 
changing the draft to something like:

draft-moskowitz-rfc4082-update

The use of 4082 is to lessen any marketing confusion.  Try googling 
Tesla.  Now add ietf.  How did it go?

I was part of the IAB trademark discussions back in '97 or there about.  
There is no trademark issue here, but perhaps some market presecption.  
Since this is really an update to rfc4082, thus the name.  But as a fun 
note the oldest draft I can find is:

https://datatracker.ietf.org/doc/draft-irtf-smug-tesla/

Published 11-17-00 so...

Anyway enough with the naming issues.

========================================


My goal is to take all current work that has expanded on how 4082 works 
and incorporate those expansions into an update.  I will then have 
Appendices to cover specific uses to show how they align with the body 
of the draft.

Right now I only have the work being done in the International Civil 
Aviation Organization (ICAO) in their Global Navigation Satellite System 
(GNSS, e.g. US GPS) Satellite-based augmentation system (SBAS) 
authentication protocol.

Others are welcome to join in.

I will be working with my co-list maintainer, Sarah Grant to set up a 
Github.  I am working with ICAO to get they documents (still drafts) 
posted there.  There are also papers that the ICAO work is based on, and 
I will work on getting them posted.  Or at least a text file with the 
URL(s) of where to get them.

All comments are welcomed.  I will be working on a new draft.  Goal is 
the end of the week.  But before end of next week (week of Dec 7 I am 
back in Montreal for the ICAO Trust Framework Panel). So I want an 
updated draft here to feed into my TFP contributions.

Thank you for joining.

Robert Moskowitz

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