Re: "Last Look" at the RADIUS Design Guidelines document

[Avi Lior <avi@bridgewatersystems.com>]

On 16-01-2010, at 10:31 , Alan DeKok wrote:

> Avi Lior wrote:
>> On 14-01-2010, at 11:16 , Alan DeKok wrote:
>>> Your suggestion is *denying* the possibility that RADIUS servers can
>>> process complex attributes themselves.  Some people have servers that
>>> are capable of encoding and decoding complex types without resorting to
>>> adding application layers.
>> 
>> Or new code perhaps.  No?
> 
>  Or "having had your question answered and your point refuted, the only
> possible response is to change the subject".

But you didnt answer the question.  You continue to evade and thus you get asked the same question over and over again.

So again, such server can they handle complex attribute without requiring no code.  Yes or No?

In the document on page 9 (bottom) you are asserting the virtues of taking a complex attribute and using instead standard based attributes.

In the next paragraph you state "one of the fundamental goals of RADIUS protocol design...."  First what is the purpose of that paragraph - it really makes no recommendations what so ever.

Also based on the specific comment in this email dont you think that paragraph is missing some of the information you offer in this email.

Because according to you, a RADIUS server can be constructed that can encode and decode complex types without resorting to adding application layers and presumably even new code.  The paragraph is thus misleading and should be fixed or removed.
--
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/>