Hi,

I quickly looked at -06. Looks ready for WGLC. Two high level comments.

- I think QUIC should be mentioned already in section 1.1 and mentioned 
everytime DTLS is mentioned Otherwise the document feels old already when it is 
published. QUIC already makes up a huge part of internet traffic (over 25% of 
traffic in some ISP), and is probably already more used than DTLS. I don't see 
any difference between DTLS and QUIC for the purpose of this document. Both are 
based on the TLS handshake.

- The document use both "Service Name" (title) and "Service Identity" 
(abbreviation). Maybe one of them is enough.

Cheers,
John

From: Uta <[email protected]> on behalf of Salz, Rich 
<[email protected]>
Date: Thursday, 26 May 2022 at 16:16
To: [email protected] <[email protected]>
Subject: Re: [Uta] I-D Action: draft-ietf-uta-rfc6125bis-06.txt
Colleagues,

With this draft we (the authors) think the document is done. We received a lot 
of excellent feedback and comments, and incorporated pretty much all of it. We 
believe this document is ready for WGLC, and ask the chairs to do that.

Depending on what happens during the WGLC, we'll want one minute, or more, to 
present at IETF 114.

On 5/26/22, 10:11 AM, "[email protected]" <[email protected]> 
wrote:


    A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
    This draft is a work item of the Using TLS in Applications WG of the IETF.

            Title           : Service Names in TLS
            Authors         : Peter Saint-Andre
                              Jeff Hodges
                              Rich Salz
         Filename        : draft-ietf-uta-rfc6125bis-06.txt
         Pages           : 26
         Date            : 2022-05-26

    Abstract:
       Many application technologies enable secure communication between two
       entities by means of Transport Layer Security (TLS) with Internet
       Public Key Infrastructure Using X.509 (PKIX) certificates.  This
       document specifies procedures for representing and verifying the
       identity of application services in such interactions.

       This document obsoletes RFC 6125.


    The IETF datatracker status page for this draft is:
    ://datatracker.ietf.org/doc/draft-ietf-uta-rfc6125bis/

    There is also an HTML version available at:
    https://www.ietf.org/archive/id/draft-ietf-uta-rfc6125bis-06.html

    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-uta-rfc6125bis-06


    Internet-Drafts are also available by rsync at 
rsync.ietf.org::internet-drafts

_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta
_______________________________________________
Uta mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/uta

Reply via email to