[radext] #158: Section 1
"radext issue tracker" <trac+radext@trac.tools.ietf.org> Sun, 09 June 2013 00:03 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 0FDDB21F9402 for <radext@ietfa.amsl.com>; Sat, 8 Jun 2013 17:03:49 -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 augbprFm99aL for <radext@ietfa.amsl.com>; Sat, 8 Jun 2013 17:03:48 -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 4F32121F93D7 for <radext@ietf.org>; Sat, 8 Jun 2013 17:03:48 -0700 (PDT)
Received: from localhost ([127.0.0.1]:56343 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 1UlT6m-0002YL-Ge; Sun, 09 Jun 2013 02:03:44 +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:03:44 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://wiki.tools.ietf.org/wg/radext/trac/ticket/158
Message-ID: <066.a0a9674c2c43590339c9d13072676341@trac.tools.ietf.org>
X-Trac-Ticket-ID: 158
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: <20130609000348.4F32121F93D7@ietfa.amsl.com>
Resent-Date: Sat, 08 Jun 2013 17:03:48 -0700
Resent-From: trac+radext@trac.tools.ietf.org
Cc: radext@ietf.org
Subject: [radext] #158: Section 1
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:03:49 -0000
#158: Section 1
When the NAI was defined for network access, it had the side effect
of defining an identifier which could be used elsewhere. Some
systems which required the use of an identifier did so by leveraging
the NAI. This process simplified the management of credentials, by
re-using the same credential in multiple situations. We suggest that
this re-use is good practice. The alternative is to have protocol-
specific identifiers, which increases cost to both user and
administrator.
[BA] I do not agree that the definition of the NAI in RFC 2486
automatically defined the syntax of user identifiers used outside of
network access. Nor do I agree that the use of the NAI should be widely
encouraged in other protocols. If this were valid then those other
protocols would have referenced RFC 2486 for their user identity syntax,
and they did not do so. For example, SIP and HTTP do not reference the
NAI, and I do not believe it is the goal of this document to redefine SIP,
HTTP or any other protocol that uses RADIUS. In any case, that is outside
the scope of the RADEXT WG.
--
-------------------------------------+-------------------------------------
Reporter: | Owner: draft-ietf-radext-
bernard_aboba@hotmail.com | nai@tools.ietf.org
Type: defect | Status: new
Priority: blocker | Milestone: milestone1
Component: nai | Version: 1.0
Severity: In WG Last Call | Keywords:
-------------------------------------+-------------------------------------
Ticket URL: <http://wiki.tools.ietf.org/wg/radext/trac/ticket/158>
radext <http://tools.ietf.org/radext/>
- [radext] #158: Section 1 radext issue tracker
- Re: [radext] #158: Section 1 radext issue tracker