[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Issue 226: RFC 3576bis and Renumbering
> I think we'd be better off just making
Acct-Session-Id a MUST, and
> ignoring the other attributes.
Acct-Session-Id a MUST would ensure Diameter compatibility.
probably needs to be at least a MAY for the same reason.
There are just a few problems with this idea (in the absence
of RADIUS accounting). The first & most obvious is that "sessions" do
not exist in RADIUS. This is because the RADIUS server has no idea when
(or if) the session ends or, more subtly, if it actually begins. All the
RADIUS server knows is that it
authorized a session in an Access-Accept; by the time that message arrived at
the NAS, the user might already have left. So, basically, what you are
saying seems to be that
deploying RADIUS accounting is mandatory
an undefined but incestuous relationship between separate RADIUS
and RADIUS Accounting servers is also mandatory OR
the RADIUS and RADIUS Accounting servers must be one and the