Re: [Dance] DANCE use for DRIP Network Remote ID

Joey Salazar <joeygsal@gmail.com> Fri, 24 June 2022 16:24 UTC

Return-Path: <joeygsal@gmail.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 B7274C15CF4A for <dance@ietfa.amsl.com>; Fri, 24 Jun 2022 09:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 J4U3yjqZhoNS for <dance@ietfa.amsl.com>; Fri, 24 Jun 2022 09:24:32 -0700 (PDT)
Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 4E15CC14CF0D for <dance@ietf.org>; Fri, 24 Jun 2022 09:24:32 -0700 (PDT)
Received: by mail-pj1-x102a.google.com with SMTP id l2so2074303pjf.1 for <dance@ietf.org>; Fri, 24 Jun 2022 09:24:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gsQY3EqDZaVP/fmhw2cmsnuHw8Ancb4ICjdsI9QRO/E=; b=OI2DKai9F0XOP/o7/JDVK5TtT0oebeB5l3ZrbqaPKsdK38dKX5uKgvkywxIa+XZgGQ sWi+W0t+riyTRB1NRzT6tUC6rEYsHPntwqmkuJLAGyaSQM1MIkE4CarYCa50MWSWSd+K GYN0o8DaUot8aIby2ZlMWjSw7/1FIHDNbE1XVegVKS2bP0VSPixSeqpV/nCRglhxZAQp dMDkV2BsPmi/4Vhi1RVtt4+8TkTgg9tAdMPkxWmc6JXRTXF4Gvm+wnUcwX8qiGTH12jA 6TaJiOIV9BF8HfJhnljOl4tGTKQA3uSU27qvagsHMl2oCcoen5+Rx1p5S40b/IdGGHOb 8sZQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gsQY3EqDZaVP/fmhw2cmsnuHw8Ancb4ICjdsI9QRO/E=; b=v36ACyMexIHmW6csQTMPbVSxGDVTNxsWANl2kvDgc5cwmbnL49U4sgQHhk1B6n5nF9 IcbbvA4KguE09g4R0j1qJcqZkaYNWse0yVk+zE3JSzZYzzja+htF75srz3e0daneJwkk hrle+NQOZbXfWiwaKjDY543vMe8/D8M6T5KSDMXcbmV4uzI15rkZIRaimLGGIHk/fT3T 5XkS0PZWIEnYdg6zHloMkkfUR/ZMFNPOR80LWzgAU2Fq8Com+yXH2b0a3k5bkppE9Rs1 2tRZlu3jdnwXBwCtIuU1rVS9lH88TRCOcxlo2Bwb+lltaAQ+riqyFcsBGqkKIW4blIx1 qS7Q==
X-Gm-Message-State: AJIora+h7dMHaJ+YX+wRC/IO1Po3R/pC+DFYwu/9ZORZ2omrD7/RpcrY nJ9ylLNOSxBxBWz+WsxZfhXn3egHBRpU0fVT2R6XPiHa96Y=
X-Google-Smtp-Source: AGRyM1sJglxvn5SO9uBWweCoKfmqrKSTyvuTgYMtG2QbjCHXw05/Dr0PXmkl3Mfy5uhcx2NpBxPFnHQh9fKaHSiDr5Q=
X-Received: by 2002:a17:90b:38c8:b0:1e8:5202:f6d4 with SMTP id nn8-20020a17090b38c800b001e85202f6d4mr5061406pjb.149.1656087871725; Fri, 24 Jun 2022 09:24:31 -0700 (PDT)
MIME-Version: 1.0
References: <43933f77-6abf-7750-f5e9-e3d0e20135d5@htt-consult.com>
In-Reply-To: <43933f77-6abf-7750-f5e9-e3d0e20135d5@htt-consult.com>
From: Joey Salazar <joeygsal@gmail.com>
Date: Fri, 24 Jun 2022 18:28:48 +0200
Message-ID: <CAEhLraisaddstCUOJkuMrSN+1WRKYAoj+xSkOU+JGDp-ebH7eA@mail.gmail.com>
To: Robert Moskowitz <rgm-sec@htt-consult.com>
Cc: dance@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004fa79e05e23401e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dance/80BKLkjG_GIetZZfxCPooJvaxvE>
Subject: Re: [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 16:24:32 -0000

On Fri, Jun 24, 2022 at 4:27 PM Robert Moskowitz <rgm-sec@htt-consult.com>
wrote:
Hi Bob,

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.
>

Is this referring to HIP-DNS-EXT? If not, could you perhaps explain a bit
more?

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.
>

Thank you for bringing these 2 drafts to the WG's attention, is there a
preferred platform for folks to share their thoughts?
I see there's a github repo for the draft-ietf-drip-registries I-D but none
listed for draft-moskowitz-drip-secure-nrid-c2.

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.  :)
>

It would be great to have discussion on this : )

DANCErs feel free to speak up!

--
Joey Salazar
DANCE co-chair