Re: [radext] #176 (nai): draft-ietf-radext-nai-05: is the term *Network Access* Identifier still appropriate?
"radext issue tracker" <trac+radext@trac.tools.ietf.org> Wed, 08 October 2014 08:39 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35FC01A0108 for <radext@ietfa.amsl.com>; Wed, 8 Oct 2014 01:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.386
X-Spam-Level:
X-Spam-Status: No, score=-0.386 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_NAIL=2.3, RP_MATCHES_RCVD=-0.786] autolearn=no
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 rbH1VRFKPnIU for <radext@ietfa.amsl.com>; Wed, 8 Oct 2014 01:39:52 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5AE7D1A0105 for <radext@ietf.org>; Wed, 8 Oct 2014 01:39:52 -0700 (PDT)
Received: from localhost ([::1]:46239 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+radext@trac.tools.ietf.org>) id 1Xbmmi-0005f6-K8; Wed, 08 Oct 2014 01:39:48 -0700
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, aland@deployingradius.com, stefan.winter@restena.lu
X-Trac-Project: radext
Date: Wed, 08 Oct 2014 08:39:48 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/radext/trac/ticket/176#comment:4
Message-ID: <080.1a955c63a090de473a357e378209ef11@trac.tools.ietf.org>
References: <065.18ebd81ae64d013f63a780221f34a543@trac.tools.ietf.org>
X-Trac-Ticket-ID: 176
In-Reply-To: <065.18ebd81ae64d013f63a780221f34a543@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-radext-nai@tools.ietf.org, aland@deployingradius.com, stefan.winter@restena.lu, radext@ietf.org
X-SA-Exim-Mail-From: trac+radext@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: aland@freeradius.org
Archived-At: http://mailarchive.ietf.org/arch/msg/radext/rCileR_SSHm032PD_aVhT1-HDyc
Cc: radext@ietf.org
Subject: Re: [radext] #176 (nai): draft-ietf-radext-nai-05: is the term *Network Access* Identifier still appropriate?
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 08 Oct 2014 08:39:53 -0000
#176: draft-ietf-radext-nai-05: is the term *Network Access* Identifier still appropriate? Comment (by stefan.winter@restena.lu): Another occurence is in the Abstract: "... the user identity submitted by the client prior to accessing network resources." It should probably just be "resources" to remove the specific scope of network access. This can also be done in IETF LC. -- -------------------------------------+------------------------------------- Reporter: | Owner: draft-ietf-radext- stefan.winter@restena.lu | nai@tools.ietf.org Type: defect | Status: new Priority: major | Milestone: Component: nai | Version: Severity: Waiting for Shepherd | Resolution: Writeup | Keywords: | -------------------------------------+------------------------------------- Ticket URL: <http://tools.ietf.org/wg/radext/trac/ticket/176#comment:4> radext <http://tools.ietf.org/radext/>
- [radext] #176 (nai): draft-ietf-radext-nai-05: is… radext issue tracker
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… radext issue tracker
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… Jouni Korhonen
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… Stefan Winter
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… Sam Hartman
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… radext issue tracker
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… radext issue tracker
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… Stefan Winter
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… radext issue tracker
- Re: [radext] #176 (nai): draft-ietf-radext-nai-05… radext issue tracker