Re: Ascend Radius with Livingston

Christopher Oliver (oliver@fritz.co.traverse.com)
Fri, 24 Nov 1995 14:24:27 -0500 (EST)

>From the mind of megaphone (oops!) megazone:
>Once upon a time Evan Baer shaped the electrons to say...
>>of 2 minutes or so on the Max. So, we have to use the Ascend version
>>to use the Ascend 'extensions' of idle time and filters, etc.
>
>So why not just add those to the dictionary file for our RADIUS?
>
>You should be able to merge the two dictionary files, there is no reason
>that RADIUS can't send the Ascend's variables.

Well, some things to bear in mind is that the Ascend attributes
have considerable substructure. They've not adhered to the data
types mentioned in the working draft. Thus, their (per)version
of the reference model is nearly twice the size. I.e. they've
added a fair deal of code to parse the structured attributes and
construct them for transmission. The most egregious example is
the specification of filters. This is the sort of cruft that
disregard for an open standards process leads to.

Bletch!

-- 
Christopher Oliver                     Traverse Communications
Systems Coordinator                    223 Grandview Pkwy, Suite 108
oliver@traverse.com                    Traverse City, Michigan, 49684
'tis an ill wind that blows no minds.