[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

Hannes Tschofenig wrote:
> 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
> Guidelines document.

  The guidelines are guidelines, not absolute rules.  If following the
guidelines results in something horrible (e.g. 100's of attributes),
then it may be better to create a complex type, which is permitted:

   ... the introduction of new complex data types within RADIUS
   attribute specifications SHOULD be avoided,

  It's not a MUST.

  Alan DeKok.

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