Some thoughts

[Bernard Aboba <aboba@internaut.com>]

As has been noted previously, the discusson of potential IETF RADIUS work
is focussed on the *minimum* work needed to enable deployed applications
such as IP Telephony or (W)LAN access.

That implies that if you'd like to suggest a work item, that the tie
between this and the above applications needs to be clearly made.

For example, the work on RADIUS transport profiles was suggested in order
to improve the usability of RADIUS accounting in usage-based billing
scenarios, primarily for IP telephony, but also potentially for (W)LAN
access.

It was also suggested that these services would benefit from prepaid
accounting support.

Since today various SDOs are already standardizing (W)LAN related
attributes it was suggested that better interoperability would be obtained
by having an IETF RFC on the subject.

So far, I'm not clear about the link between "attribute extension" and the
above goals.  Currently there are more than enough RADIUS attributes left
to handle the needs that have been described so far -- which would suggest
that attribute extension is not essential, and therefore is a candidate
for being removed from the charter.

Comments?

--
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/>