[rfc4082-update] Start of github

Robert Moskowitz <rgm-sec@htt-consult.com> Tue, 09 December 2025 04:23 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 27CE497C79B4 for <rfc4082-update@mail2.ietf.org>; Mon, 8 Dec 2025 20:23:10 -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 OxjuqynzNlsO for <rfc4082-update@mail2.ietf.org>; Mon, 8 Dec 2025 20:23:09 -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 A665797C79AF for <rfc4082-update@ietf.org>; Mon, 8 Dec 2025 20:23:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=htt-consult.com; s=mail; t=1765254183; bh=uOdg54qqS7LGZx7r3d6KgOXx3HK8qtCHZOYhb72naWo=; h=Date:To:From:Subject:From; b=cEldu6E9ghqY0UiVc+n8FZNUoa5qq6GSPX6NBIA689gu6wibfJzdoic7GHTtesQKo MwLNazar2gCroyAzsepHRDoKq/aXTYiaVtFCw3KNWU/DFC4u+1ZXzS4Lj2dO5HdDX6 tGxRVDUji0HVzNz2cWgHBUlKKd145gHXiXjDMRjbWmsYwO63zb5Nu+d+RnR/9ms/ZC WaS2jM46KXn+3b48HYTBUw9KtQnETl9m7RW3e6ZOg9bJGzyBey782WKZKuR+xsHfHf Z0VMuykOHF0XYTzZWKRwbsRZZj+Qmz3PiQR6oJWCQcXMIrltv/VARLlB9LNyl9h7jL be386u5oQbf0A==
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 ED0B34A03FF for <rfc4082-update@ietf.org>; Mon, 8 Dec 2025 23:23:02 -0500 (EST)
Message-ID: <e62a8339-aeed-4918-9833-070851a9c646@htt-consult.com>
Date: Mon, 08 Dec 2025 23:22:47 -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: VX273NVBIXV3HODKKXC5WWZSWWA7TWCY
X-Message-ID-Hash: VX273NVBIXV3HODKKXC5WWZSWWA7TWCY
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] Start of github
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/9uYADOjy5SXfS3ROyk7MeBmRS1s>
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>

Sarah Grant helped me out by setting up our github.

I just uploaded:

https://github.com/rgmhtt/SBAS/blob/main/JWGs15_WP27rev1_SBAS%20Authentication%20SARPs_251117.pdf

Which is the ICAO SBAS Authentication working document.  Officially 
released to me to post here.

This is the doc that details their rfc4082 updated implementation and 
what I am working to extract into the start of rfc4082-update draft.

Lots of hard work from the SBAS Auth study group.

I took the working doc, accepted all changes, deleted all comments, and 
exported to pdf.

Fun reading....

Bob