Indefinite lengths
03Some strings and containers can end with a break code rather than carrying a known length.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 3.2 ↗
RFC 8949 · § 3.2EXAMPLE
3 / 3
03
Close with break
FF completes the array [1,2].
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
Indefinite-length forms exist for byte/text strings, arrays, and maps.
- Indefinite-length forms exist for byte/text strings, arrays, and maps.
- FF terminates the permitted indefinite-length item; it is not a general standalone value.
- Map content still requires complete key/value pairs.
Examples are illustrative. Consult the linked RFC and its errata for implementation details.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy