The following errata report has been submitted for RFC5216, "The EAP-TLS Authentication Protocol".
-------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=5216&eid=2510 -------------------------------------- Type: Editorial Reported by: Min Pae <min....@viasat.com> Section: 3.1 Original Text ------------- The L bit (length included) is set to indicate the presence of the four-octet TLS Message Length field, and MUST be set for the first fragment of a fragmented TLS message or set of messages. Corrected Text -------------- The L bit (length included) is set to indicate the presence of the four-octet TLS Message Length field, and MUST be set for the first fragment of a fragmented TLS message. The L bit MAY be included in all fragments of a fragmented TLS message, but if included the TLS Length MUST represent the entire length of the TLS message. Notes ----- The lack of definition for what to do with the L bit and the TLS length field for TLS fragments other than the first fragment is leaving the door open to divergent behavior for whether the L bit and length field are included, what the length contains if they're included, and how to interpret it. Instructions: ------------- This errata is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party (IESG) can log in to change the status and edit the report, if necessary. -------------------------------------- RFC5216 (draft-simon-emu-rfc2716bis-13) -------------------------------------- Title : The EAP-TLS Authentication Protocol Publication Date : March 2008 Author(s) : D. Simon, B. Aboba, R. Hurst Category : PROPOSED STANDARD Source : EAP Method Update Area : Security Stream : IETF Verifying Party : IESG _______________________________________________ Emu mailing list Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
