Re: [TLS] PR#345: IANA Considerations

[Eric Rescorla <[e-mail]>]

On Thu, Nov 19, 2015 at 7:03 AM, Martin Rex <[e-mail]> wrote:

> Eric Rescorla wrote:
> >
> > There are presently four categories of cipher suites vis-a-vis TLS 1.3.
> >
> > 1. MUST or SHOULD cipher suites.
> > 2. Standards track cipher suites (or ones we are making ST, like
> >     the ECC ones).
> > 3. Non standards track cipher suites
> > 4. Cipher suites you can't use at all with TLS 1.3, like AES-CBC.
> >
> > I think we're all agreed that category #1 should be marked recommended
> > and that #3 and #4 should not be. This leaves us with category #2, which
> > includes stuff like:
> >
> > - FFDHE
> > - CCM
> >
> > My proposal is that we:
> >
> > - List all the Standards Track cipher suites that are compatible with TLS
> > 1.3 in Appendix A.
> > - Mark all the cipher suites that are listed in Appendix A as
> "Recommended"
>
>
> I'm slightly confused.
>
> rfc5288 is standards track and describes AES-GCM with static RSA keyex.
>

This isn't compatible with TLS 1.3 because TLS 1.3 removes static RSA.


rfc5289 is only informational (i.e. _not_ standards track) and describes
> AES-GCM with ECDHE keyex.


We are re-labelling the AES-GCM ECDHE suites as standards track either in
this document or in RFC4492bis.

-Ekr


>
>
>
> -Martin
>