Re: [radext] [precis] saslprepbis and NAI
Peter Saint-Andre - &yet <peter@andyet.net> Tue, 25 November 2014 16:02 UTC
Return-Path: <peter@andyet.net>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A7421AC39D for <radext@ietfa.amsl.com>; Tue, 25 Nov 2014 08:02:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KMpEj32iCiwI for <radext@ietfa.amsl.com>; Tue, 25 Nov 2014 08:02:41 -0800 (PST)
Received: from mail-ie0-f173.google.com (mail-ie0-f173.google.com [209.85.223.173]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE8491AC3AD for <radext@ietf.org>; Tue, 25 Nov 2014 08:01:19 -0800 (PST)
Received: by mail-ie0-f173.google.com with SMTP id y20so798593ier.4 for <radext@ietf.org>; Tue, 25 Nov 2014 08:01:19 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=E1tv0a4O04mOqxzSmK6BFJ5TzwxSv9ScTc134uM+l98=; b=foqBvhEi/wPmXift+fdgoE4BPJfK5KrquOGmHxfQX+5UkM2lXCvq+W6Y9TngO3u2GV U9mDoYhO9m0rgURGp+cW+Lvb5aHL0An9NJbwthZG5J3K1Fd4I7EBBK6dcsA1+6kqeCd3 tFTVEanKJMX35sgtt0eKDzvVVhw3jK8v1gV+oWJQyYW/E0quorX0r5PQyJMKxKsBgvKS u4xMM4mnHvLP/DfQIMZMmfMdfqukhqkDRKLsfI/sy6mmAdfhbqXMr582V/gb9cTVMaFD tJLw8msweJ4A9B06pBcuFJIkeDHyFXseyOfEA01pRpEeBAAbs6bOBeUUVNKeRRppxJfV rJaw==
X-Gm-Message-State: ALoCoQl8EAKGEu8iNVipi+I9dtIj3HBy3mmRxRuJuBwmNUR9RwVe2F9lmZCatL8DjnEGC32BaLSD
X-Received: by 10.42.130.7 with SMTP id t7mr12774894ics.25.1416931279143; Tue, 25 Nov 2014 08:01:19 -0800 (PST)
Received: from aither.local (c-73-34-202-214.hsd1.co.comcast.net. [73.34.202.214]) by mx.google.com with ESMTPSA id g5sm745984iod.25.2014.11.25.08.01.18 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Nov 2014 08:01:18 -0800 (PST)
Message-ID: <5474A7CD.6070004@andyet.net>
Date: Tue, 25 Nov 2014 09:01:17 -0700
From: Peter Saint-Andre - &yet <peter@andyet.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alan DeKok <aland@deployingradius.com>
References: <54660EE5.50503@deployingradius.com> <5473EF2A.90808@andyet.net> <5474A631.7060506@deployingradius.com>
In-Reply-To: <5474A631.7060506@deployingradius.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/9Uln7i3yXrqvNXC00D9XttbWvp4
Cc: "radext@ietf.org" <radext@ietf.org>, precis@ietf.org
Subject: Re: [radext] [precis] saslprepbis and NAI
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 25 Nov 2014 16:02:43 -0000
On 11/25/14, 8:54 AM, Alan DeKok wrote: > Peter Saint-Andre - &yet wrote: >> On 11/14/14, 7:17 AM, Alan DeKok wrote: >>> The RADEXT WG is in the last stages of publishing the updated NAI >>> document: >>> >>> https://tools.ietf.org/html/draft-ietf-radext-nai-10 >>> >>> This defines a standard for "username@realm" handling, where "realm" >>> is a fully qualified hostname. It would be useful to reference that >>> from the saslprepbis document. >> >> What kind of reference do you have in mind? Perhaps a pointer from >> Section 3.4 ("Application-Layer Constructs")? > > Yes. Just another indication that there are applications using the > constructs. OK. I thought of some good text for this in the middle of the night but I neglected to write it down. :( I'll work to add something in the next version. >> I've just reviewed the NAI specification. Although it does directly not >> address issues such as width mapping, case mapping, and Unicode >> normalization (seemingly inheriting its handling of those issues from >> RFC 5335 for the username portion and from IDNA2008 for the realm >> portion), as far as I can see it is compatible with saslprepbis. > > Thanks. RFC 4282 did address many of those issues, and the conclusion > was it's recommendations were wrong. This document addresses the issues > by pointing to other documents. An eminently sensible approach, I think. Peter -- Peter Saint-Andre https://andyet.com/
- [radext] saslprepbis and NAI Alan DeKok
- Re: [radext] [precis] saslprepbis and NAI Peter Saint-Andre - &yet
- Re: [radext] [precis] saslprepbis and NAI Peter Saint-Andre - &yet
- Re: [radext] [precis] saslprepbis and NAI Sam Hartman
- Re: [radext] [precis] saslprepbis and NAI Alan DeKok
- Re: [radext] [precis] saslprepbis and NAI Alan DeKok
- Re: [radext] [precis] saslprepbis and NAI Peter Saint-Andre - &yet
- Re: [radext] saslprepbis and NAI Benoit Claise