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

[Robert Moskowitz <[e-mail]>]

On 6/24/22 12:28, Joey Salazar wrote:
> On Fri, Jun 24, 2022 at 4:27 PM Robert Moskowitz 
> <[e-mail]> 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?

oops that is suppose to be sec 3.2.1.3 ...

No.  Although HIP-DNS-EXT (rfc 8005) MAY be used for those UAS using HIP 
for Network Remote ID, DTLS is also usable for this comm, as the Net-RID 
Service Provider will have a fixed address.  So how, given drip-rid DETs 
(HHITs) can DTLS authentication best be supported. Well through DANCE 
and client TLSA RR.

HIP is covered, very easily in sec 3.2.1.2


3.2.1.3 is for those implementations using DTLS.

I should point out that for Command and Control (C2), DTLS is 
problematic IF the Ground Control Station (GCS) is mobile in the 
network.  For those GCS fixed (like in a major operations center), DTLS 
COULD be used for C2.  HIP with the RVS works very well for IP mobility 
on both ends.  Particularly managing the double jump problem (both nodes 
move at the same time).

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

No for secure-nrid-c2, as it is not yet adopted by the wg.  I keep all 
copies local.  Best to comment for both in the DRIP mailing list.  I 
will also follow comments here.


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

And I am listening.

Bob