UTF-8, a transformation format of ISO 10646

Yergeau, F.

doi:10.17487/rfc2279

Cited by 288 publications

(275 citation statements)

References 0 publications

Supporting

Mentioning

273

Contrasting

Unclassified

Order By: Relevance

“…The "text" data type encodes UTF-8 text [RFC3629]. The maximum length of the text is given by the encapsulating attribute.…”

Section: -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+mentioning

confidence: 99%

Data Types in RADIUS

DeKok¹

2017

View full text Add to dashboard Cite

RADIUS specifications have used data types for two decades without defining them as managed entities. During this time, RADIUS implementations have named the data types and have used them in attribute definitions. This document updates the specifications to better follow established practice. We do this by naming the data types defined in RFC 6158, which have been used since at least the publication of RFC 2865. We provide an IANA registry for the data types and update the "RADIUS Attribute Types" registry to include a Data Type field for each attribute. Finally, we recommend that authors of RADIUS specifications use these types in preference to existing practice. This document updates RFCs 2865, 3162, 4072, 6158, 6572, and 7268.

show abstract

“…The "text" data type encodes UTF-8 text [RFC3629]. The maximum length of the text is given by the encapsulating attribute.…”

Section: -+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+mentioning

confidence: 99%

Data Types in RADIUS

DeKok¹

2017

View full text Add to dashboard Cite

show abstract

“…Conformant XML parsers recognize both UTF-8 (defined in [RFC3629]) and UTF-16 (defined in [RFC2781]); per [RFC2277], UTF-8 is the RECOMMENDED character encoding for use with SPPF.…”

Section: Versioning and Character Encodingmentioning

confidence: 99%

Session Peering Provisioning Framework (SPPF)

Cartwright¹,

Bhatia²,

Ali³

et al. 2016

View full text Add to dashboard Cite

show abstract

“…The string-to-key function as defined in [RFC3961] requires the salt to be valid UTF-8 strings [RFC3629]. Not every 128-bit random string will be valid UTF-8, so a UTF-8-compatible encoding would be needed to encapsulate the random bits.…”

Section: Random Values In Salt Stringsmentioning

confidence: 99%