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> Tue, 17 June 2014 21: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 EFAF21A0189 for <radext@ietfa.amsl.com>; Tue, 17 Jun 2014 14:39:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.251
X-Spam-Level:
X-Spam-Status: No, score=-0.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MANGLED_NAIL=2.3, RP_MATCHES_RCVD=-0.651] 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 HWB3eaoFK-UE for <radext@ietfa.amsl.com>; Tue, 17 Jun 2014 14:39:43 -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 33DDB1A017C for <radext@ietf.org>; Tue, 17 Jun 2014 14:39:43 -0700 (PDT)
Received: from localhost ([::1]:39124 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 1Wx16Q-0007Mn-Km; Tue, 17 Jun 2014 14:39:38 -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
X-Trac-Project: radext
Date: Tue, 17 Jun 2014 21:39:38 -0000
X-URL: http://tools.ietf.org/radext/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/radext/trac/ticket/176#comment:1
Message-ID: <080.187563b7a98218620fe0f8797b2665a0@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, 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/zjOb5fLahgAwi8TEbGL0Jh6ZtcY
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: Tue, 17 Jun 2014 21:39:44 -0000
#176: draft-ietf-radext-nai-05: is the term *Network Access* Identifier still appropriate? Comment (by aland@deployingradius.com): I think this requires larger discussion in the WG -- -------------------------------------+------------------------------------- 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://trac.tools.ietf.org/wg/radext/trac/ticket/176#comment:1> 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