Ticket #276 (closed editorial: incorporated)
untangle ABNFs for header fields
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
|Component:||non-specific||Severity:||Active WG Document|
Currently, we use ABNF to enumerate header fields. This doesn't reflect how parsing a message works: it generates a set of field names and values, and only after that, field values are parsed according to *that* headers specific ABNF.
Get rid of these ABNF productions, and replace them with simple Overview tables.
- Status changed from new to closed
- Resolution set to incorporated
- Status changed from closed to reopened
- Resolution incorporated deleted