diff options
| author | Ingela Anderton Andin <[email protected]> | 2017-06-13 17:58:52 +0200 |
|---|---|---|
| committer | Ingela Anderton Andin <[email protected]> | 2017-06-13 17:58:52 +0200 |
| commit | 478205d32667dd7575d70d412d96c8c695168c46 (patch) | |
| tree | e5c97d54672d96c814ccaf8435d3abe574a9d819 /otp_versions.table | |
| parent | 698068c2322d6032f46487f56802246198e576f2 (diff) | |
| download | otp-478205d32667dd7575d70d412d96c8c695168c46.tar.gz otp-478205d32667dd7575d70d412d96c8c695168c46.tar.bz2 otp-478205d32667dd7575d70d412d96c8c695168c46.zip | |
dtls: Make HelloVerifyRequest version adhere to RFC
ERL-434
RFC6347 says about hello_verify_request version field as follow
https://tools.ietf.org/html/rfc6347#page-16
The server_version field has the same syntax as in TLS. However, in
order to avoid the requirement to do version negotiation in the
initial handshake, DTLS 1.2 server implementations SHOULD use DTLS
version 1.0 regardless of the version of TLS that is expected to be
negotiated.
But current DTLS server responses DTLS1.2 instead of DTLS1.0.
Diffstat (limited to 'otp_versions.table')
0 files changed, 0 insertions, 0 deletions