PPP LCP Internationalization Configuration Option
updates
Extracted elements (12)
This option was defined to satisfy RFC 2277's requirement that IETF protocols support negotiation of character set and language for human-readable text, enabling internationalized PPP authentication and LCP messages.
If the Internationalization option is rejected by the peer, the default language and charset MUST be used to construct all human-readable messages sent to the peer.
Implementations SHOULD send only lower-case Language-Tag fields, since language tags are case-insensitive and capitalization carries no meaning.
Only one instance of this option SHOULD be sent by an implementation, representing its preferred language and charset.
The Internationalization option MAY be negotiated independently in each direction.
The MIBenum value MUST represent one of the charsets listed in the IANA charset registry.
The Internationalization Configuration Option (Type 28) allows PPP peers to negotiate the character set and language for human-readable messages. It carries a 4-octet MIBenum identifying the charset and a variable-length Language-Tag ASCII string.
The Language-Tag field is a variable-length ASCII string containing an RFC 1766 language tag. The default tag value is 'i-default'.
The MIBenum field is four octets identifying a charset from the IANA charset registry. The default charset is UTF-8, with MIBenum value 106.
The document assigns LCP Option Type 28 for the Internationalization option. Up-to-date LCP Option Type values are maintained in STD 2 (Assigned Numbers).
An attacker might manipulate the Internationalization option such that displayable messages would be unintelligible to the reader, potentially as a social engineering or denial-of-comprehension attack.
The Internationalization option wire format: Type (1 octet, value 28), Length (1 octet, minimum 7), MIBenum (4 octets, unique integer identifying charset from IANA registry), Language-Tag (variable-length ASCII string, RFC 1766 language tag).