<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Le 27.11.2008 21:41, Alan DeKok a écrit :
<blockquote cite="mid:492FA0BF.6090301@deployingradius.com" type="cite">
<pre wrap="">Alexandre Chapellon wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I have noticed that the "Class" attribute as defined in rfc2865 is a
string value, but looking at dictionary that comes with freeradius i saw
that it's an octet value.
</pre>
</blockquote>
<pre wrap=""><!---->
FreeRADIUS was the first to mark some attributes as "binary" versus
"ascii". The original RFC's didn't make that distinction. When they
were updated, they chose different names for the types.
We chose "string" and "octets" to mean "ascii" and "binary". They
chose "text" and "string".
</pre>
<blockquote type="cite">
<pre wrap="">As far as I know none of the rfc updating 2865 redefine the class attribute.
Is there a reason for this, is it safe to make it a string value?
</pre>
</blockquote>
<pre wrap=""><!---->
I very much suggest leaving it alone. Editing things just to make the
"closer" to the RFC's is not a good idea. The RFC's are well known to
be wrong in many cases.
</pre>
</blockquote>
<br>
Well the aim of switching type is not to be closer to rfc, i'm not
fanatic enough :)!<br>
My problem is I need to send a string to the NASes in the Access-Accept
and want them to sent it back to me as is in Accounting packets.<br>
Is there other attributes of type string that allow such a behaviour
from the NASes?<br>
<br>
<blockquote cite="mid:492FA0BF.6090301@deployingradius.com" type="cite">
<pre wrap="">
e.g. After a number of similar discussions, RFC 5080 was issued. It
fixes a bunch of problems in earlier RFC's, and at one point, says that
the FreeRADIUS way of doing things is the best way. Since I'm a
co-author, that statement was easy to make.
I'm currently authoring or co-authoring 4-5 other RADIUS RFC's. One
of will update RFC 4282, which is substantially wrong.
Alan DeKok.
-
List info/subscribe/unsubscribe? See <a class="moz-txt-link-freetext" href="http://www.freeradius.org/list/users.html">http://www.freeradius.org/list/users.html</a>
</pre>
</blockquote>
</body>
</html>