[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue: Treatment of null Identity Response
Hi,
Sorry to break in, but I need to support Jari in this:
On Thu, Dec 15, 2005 at 05:42:00PM +0200, Jari Arkko wrote:
> Nelson, David wrote:
>
> >Jari Arkko writes...
> >
> >
> >
> >>>The text in the CUI draft indicates that the NUL CUI includes a
> >>>
> >>>
> >single
> >
> >
> >>>'NUL' character.
> >>>
> >>>
> >>Right. This is correct, and we do not have a problem with the empty
> >>string rule.
> >>
> >>
> >
> >Since counted strings can have embedded NUL characters, that's true. It
> >obviously requires special handling in the C-style string to RADIUS
> >string conversion, though.
>
> Well, if its a "string" in RADIUS terminology then its
> really an octet string in more general terminology, and
> implementations already have to support embedded 00s.
Fully agreed.
And in C, people routinely work with length-defined strings as well as
NUL-terminated strings, by the way.
> >I agree, although if the type is intended to be a UTF-8 printable
> >string, the correct RADIUS type would be "text", not "string. If there
> >is consensus on that, it could be fixed in AUTH48.
> >
> >
> Yes. To me the CUI function is more of a binary handle
> than a printable string. But I'm not sure if others agree.
Fully agreed again.
Cheers,
Emile.
--
E-Advies - Emile van Bergen emile@e-advies.nl
tel. +31 (0)78 6136282 http://www.e-advies.nl
--
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/>