i18n and RADIUS
Alan DeKok <aland@deployingradius.com> Wed, 03 August 2011 02:38 UTC
Return-Path: <owner-radiusext@ops.ietf.org>
X-Original-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com
Delivered-To: ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B738311E8077 for <ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com>; Tue, 2 Aug 2011 19:38:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.6
X-Spam-Level:
X-Spam-Status: No, score=-102.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WnXHGtb3q57p for <ietfarch-radext-archive-IeZ9sae2@ietfa.amsl.com>; Tue, 2 Aug 2011 19:38:34 -0700 (PDT)
Received: from psg.com (psg.com [IPv6:2001:418:1::62]) by ietfa.amsl.com (Postfix) with ESMTP id 03B7311E8081 for <radext-archive-IeZ9sae2@lists.ietf.org>; Tue, 2 Aug 2011 19:38:33 -0700 (PDT)
Received: from majordom by psg.com with local (Exim 4.76 (FreeBSD)) (envelope-from <owner-radiusext@ops.ietf.org>) id 1QoRJE-00043A-Tx for radiusext-data0@psg.com; Wed, 03 Aug 2011 02:35:48 +0000
Received: from [2a01:e0b:1:76:21c:c0ff:fe27:7b54] (helo=liberty.deployingradius.com) by psg.com with esmtp (Exim 4.76 (FreeBSD)) (envelope-from <aland@deployingradius.com>) id 1QoRJC-00042u-LX for radiusext@ops.ietf.org; Wed, 03 Aug 2011 02:35:46 +0000
Message-ID: <4E38B3FE.2030406@deployingradius.com>
Date: Tue, 02 Aug 2011 22:35:42 -0400
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: 'radext mailing list' <radiusext@ops.ietf.org>
Subject: i18n and RADIUS
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Sender: owner-radiusext@ops.ietf.org
Precedence: bulk
List-ID: <radiusext.ops.ietf.org>
As discussed at the last IETF, RFC 4282 has some problems. My draft (expired) describes the issues, and proposes a way to address them. The Precis working group is looking at i18n issues across a wide variety of protocols. The framework document applies to RADIUS and to EAP, though neither is explicitly mentioned: http://tools.ietf.org/id/draft-blanchet-precis-framework-02.txt I'd recommend reading Section 3, which defines stringprep "classes" for names and secrets. Section 10 deals with "confusable" strings, and says that applications need to find a way to deal with them. It looks like the work in Precis will allow RADIUS and EAP to continue with their current way of dealing with names and passwords. Since neither RADIUS nor EAP show strings to users, "confusable" strings can be avoided in the protocol transport. Alan DeKok. -- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>
- i18n and RADIUS Alan DeKok
- Re: i18n and RADIUS Bernard Aboba
- Re: i18n and RADIUS Alan DeKok
- RE: i18n and RADIUS Bernard Aboba
- Re: i18n and RADIUS Alan DeKok