[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [AAA-WG]: Reconciling Radius/Diameter SIP application
Hi Miquel, Jarri,
> > 3- Radius does not define UTF8String data types, so all these
> > attributes
> > will remain as String, but the Radius draft will indicate
> that contain a
> > UTF8String verbally (this is required by HTTP and SIP).
Just one point now. RADIUS "Text" type attributes are UTF-8 compliant. I
just want to make sure that the definition of Text and UTF8String are the
same. And they appear to be.
From RFC 2865:
text 1-253 octets containing UTF-8 encoded 10646 
characters. Text of length zero (0) MUST NOT be sent;
omit the entire attribute instead.
 Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC
2279, January 1998.
From RFC 3588:
This is a human readable string represented using the
ISO/IEC IS 10646-1 character set, encoded as an OctetString using
the UTF-8 [UFT8] transformation format described in RFC 2279.
So where applicable the attributes in Sterman should be set to Text.
to unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.