Subject: [eap] Issue 38: Language Negotiation

From: [email-masked] (Bernard Aboba)
Date: Sun, 6 Oct 2002 03:24:26 -0700 (PDT)

Issue 38: Language Negotiation
Submitter: Bernard Aboba
Submitter email address: [email-masked]
Date first submitted: October 5, 2002
Reference:
Document: RFC2284bis-06
Comment type: T
Priority: 1
Section: N/A
Rationale/Explanation of issue:

Currently there is no way to make sure that displayable messages
(such as Notifications) are sent in a language that the user understands.

Some ideas on how this might be accomplished:

a. Add language type to the first octets of the Notification Request AND
allow a Notification Response to encode an alternate language. However,
the Notification Response is of zero length, so there is a question of
whether this would break existing implementations.

b. Encode the proposed language type in the Identity Request, and allow
the Identity Response to encode an alternate language.