too long Calling Station Ids

[Josip Rodin]

On Fri, Dec 03, 2010 at 09:41:07PM +0100, Alan DeKok wrote:
>   Using random fields in random "printable" formats is a bad idea.
> RADIUS has the concept of "attributes".  These attributes have names,
> specific meanings, and well-defined formats.  I have no idea why many
> vendors are unable to use them.
> 
> > Yes, I know RFC 2865 says "phone number". But if fails to say anything
> > about the situation where there is no originating phone number.  So
> > vendors use what they have.  And port/vlan/mac is the best they can do
> > unless they have some PPPoE intermediate agent information.
> 
>   So define VSAs.  Other vendors have.  It's not hard.

I agree with you that a random string is too vague, but in practice that's
actually not bad, compared to the situation that I've had lately, where one
set of PPPoE NASes was sending that information like this, another set of
PPPoE NASes didn't send *anything*, another set of PPTP NASes sent Tunnel-*
attributes, and yet another set of PPTP NASes decided to send nothing.
They're all fairly similar Ciscos, but some have funky LAC's at the other
end, some have a funky T train IOS, some have rabies...

Getting a string full of actual information and worrying how to store it
and parse it is a good kind of worry.

-- 
     2. That which causes joy or happiness.