[gnutls-devel] GnuTLS | ext/record_size_limit: distinguish sending and receiving limits (!985)

[Development of GNU's TLS library]

Nikos Mavrogiannopoulos started a new discussion on lib/ext/max_record.c: https://gitlab.com/gnutls/gnutls/merge_requests/985#note_168476806

> - * doesn't have the limitation, as long as the value ranges between
> - * 512 and 16384.  Note that not all TLS implementations use or even
> - * understand those extension.
> + * called 'max fragment length', which limits the acceptable values to
> + * 512(=2^9), 1024(=2^10), 2048(=2^11) and 4096(=2^12).
>   *
> - * In TLS 1.3, the value is the length of plaintext content plus its
> - * padding, excluding content type octet.
> + * Since 3.6.4, the limit is also negotiated through a new TLS
> + * extension called 'record size limit', which doesn't have the
> + * limitation, as long as the value ranges between 512 and 16384.
> + * Note that while the 'record size limit' extension is preferred, not
> + * all TLS implementations use or even understand the extension.
> + *
> + * Deprecated: if the client can assume that the 'record size limit'
> + * extension is supported by the server, it had better use

I think "had" is a typo here. should sounds more natural, if I understand the meaning correctly.

-- 
Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/merge_requests/985#note_168476806
You're receiving this email because of your account on gitlab.com.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20190509/f803df91/attachment-0001.html>