On Thu, Aug 9, 2018 at 7:41 AM, Hubert Kario <[email protected]> wrote:
> I've noticed that while there is an explicit requirement for extension > types > to be unique for any given message: > > https://tools.ietf.org/html/draft-ietf-tls-tls13-28#page-43: > > There MUST NOT be more than one extension of the > same type in a given extension block. > > and for key_shares: > > https://tools.ietf.org/html/draft-ietf-tls-tls13-28#page-54 > > Clients MUST NOT offer multiple KeyShareEntry values > for the same group. > > I don't see a similar requirement for other lists of values: > signature_algorithms, supported_groups, cipher_suites, etc. > > Did I miss something? > Nope. I don't believe it's a current requirement. -Ekr -- > Regards, > Hubert Kario > Senior Quality Engineer, QE BaseOS Security team > Web: www.cz.redhat.com > Red Hat Czech s.r.o., Purkyňova 115, 612 00 Brno, Czech Republic > _______________________________________________ > TLS mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/tls > >
_______________________________________________ TLS mailing list [email protected] https://www.ietf.org/mailman/listinfo/tls
