Subject: Re: [tcpinc] We need MTI symmetric algorithms too!

From: "Black, David" <[email-masked]>
Date: Fri, 3 Nov 2017 17:56:16 +0000

The absence of comments has been taken as absence of objection, hence what Daniel proposed is what has been done.

See the just-posted version of the tcpcrypt draft for details.

Thanks, --David

> -----Original Message-----
> From: Tcpinc [mailto:[email-masked]] On Behalf Of Daniel B Giffin
> Sent: Tuesday, October 24, 2017 2:08 PM
> To: tcpinc <[email-masked]>
> Subject: [tcpinc] We need MTI symmetric algorithms too!
> 
> Somehow we overlooked this: the tcpcrypt document does not
> currently mandate that implementations support any
> particular symmetric (AEAD) algorithms.
> 
> We need to make something mandatory-to-implement, of course,
> in order to ensure that compliant implementations can talk
> to each other.
> 
> We propose this disposition for the three algorithms
> currently specified for tcpcrypt:
> 
>      MUST: AES128-GCM
>    SHOULD: AES256-GCM
>    SHOULD: CHACHA20_POLY1305
> 
> This is the arrangement TLS 1.3 uses as well.
> 
> Please comment as soon as possible if you have any concerns
> with this approach.
> 
> Thanks,
> daniel
> 
> _______________________________________________
> Tcpinc mailing list
> [email-masked]
> https://www.ietf.org/mailman/listinfo/tcpinc