maybe_merge staples together subsequent frames with the same content type (saves 5 bytes each!)
maybe_split splits messages into fragments of 2 ^ 14 size, as required by RFC!
Merge pull request #96 from mirleft/proper-sending-length

maybe_merge staples together subsequent frames with the same content typ...
feedback: decode the alert we fail with
Merge pull request #97 from mirleft/feedback-feedback

feedback: decode the alert we fail with
move record chunking to before encryption..
Merge pull request #98 from mirleft/proper-proper-sending-length

Fix record chunking ...
only merge HANDSHAKE frames - alerts and change cipher spec are rare enough that
it does not pay off. empty APPLICATION_DATA (at least in TLS_1_0) frames are crucial
(against BEAST).
configuration option whether to require secure rekeying (on by default)
check rekeying data only if we require secure rekeying in client
respect configuration in respect to secure rekeying - if not required, don't check
rework rekeying; semantics being:
- if use_rekeying is false, fail rekeying requests on both sides (server:renegotiate ; client:get_rekeying_data)
- if we received some data from the other side
  -> check whether we have rekeying data; require equality (or empty if None)
- if we received ciphersuite and have no rekeying data (client_hello only, thus in server), return
- if not required, return
- if required, fail
change API of max/min_protocol_version and supported_protocol_versions;
use tls_version list instead of config
simplify further: move supported_protocol_version to handshake_common and
max/min_protocol_version to core, and adjust clients of these
Merge pull request #99 from mirleft/fix-merge

only merge HANDSHAKE frames - alerts and change cipher spec are rare enough that
signal a WARNING level alert in-band when configuration requests to not renegotiate, but server asked us
protocol_versions is now a tuple (high, low), specifying the protocol version range

simplifies quite some code
Merge pull request #100 from mirleft/config-secure-rekeying

Config secure rekeying
some validation for starters (but we actually do not want everything in here)
style
re-add lost in translation fragment