Connected: An Internet Encyclopedia
RFC 822 - 3.4.7. CASE INDEPENDENCE

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 822
Up: 3. LEXICAL ANALYSIS OF MESSAGES
Up: 3.4. CLARIFICATIONS
Prev: 3.4.6. BRACKETING CHARACTERS
Next: 3.4.8. FOLDING LONG HEADER FIELDS

### 3.4.7. CASE INDEPENDENCE

Except as noted, alphabetic strings may be represented in any combination of upper and lower case. The only syntactic units which requires preservation of case information are:

- text
- qtext
- dtext
- ctext
- quoted-pair
- local-part, except "Postmaster"

When matching any other syntactic unit, case is to be ignored. For example, the field-names "From", "FROM", "from", and even "FroM" are semantically equal and should all be treated identically.

When generating these units, any mix of upper and lower case alphabetic characters may be used. The case shown in this specification is suggested for message-creating processes.

Note: The reserved local-part address unit, "Postmaster", is an exception. When the value "Postmaster" is being interpreted, it must be accepted in any mixture of case, including "POSTMASTER", and "postmaster".

Next: 3.4.8. FOLDING LONG HEADER FIELDS

Connected: An Internet Encyclopedia
RFC 822 - 3.4.7. CASE INDEPENDENCE