Draft: draft-ietf-tls-tls13

Commentary: As discussed on list . 
 Minor suggestions : 1 ) Explicitly specify the expectation of a " record_overflow " alert after the two " MUST NOT"s . 2 ) Also drop the issue " OPEN ISSUE " note that 's on line 1087 - 1088 . 3 ) Amend the changelog to mention this . 4 ) Add a sentence noting the overhead cap has changed to the " Note : In versions of TLS prior to 1.3 " paragraph , or elsewhere . 
 As suggests , I 've updated the PR . I have not the Note . I do n't like those . The change log is enough . 
 Why was the changelog amended as for draft-09 ? The draft-08 has n't been published yet . Is it in the progress of being released ? ( not shown on DataTracker and releases have n't been tagged on GitHub since draft-05 ) 
 Pilot error . Please feel free to submit a PR . ,   wrote : 
 This is currently 2^{14 } + 2048 ( in TLSCiphertexT ) and then 2^{14 } + 1024 later . This is introduced by leaving room for compression . Should we just reduce this entirely across the board . Certainly we do n't need to leave room for compression . 
 Proposal at interim : 256 octets total .
Paragraph (version B):
The maximum permittion record expansion for AEAD has been reduced
from 2048 to 256 octets.
Paragraph (version A):
The length (in bytes) of the following TLSCiphertext.fragment.
The length MUST NOT exceed 2^14 + 2048.
Paragraph (version B):
The length (in bytes) of the following TLSCiphertext.fragment.
The length MUST NOT exceed 2^14 + 256.  An endpoint that receives
a record that exceeds this length MUST generate a fatal
"record_overflow" alert.
Paragraph (version A):
The AEAD output consists of the ciphertext output by the AEAD
encryption operation.  The length will generally be larger than
TLSPlaintext.length, but by an amount that varies with the AEAD
cipher.  Since the ciphers might incorporate padding, the amount of
overhead could vary with different TLSPlaintext.length values.  Each
AEAD cipher MUST NOT produce an expansion of greater than 1024 bytes.
Symbolically,
Paragraph (version B):
The AEAD output consists of the ciphertext output by the AEAD
encryption operation.  The length will generally be larger than
TLSPlaintext.length, but by an amount that varies with the AEAD
cipher.  Since the ciphers might incorporate padding, the amount of
overhead could vary with different TLSPlaintext.length values.
Symbolically,
Paragraph (version B):
An AEAD cipher MUST NOT produce an expansion of greater than 256
bytes.  An endpoint that receives a record that is larger than
2^14+256 octets MUST generate a fatal "record_overflow" alert.
Paragraph (version A):
A TLSCiphertext record was received that had a length more than
2^14+2048 bytes, or a record decrypted to a TLSPlaintext record
with more than 2^14 bytes.  This alert is always fatal and should
never be observed in communication between proper implementations
(except when messages were corrupted in the network).
Paragraph (version B):
A TLSCiphertext record was received that had a length more than
2^14+256 bytes, or a record decrypted to a TLSPlaintext record
with more than 2^14 bytes.  This alert is always fatal and should
never be observed in communication between proper implementations
(except when messages were corrupted in the network).