Skip to content

US-ASCII #696

@martinthomson

Description

@martinthomson

In Section 5.5:

Newly defined fields SHOULD limit their values to US-ASCII octets.

This is probably overly broad considering that the ABNF says VCHAR / SP / HTAB (I question the wisdom of including HTAB, but now is not the time to worry about that). Could this be changed to "printable or visible US-ASCII octets, plus SP and HTAB"?

(Incidentally, why doesn't the field-content rule use the ABNF WSP rule?)

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions