[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Chargeable-User-Identity

To: <radiusext@ops.ietf.org>
Subject: RE: Chargeable-User-Identity
From: "David B. Nelson" <dnelson@elbrysnetworks.com>
Date: Mon, 10 Aug 2009 13:50:17 -0400
In-reply-to:
Organization: Elbrys Networks, Inc.
References: <4A7FBEFA.2030702@restena.lu> <5A1555961F4C4B0495923ABDAEFAF05E@NEWTON603> <4A8022C7.3000205@restena.lu> <DB68F260B4FD46F3817A143A7CFACC98@xpsuperdvd2> <4A805734.1080905@umk.pl>

> I see no direct conflict with RADIUS services or attributes.

On the other hand, it does appear that your use cases place additional
requirements on the properties of CUI beyond what is defined in the RFC.
RADIUS Servers that are fully compliant to the RFC may not work well in the
eduroam scenarios you describe.  



--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

References:
- Chargeable-User-Identity
  - From: Stefan Winter <stefan.winter@restena.lu>
- RE: Chargeable-User-Identity
  - From: "Dave Nelson" <d.b.nelson@comcast.net>
- Re: Chargeable-User-Identity
  - From: Stefan Winter <stefan.winter@restena.lu>
- RE: Chargeable-User-Identity
  - From: "David B. Nelson" <dnelson@elbrysnetworks.com>
- Re: Chargeable-User-Identity
  - From: Tomasz Wolniewicz <twoln@umk.pl>

Prev by Date: RE: Chargeable-User-Identity
Next by Date: Re: Chargeable-User-Identity
Previous by thread: Re: Chargeable-User-Identity
Next by thread: RE: Chargeable-User-Identity
Index(es):
- Date
- Thread