[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Proposed resolution to Issue 325

Bernard Aboba wrote:
> One thing I noticed in Section 2.1.3 was the following sentence:
> 
> " For data types not  supported by current RADIUS server dictionaries,
> changes to the
>    dictionary code can be required in order to allow the new type to be
> supported by 
>    and configured on the RADIUS server. "
> 
> In Issue #325, it was pointed out that new data types can initially be sent
> by a RADIUS server by configuring them as Strings.  So code changes are
> required only to enable RADIUS server to receive and parse the new data
> types, not to send them.  Of course, changes to the dictionary are necessary
> to improve the convenience with which the new data types can be entered.  

  I think that's partially covered by saying "changes CAN be required".

  Do we need specific text saying how new types can be entered as strings?

  Alan DeKok.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>