Ticket #507 (closed design: incorporated)
integer value parsing
|Reported by:||email@example.com||Owned by:|
|Component:||non-specific||Severity:||In IETF LC|
Description (last modified by firstname.lastname@example.org) (diff)
Any Content-Length field value greater than or equal to zero is valid. Since there is no predefined limit to the length of a payload, a recipient SHOULD anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows (Section 9.3).
In the byte range syntax, first-byte-pos, last-byte-pos, and suffix-length are expressed as decimal number of octets. Since there is no predefined limit to the length of a payload, recipients ought to anticipate potentially large decimal numerals and prevent parsing errors due to integer conversion overflows.
So we have similar text, once with "SHOULD", once with "ought to". We should make this consistent. Also, why isn't this a MUST?
(thanks to SM for spotting this)
- Severity changed from In WG Last Call to In IETF LC
- Status changed from new to closed
- Resolution set to wontfix
- Status changed from closed to reopened
- Resolution wontfix deleted