[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Suggestions regarding RADIUS encoding for draft-ietf-dime-qos-attributes-07.txt
The problem is the following. Whatever we do we with the encoding someone
will come along and say that it does not comply with the RADIUS Design
I can already envision some folks who will later complain.
[mailto:firstname.lastname@example.org] On Behalf Of Glen Zorn
Sent: 28 October, 2008 16:26
To: 'Bernard Aboba'
Subject: RE: Suggestions regarding RADIUS encoding for
Alan DeKok said:
"The sheer number of attributes, and use of Diameter functionality
(e.g. grouping && data types) makes it difficult.
I'm not sure there are any good methods for doing this."
I would agree with Alan that there is no obvious RADIUS encoding of
compatible with the RADIUS Design Guidelines.
and this matters because?
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.