[rfc4082-update] Re: Start of github

Robert Moskowitz <rgm-sec@htt-consult.com> Tue, 09 December 2025 04:31 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 F18EA97C8666 for <rfc4082-update@mail2.ietf.org>; Mon, 8 Dec 2025 20:31:31 -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 7sNkjw5DsFbg for <rfc4082-update@mail2.ietf.org>; Mon, 8 Dec 2025 20:31:30 -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)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id CAF3F97C8660 for <rfc4082-update@ietf.org>; Mon, 8 Dec 2025 20:31:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=htt-consult.com; s=mail; t=1765254690; bh=MSJIuHTNf6Kxej496PKh/f2iMTFMfrBKr/9RV3sdcoE=; h=Date:Subject:To:References:From:In-Reply-To:From; b=I27NcS0izg1jAk2orF+0Vk5MnLdwuWASUUxE2mY+1u6Ie+GWej4jRk4pyVxIfNTDZ /IV1wq7sF6xnK80TJZS2lsa9t5IHlKpHr1I7wGcfQasenIbcwUw17CX6s8t/wy1ARp Zze2vKqYcXgqU8Ec9VxUJj/W+zPlTXSMxLK8YxGHnD8eG5u/OTe4JS3HWomjBHhVZ3 cOvZLWwqZiow776LrnC69GDNHefSeNB8vTvjfdgJOEKny+8ny5EMp/lbmFpPUtuC3i YDl6bZIo4gMN0ELA+6Zr3PjBS9p6Vpwl6plVdKJezm8rkgFMP94k2lU177cgOZPe4J EOXSbObClFHNw==
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)) (No client certificate requested) by klovia.htt-consult.com (Postfix) with ESMTPSA id 031494A010D for <rfc4082-update@ietf.org>; Mon, 8 Dec 2025 23:31:29 -0500 (EST)
Message-ID: <9b86071d-9402-4dff-87aa-60bbb711ad6b@htt-consult.com>
Date: Mon, 08 Dec 2025 23:31:29 -0500
MIME-Version: 1.0
Content-Language: en-US
To: rfc4082-update@ietf.org
References: <e62a8339-aeed-4918-9833-070851a9c646@htt-consult.com>
From: Robert Moskowitz <rgm-sec@htt-consult.com>
In-Reply-To: <e62a8339-aeed-4918-9833-070851a9c646@htt-consult.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Message-ID-Hash: 2DUBYOU66PXXOK5Q4VDDDEONLYD34EHZ
X-Message-ID-Hash: 2DUBYOU66PXXOK5Q4VDDDEONLYD34EHZ
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: 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/YTX9H6TBh1xhozswNaSD7JzU8jY>
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>

I also now have the pre-release ver of ICAO's doc 10169 - Aviation 
Common Certificate Policy

I have been told I can release this to the IETF, and I should get it up 
soon here.  Only sec 10.3.3 directly applies to SBAS and after our 
meeting today, we are most likely going to have to amend it in some way 
(expect it has already gone out!).

Well what is in 10.3.3 is what SBAS providers are currently building to.

So I will let you know when I get the ACCP uploaded.

On 12/8/25 11:22 PM, Robert Moskowitz wrote:
> 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
>
> _______________________________________________
> rfc4082-update mailing list -- rfc4082-update@ietf.org
> To unsubscribe send an email to rfc4082-update-leave@ietf.org