On Mon, Aug 22, 2016 at 03:48:03PM +0300, Ilari Liusvaara wrote:
> On Mon, Aug 22, 2016 at 02:29:10PM +0200, Peter Wu wrote:
> > Hi,
> >
> > The Implementations wiki page in the Github repository
> > (https://github.com/tlswg/tls13-spec/wiki/Implementations) states that
> > extension 0xff02 (65282) defines the TLS draft version in use.
>
> Also, nice surprise mentioning it only there and not in the draft spec
> itself (complete with appropriate RFC-Editor notes).
>
> > I cannot seem to find an official registration with IANA though which
> > might cause implementation issues in the future if this extension type
> > is re-purposed.
>
> There is no registration for it. However, only draft implmentations
> send it (final ones won't), which should limit the damage, as draft
> implementations are meant for testing only, and not for general-
> purpose use.
The same page notes:
"Implementations of the final version should check for this
extension and fail to negotiate TLS 1.3 if it is present. That check
might be removed once sufficient time has passed."
...which suggests that implementations of the final version could
actually care about it.
> > Question: can we rely on this extension being used only for specifying
> > the TLS draft version? We are working on adding TLS 1.3 support to the
> > Wireshark SSL/TLS dissector, if this extension type is not official we
> > should probably not add it.
>
> Well, I don't suppose it will be re-used quickly...
I don't have a crystal ball, but it would be nice if use of an extension
type is registered somewhere. Either directly with IANA or, as suggested
by Xiaoyin, by reserving a range.
--
Kind regards,
Peter Wu
https://lekensteyn.nl
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
