[Dance] DANCE use for DRIP Network Remote ID

Robert Moskowitz <rgm-sec@htt-consult.com> Fri, 24 June 2022 14:27 UTC

Return-Path: <rgm-sec@htt-consult.com>
X-Original-To: dance@ietfa.amsl.com
Delivered-To: dance@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12104C15CF25 for <dance@ietfa.amsl.com>; Fri, 24 Jun 2022 07:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pHqz9u9kXxpS for <dance@ietfa.amsl.com>; Fri, 24 Jun 2022 07:27:34 -0700 (PDT)
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 6406AC15D499 for <dance@ietf.org>; Fri, 24 Jun 2022 07:27:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by z9m9z.htt-consult.com (Postfix) with ESMTP id E21386250B for <dance@ietf.org>; Fri, 24 Jun 2022 10:26:46 -0400 (EDT)
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 FgZ4WeTqqN9R for <dance@ietf.org>; Fri, 24 Jun 2022 10:26:40 -0400 (EDT)
Received: from [192.168.160.11] (unknown [192.168.160.11]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by z9m9z.htt-consult.com (Postfix) with ESMTPSA id E9CBF624D4 for <dance@ietf.org>; Fri, 24 Jun 2022 10:26:39 -0400 (EDT)
Message-ID: <43933f77-6abf-7750-f5e9-e3d0e20135d5@htt-consult.com>
Date: Fri, 24 Jun 2022 10:27:22 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0
To: dance@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
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/QC7ZaPC1dHMj2VCPXCJxbB7V7Oc>
Subject: [Dance] DANCE use for DRIP Network Remote ID
X-BeenThere: dance@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DANE Authentication for Network Clients Everywhere <dance.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dance>, <mailto:dance-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dance/>
List-Post: <mailto:dance@ietf.org>
List-Help: <mailto:dance-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dance>, <mailto:dance-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 24 Jun 2022 14:27:35 -0000

Please review:

Sec 3.2.1.2 in draft-moskowitz-drip-secure-nrid-c2

for DANCE (and DANE) usage.  Any improvement in this section is really 
appreciated.

In Sec 5.6 of draft-ietf-drip-registries

We get where the TLSA RR is created as part of the UAS registration.  
Text here needs lots of help, I have already sent off one set of changes 
to the editor.

So this COULD be a major use case for DANCE.  I have a meeting next week 
at ICAO in Montreal where we will be defining the parts of the ICAO 
International Aviation Trust Framework (IATF) as part of the Global 
Resilient Aviation Interoperable Network (GRAIN) for a 6 month PoC.

I want to ensure that DANCE/DANE is included beyond their grand PKI 
model....

If my DRIP, IPSECME, TLS, LPWAN, CFRG participation does not conflict I 
can add to the DANCE discussion and adding this use case to the 
architecture.  :)

Bob