rfc-2987

Registration of Charset and Languages Media Features Tags

P. Hoffman
date2000-11 streamLegacy statusPROPOSED STANDARD pages6 canonicalhttps://www.rfc-editor.org/rfc/rfc2987 doi10.17487/RFC2987
This document contains the registration for two media feature tags: "charset" and "language". [STANDARDS-TRACK]

Extracted elements (11)

design-rationale §2

The 'language' tag is classified as a preference rather than a capability because most devices can attempt to process text in an unfamiliar language without catastrophic failure, unlike charsets where unknown encodings render content unprocessable.

interoperability-note §1

Charset aliases MUST NOT be used in media feature expressions because feature-expression manipulation tools may convert aliases to the principal name, causing mismatches. Values SHOULD be expressed in all lowercase letters.

interoperability-note §2

Language subtags are not used for comparison; language tags are always handled as a single opaque token as specified in RFC 1766.

interoperability-note §2

Language tag values SHOULD be expressed in all lowercase letters even though the tags are not case-sensitive, to increase the likelihood of interoperability across implementations.

interoperability-note §1

The 'charset' capability SHOULD always be indicated in conjunction with any capability to handle textual data, ensuring receivers can properly assess rendering ability.

protocol-element §1

The 'charset' media feature tag indicates a device's ability to display particular character sets. For most devices this is a capability (hard requirement), not a preference, because devices typically cannot intelligently process unknown charsets.

protocol-element §2

The 'language' media feature tag indicates a device's or user's ability to handle particular human languages. For most devices this is a preference rather than a hard requirement, and 'display' often means text-to-speech.

registry §1

Registers the 'charset' media feature tag (ASN.1 OID 1.3.6.1.8.1.31) with IANA. Values are case-insensitive tokens as defined in RFC 2978 (IANA Charset Registration Procedures), compared only for equality.

registry

registry §2

Registers the 'language' media feature tag (ASN.1 OID 1.3.6.1.8.1.32) with IANA. Values are language tags as defined in RFC 1766, treated as single tokens with no subtag comparison, and compared case-insensitively.

registry

security-consideration §1

Advertising 'charset' capability may slightly aid an attacker if a security bug exists in the display of that charset in the target environment, by confirming the device will render the attacker-chosen charset.

security

security-consideration §2

Advertising 'language' capability may slightly aid an attacker if a security bug exists in the display of that language in the target environment, by confirming the device will process the attacker-chosen language.

security