Re: [TLS] Cached Info extension - Draft 01

[Simon Josefsson <simon at josefsson.org>]

Stefan Santesson <stefan at aaa-sec.com> writes:

> It was not my intention to kill off this discussion with this new draft.
>
> I¹m wandering whether the silence is a sign of agreement, vacation or just a
> giving up that the author will ever listen to reasonable arguments...

I still prefer Martin's proposal to add framing, but could live with
your approach.

A mild problem that I don't think is fully covered yet is the complexity
in transition to new hashes -- clients will forever need to send SHA-1
hashes to the server, it seems, to ensure interoperability?  Or should
the document contain some text that explains that servers should pick
the "preferred" hash it supports, and that clients should cache that
choice for future use?  Additional text would then be needed to explain
that if clients try the new hash later on, and it doesn't work, it
should revert back to SHA-1 in case the server software was changed to
not support the other hash.  This aspects doesn't feel completely baked
yet to me.

> /Stefan
>
>
> On 09-06-16 7:13 PM, "Stefan Santesson" <stefan at aaa-sec.com> wrote:
>
>> I decided it was easier to explain my suggestions by incorporating it into a
>> new draft and submit it.
>> 
>> Draft 01 is currently in staging at:
>> http://www.ietf.org/proceedings/staging/draft-ietf-tls-cached-info-01.txt
>> 
>> This indicates by no means that I think we have reached an agreement on this
>> issue, but it at least we have a version that represents a better starting
>> point for change discussions.
>> 
>> I did however include Simon¹s suggested wording amendment in the beginning of
>> section 4.
>> 
>> /Stefan
>> 
>> _______________________________________________
>> TLS mailing list
>> TLS at ietf.org
>> https://www.ietf.org/mailman/listinfo/tls
>
> _______________________________________________
> TLS mailing list
> TLS at ietf.org
> https://www.ietf.org/mailman/listinfo/tls