IETF Logo Mail Archive

Re: [radext] WGLC #1 for draft-ietf-radext-nai-03

Alan DeKok <aland@deployingradius.com> Thu, 20 June 2013 00:54 UTC

Return-Path: <aland@deployingradius.com>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5851D21F9EC5 for <radext@ietfa.amsl.com>; Wed, 19 Jun 2013 17:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KiA4YPHgKB0a for <radext@ietfa.amsl.com>; Wed, 19 Jun 2013 17:54:23 -0700 (PDT)
Received: from power.freeradius.org (power.freeradius.org [88.190.25.44]) by ietfa.amsl.com (Postfix) with ESMTP id 6D38321F9EB7 for <radext@ietf.org>; Wed, 19 Jun 2013 17:54:23 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by power.freeradius.org (Postfix) with ESMTP id 624F2224007E for <radext@ietf.org>; Thu, 20 Jun 2013 02:53:24 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at power.freeradius.org
Received: from power.freeradius.org ([127.0.0.1]) by localhost (power.freeradius.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id snNERhmr1Kcv for <radext@ietf.org>; Thu, 20 Jun 2013 02:53:22 +0200 (CEST)
Received: from Thor-2.local (bas1-ottawa11-1176120556.dsl.bell.ca [70.26.44.236]) by power.freeradius.org (Postfix) with ESMTPSA id 0F933224007A for <radext@ietf.org>; Thu, 20 Jun 2013 02:53:21 +0200 (CEST)
Message-ID: <51C25283.8030007@deployingradius.com>
Date: Wed, 19 Jun 2013 20:53:23 -0400
From: Alan DeKok <aland@deployingradius.com>
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: "radext@ietf.org" <radext@ietf.org>
References: <7104B68E-C97B-4847-B0BF-8590ED1810D7@gmail.com>, <A1E4691F-0EB3-41ED-8771-67CF4AED4FCA@gmail.com>, <51C1BA01.7060106@deployingradius.com> <BLU169-W63408B8B132AA00E972F75938D0@phx.gbl> <51C1CFC5.5090209@deployingradius.com>
In-Reply-To: <51C1CFC5.5090209@deployingradius.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Subject: Re: [radext] WGLC #1 for draft-ietf-radext-nai-03
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Jun 2013 00:54:29 -0000

  Bernard and I had a long talk today about the NAI document.  There are
some clear points, but there is still one point which is unclear.

  It's not clear if the process of normalizing a realm name is
independent of Unicode version.  If it is, then proxies can happily
normalize what they get, and we don't care what endpoints produce.

  If it's dependent on Unicode version, then the only system capable of
normalizing the NAI is the endpoint which produces it.  And they don't
normalize NAIs now.

  We're trying to track down a definitive answer.

  Alan DeKok.

v2.23.0 | Report a Bug | By Email