[radext] #165: Section 2.8
"radext issue tracker" <trac+radext@trac.tools.ietf.org> Sun, 09 June 2013 00:33 UTC
Return-Path: <trac+radext@trac.tools.ietf.org>
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 3A2A021F93D7 for <radext@ietfa.amsl.com>; Sat, 8 Jun 2013 17:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.299
X-Spam-Level:
X-Spam-Status: No, score=-100.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MANGLED_NAIL=2.3, 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 ijmQLgJ0QbcQ for <radext@ietfa.amsl.com>; Sat, 8 Jun 2013 17:33:24 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 89F9B21F9446 for <radext@ietf.org>; Sat, 8 Jun 2013 17:33:23 -0700 (PDT)
Received: from localhost ([127.0.0.1]:57895 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1UlTZR-0000Xl-Qb; Sun, 09 Jun 2013 02:33:21 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: radext issue tracker <trac+radext@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-radext-nai@tools.ietf.org, bernard_aboba@hotmail.com
X-Trac-Project: radext
Date: Sun, 09 Jun 2013 00:33:21 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://wiki.tools.ietf.org/wg/radext/trac/ticket/165
Message-ID: <066.ffbb7f34cc97f58e1643d7c72a2b9c5c@trac.tools.ietf.org>
X-Trac-Ticket-ID: 165
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-radext-nai@tools.ietf.org, bernard_aboba@hotmail.com, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: aland@freeradius.org
Resent-Message-Id: <20130609003323.89F9B21F9446@ietfa.amsl.com>
Resent-Date: Sat, 08 Jun 2013 17:33:23 -0700
Resent-From: trac+radext@trac.tools.ietf.org
Cc: radext@ietf.org
Subject: [radext] #165: Section 2.8
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.12
Reply-To: radext@ietf.org
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: Sun, 09 Jun 2013 00:33:25 -0000
#165: Section 2.8
We also note that many existing systems use user identifiers which
are similar in format to the NAI, but which are not compliant with
this specification. For example, they may use non-NFC form, or they
may have multiple "@" characters in the user identifier.
Intermediate nodes MAY normalize non-NFC identifiers to NFC, prior to
looking up the "utf8-realm" in the logical routing table.
Intermediate nodes MUST NOT modify the identifiers that they forward.
The data as entered by the user is inviolate.
[BA] In fact, use of NFC in existing implementations is very rare, so rare
that this specification simply cannot credibly require it. Therefore the
MAY for normalization here needs to be at least a SHOULD (or probably a
MUST) before comparisons are done.
--
-------------------------------------+-------------------------------------
Reporter: | Owner: draft-ietf-radext-
bernard_aboba@hotmail.com | nai@tools.ietf.org
Type: defect | Status: new
Priority: major | Milestone: milestone1
Component: nai | Version: 1.0
Severity: In WG Last Call | Keywords:
-------------------------------------+-------------------------------------
Ticket URL: <http://wiki.tools.ietf.org/wg/radext/trac/ticket/165>
radext <http://tools.ietf.org/radext/>
- [radext] #165: Section 2.8 radext issue tracker
- Re: [radext] #165: Section 2.8 radext issue tracker