[Drip] Claims, Attestations, and Certificates

Robert Moskowitz <rgm@labs.htt-consult.com> Wed, 18 November 2020 21:10 UTC

Return-Path: <rgm@labs.htt-consult.com>
X-Original-To: tm-rid@ietfa.amsl.com
Delivered-To: tm-rid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55F323A0C99 for <tm-rid@ietfa.amsl.com>; Wed, 18 Nov 2020 13:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVXtxA-iV5Ta for <tm-rid@ietfa.amsl.com>; Wed, 18 Nov 2020 13:10:24 -0800 (PST)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [23.123.122.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCAD63A0C94 for <tm-rid@ietf.org>; Wed, 18 Nov 2020 13:10:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id F2CD0626AF for <tm-rid@ietf.org>; Wed, 18 Nov 2020 16:10:22 -0500 (EST)
X-Virus-Scanned: amavisd-new at htt-consult.com
Received: from z9m9z.htt-consult.com ([127.0.0.1]) by localhost (z9m9z.htt-consult.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 0f6TKLIVTm2Q for <tm-rid@ietf.org>; Wed, 18 Nov 2020 16:10:19 -0500 (EST)
Received: from lx140e.htt-consult.com (unknown [192.168.160.29]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id D0E60625F7 for <tm-rid@ietf.org>; Wed, 18 Nov 2020 16:10:18 -0500 (EST)
To: "tm-rid@ietf.org" <tm-rid@ietf.org>
From: Robert Moskowitz <rgm@labs.htt-consult.com>
Message-ID: <a8365015-d304-05dc-874e-2e1ef28257ed@labs.htt-consult.com>
Date: Wed, 18 Nov 2020 16:10:09 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/tm-rid/1GSZuSQMoKYa64zpliCW6pm-uT0>
Subject: [Drip] Claims, Attestations, and Certificates
X-BeenThere: tm-rid@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Drone Remote Identification Protocol <tm-rid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tm-rid/>
List-Post: <mailto:tm-rid@ietf.org>
List-Help: <mailto:tm-rid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tm-rid>, <mailto:tm-rid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2020 21:10:26 -0000

This is more on the CAC subject after lots of thoughts about who is on 1st.

A HHIT is a Claim.

The entity putting forward the HHIT is making a statement, without proof 
that there is a HI registered to the RAA|HDA and the hash component of 
the HHIT is derived from all the appropriate information following the 
ORCHID function.

The Self-Attestation is an Attestation/Claim of HI ownership.

Through the signature process, the entity putting forward the 
Self-Attestation is proving ownership of a keypair.  Validation of this 
proof does require obtaining the HI; it is CLAIMED that the RAA|HDA in 
the HHIT can provide the HI needed for the proof.

The Offline-Attestation is a full Attestation of all facts.

The 'internal' HDA Attestation of HI registration with the HDA is just 
an Attestation, not a Certificate (see below).  The 'outer' envelope is 
an Attestation of owning the HI registered and signing.

Finally, why an Attestation and not a Certificate?

In my view, a Certification of Registration would contain more 
information than currently in the HDA HI registration Attestation. 
Minimally it should have a registration date and end of registration 
period date.  Probably more, but this is sufficient to place it as an 
Attestation, not a Certificate.

Thus the terminology I have used in draft-ietf-drip-rid.

Next we can talk about all the objects in the claims draft....

Fun stuff!

Bob