[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: IEEE 802.11f Request for RADIUS NAS-Port-Type and Service-Type value allocation (fwd)
FYI too.
The IANA made the registrations for the below request as they
were for RADIUS Attribute Values, which according to RFC2865
(section 6.2) are first-come, first-serve.
Just informing you as a related topic.
Michelle
-----Original Message-----
From: iesg-admin@ietf.org [mailto:iesg-admin@ietf.org]On Behalf Of Randy
Bush
Sent: Wednesday, January 15, 2003 10:59 PM
To: iesg
Subject: Fwd: IEEE 802.11f Request for RADIUS NAS-Port-Type and
Service-Type value allocation (fwd)
------- start of forwarded message -------
From: Bernard Aboba <aboba@internaut.com>
To: randy@psg.com
cc: mankin@psg.com
Subject: Fwd: IEEE 802.11f Request for RADIUS NAS-Port-Type and Service-Type
value allocation (fwd)
Date: Wed, 15 Jan 2003 19:26:31 -0800 (PST)
FYI.
An interesting case of an SDO "extension" of an IETF protocol. IEEE 802.1
has had a longstanding policy of co-publishing MIBs and AAA attributes as
Internet-Drafts, so as to allow IETF review and comment.
In this particular case, IEEE 802.11f is extending RADIUS for use in
Internet Access Point Protocol (IAPP). This includes new values for
existing attributes (below), new IEEE vendor-specific attributes and in
some cases, redefinition of existing RADIUS attributes.
So overall, this is more like an "extension" than just a "usage profile".
As I had cc'd you, I had made a request of the IEEE 802.11f chair to
allow IETF review of the "extension" but did not get a reply.
Some amount of IETF review seems essential, even if it's only posting as
an Internet Draft.
---------- Forwarded message ----------
Date: Wed, 15 Jan 2003 18:24:18 -0500
From: Robert Moskowitz <rgm@trusecure.com>
To: IANA <iana@iana.org>
Cc: Bernard Aboba <aboba@internaut.com>
Subject: Fwd: IEEE 802.11f Request for RADIUS NAS-Port-Type and
Service-Type value allocation
I really need this expedited. We need to publish the next (and perhaps
last) draft of 802.11f tomorrow by 5pm EST and we need these assignments.
Perhaps Stuart was given old information on where to direct the request
from the IANA pages...
At the end is additional explanation from Justin McCann.
>From: "Stuart Kerry" <stuart.kerry@philips.com>
>To: <cdr@telemancy.com>, <acr@merit.edu>, <wsimpson@greendragon.com>,
> <steve@livingston.com>
>Cc: "John Vollbrecht" <jrv@interlinknetworks.com>,
> "Bob O'Hara" <bob@bstormnetworks.com>,
> "Robert Moskowitz" <rgm@trusecure.com>, <jrosdahl@ieee.org>,
> "Dave Bagby" <david.bagby@ieee.org>,
> "'Justin McCann'" <jmccann@karlnet.com>
>Subject: IEEE 802.11f Request for RADIUS NAS-Port-Type and Service-Type
>value allocation
>Date: Mon, 13 Jan 2003 14:47:14 -0500
>
>
>Carl, and other RADIUS authors,
>
>The members of IEEE 802.11 Task Group F (Recommended Practice for the
>Inter-Access Point Protocol, aka IAPP) request that official values for
>the following RADIUS attributes be allocated with the descriptions as
>follows:
>
>Attribute Value Description
>------------- -----------------
>NAS-Port-Type IAPP
>Service-Type IAPP-Register
>Service-Type IAPP-AP-Check
>
>Our earlier attempts to have these attribute values allocated appear to
>have gone through the wrong channels. We are trying to get a final draft
>ratified, and are currently in session this week. We would like for
>these values to be officially allocated immediately, if possible. If an
>official allocation is not possible by Wednesday, in the interim we
>would like to be informed of the "values-to-be", i.e. what will be the
>official values when the official allocation is made.
>
>I request that you also send a copy of your reply to Justin McCann
>(jmccann@karlnet.com) and Bob O'Hara (bob.ohara@ieee.org) on behalf of
>the 802.11 Task Group.
>
>Thank you for your time,
> Stuart J. Kerry
> IEEE 802.11 Chair
From: "Justin McCann" <jmccann@karlnet.com>
To: "Robert Moskowitz" <rgm@trusecure.com>
Subject: FW: IEEE 802.11f Request for RADIUS NAS-Port-Type and Service-Type
value allocation
Date: Wed, 15 Jan 2003 17:33:25 -0500
We are adding new VALUES to already existing RADIUS ATTRIBUTES.
We need the new NAS-Port-Type value of "IAPP" to distinguish the 'users'
coming in for IAPP from regular dial-in/ISDN/Wireless users (which may
be a user name like 'jmccann' for dialin, or a STA's MAC Address
'02-03-04-05-06-07' for some currently shipping proprietary 802.11
authentication mechanisms).
We need the new Service-Type value of "IAPP-Register" to denote that the
service that is being offered to the 'user' in question is for
registering the AP/BSSID with the RADIUS Server (through the IAPP
extension) so that IAPP interaction with the RADIUS extension will work.
We need the new Service-Type value of "IAPP-AP-Check" to denote that the
service that is being offered to the 'user' in question is to check if
the RADIUS Client (New AP) can have a valid security association with
the 'user' (Old AP/BSSID).
Does this help?
Justin
Robert Moskowitz
Senior Technical Director
ICSA Labs
(248) 968-9809
Fax: (248) 968-2824
rgm@trusecure.com
There's no limit to what can be accomplished
if it doesn't matter who gets the credit
------- end of forwarded message -------