Re: query

Ok, I understood your point.

But as per RFC 2865,
what is the meaning of then "UTF-8 encoded 10646 [7] characters", *the [7]?*
*7 stands for what over here?*
**

And one more thing as per RFC 2865,
1) As per this new RFC only only we need to support US-ASCII not any other
character set, right?
2) Does free RADIUS only supporting US-ASCII ?
On Wed, Dec 15, 2010 at 8:43 PM, Alan DeKok <aland@deployingradius.com>wrote:

> karnik jain wrote:
> >  As per my understanding of RFC 2865,
> >
> >  It is clearly written in *section 5.0 of RFC 2865* that,
> > *“text      1-253 octets containing UTF-8 encoded 10646 [7] characters.
> > Text of length zero (0) MUST NOT be sent; omit the entire attribute
> > instead.” *
> >
> > So, It has to be converted into UTF-8
>
>  No.  7 bit US-ASCII is a subset of UTF-8.
>
> > If it would be compatible to each other than What is the need of
> > including above statement in RFC-2865 clearly,
> > correct me If my understanding is wrong?
>
>  The statement is required for international text.  i.e. non US-ASCII.
>
> > *Can you please tell me that,*
> > *From where I can find the information regarding US-ASCII & UTF-8
> > compatibleness as per your reply or any RFC number if it is known to you?
> *
>
>  Read the UTF-8 RFC.  This is all documented elsewhere, and is not part
> of FreeRADIUS.
>
>  Alan DeKok.
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>