Re: [Danish] Charter Text and the Problem Statement

[Hannes Tschofenig <[e-mail]>]

Hi Wes

Talking about a specific use case makes a lot of sense.
I guess you are referring to the taxi dash cam retention scenario from https://datatracker.ietf.org/meeting/110/materials/slides-110-danish-danish-bof-slides-02

The example raises a few questions:
* how does the network access authentication and authorization work? This is key because it secures the subsequent mDNS exchange as well.
* how does the taxi car know that it has to talk to recorder56 in that garage?
* how does the recorder recognize that car54 is allowed to upload video data (and to potentially access data)?

I can easily see concerns about listing IoT devices in the DNS (publically visible).

How the device would obtain operational credentials since you rarely use the same (manufacturer-provisioned) key for all services?

Ciao
Hannes

PS: I missed the example of onboarding a device in a hospital.

-----Original Message-----
From: Danish <[e-mail]> On Behalf Of Wes Hardaker
Sent: Sunday, June 20, 2021 4:51 PM
To: Hannes Tschofenig <[e-mail]>
Cc: Michael Richardson <[e-mail]>; [e-mail]
Subject: Re: [Danish] Charter Text and the Problem Statement

Hannes Tschofenig <[e-mail]> writes:

> If the problem cannot be described properly then there will be a lot
> of problems later in this group.

I think starting with a problem statement and architecture document makes a lot of sense to me.

In particular, during the last BOF there was an overview example that included a car driving into a home that reasonably explained the space.
And recently on the list there was a description of onboarding a device in a hospital, that also sounded like a reasonable place to start.
IMHO, it would be really nice to get these two, and possible other examples, fully flushed out with example DNS queries and documented some place that we could refer to them.

But...  the charter also needs a suitable shortened problem description, and that might be trickier since it seems like a longer description is almost necessary for most people to grasp the space.

--
Wes Hardaker
USC/ISI

--
Danish mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/danish
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.