Opened 8 years ago
Closed 8 years ago
#527 closed design (incorporated)
use of CHAR for other-range-set
Reported by: | julian.reschke@… | Owned by: | draft-ietf-httpbis-p5-range@… |
---|---|---|---|
Priority: | normal | Milestone: | 26 |
Component: | p5-range | Severity: | In IESG Evaluation |
Keywords: | Cc: |
Description
Amos found:
CHAR is being used in some ABNF rules for the P5 Range draft.
Section 1.2 has a generic refernce to RFC5234.
Appendix C has a more specific reference to RFC5324 explicitly listing the ABNF definitions imported, but omits CHAR.
Is that appendix relevant and needing an update before publication?
Answer: good catch. The actual bug is the use of CHAR instead of VCHAR though.
Change History (2)
comment:1 Changed 8 years ago by julian.reschke@…
comment:2 Changed 8 years ago by julian.reschke@…
- Resolution set to incorporated
- Status changed from new to closed
- Type changed from editorial to design
Note: See
TracTickets for help on using
tickets.
From [2507]:
restrict other-range-set to VCHAR (see #527)