[Dance] Re: Start of Working Group Last Call on draft-ietf-dance-architecture-06

[Tim Wicinski <[e-mail]>]

Okay, so I have some comments that hopefully folks can help set me straight
on.

previously pointed out some nits on refs that Ollie was chasing down


# The document mentions "how to dance" documents but I don't see any
examples.  do we have any examples?

# Section 4 I feel needs some work or maybe I'm reading it all wrong.

In 4.1 Overview, there is a use of terms:

subjectAltName
dNSName
rfc822Name


but with no reference to 5280

Also " 4. Client Authentication",  If we look at these section headers:

4.1. Overview
4.1.1. Example 1: TLS authentication for HTTPS API interaction, DANE
pattern assurance
4.1.1.1. Example 2: TLS authentication for HTTPS API interaction, DANE
matching in web application
4.1.1.2. Example 3: TLS user authentication for an LDAP query


Perhaps "Overview" should be "TLS Authentication"

and there should be a small paragraph along the lines of:

"There are a variety of authentication methods available for client/server
communication. "

thoughts?

Then I look at these other headings

4.1.2. IoT: Device to cloud
4.1.3. LoRaWAN
4.1.4. Edge Computing
4.1.5. Domain Users
4.1.6. SIP and WebRTC inter-domain privacy
4.1.7. DNS over TLS client authentication
4.1.8. SSH client
4.1.9. Network Access

these all feel like authentication methods - but some are better than
others correct?

a final note

In "4.1.7 " the text says "Current BCP for authentication between DNS
infrastructure"

But no Link?

I had to stop at this point.

But I welcome comments etc.

tim


On Mon, Jun 10, 2024 at 10:59 AM Olle E. Johansson <[e-mail]> wrote:

>
>
> On 8 Jun 2024, at 22:27, Tim Wicinski <[e-mail]> wrote:
>
> Olle,
>
> Have you checked your nits?
>
> Thanks, was not aware of these. I’ll check.
>
> /O
>
>
>   == Missing Reference: 'XXXrefereceXXX' is mentioned on line 785, but not
>      defined
>
>   == Unused Reference: 'I-D.johansson-sipcore-dane-sip' is defined on line
>      875, but no explicit reference was found in the text
>
>   == Unused Reference: 'RFC9140' is defined on line 932, but no explicit
>      reference was found in the text
>
> tim
>
>
> On Wed, May 29, 2024 at 2:48 AM Olle E. Johansson <[e-mail]> wrote:
>
>> We need to resolve issue #28 before publishing. The text in the
>> terminology section is not publication-ready ;-)
>>
>>
>> [image: 28.png]
>>
>> Terminology · Issue #28 · ietf-wg-dance/draft-dance-architecture
>> <https://github.com/ietf-wg-dance/draft-dance-architecture/issues/28>
>> github.com
>> <https://github.com/ietf-wg-dance/draft-dance-architecture/issues/28>
>> <https://github.com/ietf-wg-dance/draft-dance-architecture/issues/28>
>>
>> Thank you all for good work in getting the document to this state!
>>
>> /O
>>
>>
>> On 29 May 2024, at 02:01, Wes Hardaker <[e-mail]> wrote:
>>
>>
>> Folks,
>>
>> The DANCE architecture document is ready for working group last call, and
>> we thank all the various different contributors over the years for helping
>> it finally get to this state.  Please review and comment on this document
>> about its readiness for publication by June 25th, anywhere on earth.
>>
>> https://datatracker.ietf.org/doc/draft-ietf-dance-architecture/06/
>>
>> Thank you and continue dancing!
>> --
>> Wes Hardaker
>> USC/ISI
>>
>> --
>> Dance mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>>
>> --
>> Dance mailing list -- [e-mail]
>> To unsubscribe send an email to [e-mail]
>>
>
>