> On Aug 9, 2018, at 10:41 AM, Hubert Kario <hka...@redhat.com> 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.
Those can be in conflict if repeated, because they (often)
carry parameters.
> I don't see a similar requirement for other lists of values:
> signature_algorithms, supported_groups, cipher_suites, etc.
>
> Did I miss something?
These are simple lists of values with no parameters, and mere
duplication, though pointless, creates no ambiguity.
--
Viktor.
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
