[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "Last Look" at the RADIUS Design Guidelines document
Avi Lior wrote:
> But you didnt answer the question.
The question I answered was "why doesn't the section on complex types
have any text about application layers". My response was direct and to
the point. *That* point.
So... you switched the topic to "but complex attributes require code
changes!" And "But Alan is *denying* they require code changes!"
It's damning evidence as to how weak your position is.
> 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.
It explains the rationale behind the recommendations. And it's
clearly useless, just like most of my responses here.
> 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.
That statement is simply not true under any objective definition of
As before, I refer you to my earlier messages that discuss this exact
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.