Re: [TLS] First TLS cached information draft posted
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TLS] First TLS cached information draft posted
Stefan Santesson <stefan at aaa-sec.com> writes:
> Thank's Simon,
>
> Good comments and I agree to both of them.
>
> 1) Yes the intension is that if the server returns only 1 out of 2 objects,
> only the object returned will be replaced
>
> 2) If the server has indicated support of a cached object in the server
> hello, the requirement to replace that object with a hash should be a MUST.
>
> It turns out that it was not to late to cancel the submission, so I have
> already incorporated this in the 00 draft and resubmitted.
>
> If you follow the same link and hit "refresh" you will see the changes.
Looks fine, thank you.
A minor discussion would be whether adding support for SHA-256/384/512
is worthwhile, but I don't feel strongly either way.
If someone is looking into implementing this specification, I'm
interested in performing interop testing.
/Simon
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.