Re: [Secdispatch] Requesting agenda time for draft-vaughn-tlstm-update

Hi folks,

I'm trying to follow the change in S 2.1 about the TLSTM fingerprint.

In TLS 1.2, one represented signature algorithms as:

      struct {
            HashAlgorithm hash;
            SignatureAlgorithm signature;
      } SignatureAndHashAlgorithm;

We found in TLS 1.3 that it was not really possible to mix-and-match
them and so changed this to a two-byte SignatureScheme that represented
the pair of hash and algorithm as well as any other values but without
any other internal structure. E.g.,

          rsa_pss_pss_sha256(0x0809),

As I understand it, 6353 used the TLS 1.2 HashAlgorithm identifier to
indicate which hash was used to make a fingerprint, and you're changing
this because TLS 1.3 deprecated this field? If so, I don't think this
is necessary: you're not referring to anything in TLS, you're just
reusing the code point. So, I would probably not make any change
here.

-Ekr

On Sun, Jun 27, 2021 at 7:31 PM Kenneth Vaughn <kvaughn@trevilon.com> wrote:

> I would like to present https://datatracker.ietf.org/doc/draft-vaughn-tlstm-update-01/, a new version of the proposed update of RFC 6353 (TLSTM). Based on feedback from this group, and the recent IETF decision to finalize DTLS, the ITS community decided to keep support for DTLS in the update. The result of that decision was to reverse a number of changes in the text and it made more sense to write the proposed new version 01 as an update to RFC 6353 rather than a replacement of RFC 6353. The result is a shorter document where the changes are more evident.
>
> I would like to request 10-15 minutes at IETF meeting of the Security Dispatch group to discuss the possibility of launching an effort to continue the development of this document as an official IETF document.
>
> Regards,
> Ken Vaughn
>
> Trevilon LLC
> 6606 FM 1488 RD #148-503
> Magnolia, TX 77354
> +1-936-647-1910
> +1-571-331-5670 cell
> kvaughn@trevilon.com
> www.trevilon.com
>
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>