3.1.1.2.5.1 Unicode String Comparison

NSPI servers MUST compare Unicode representations of strings according to [MS-UCODEREF]. All methods in which a server is required to perform such Unicode string comparison include LCID as part of the input parameters. The server SHOULD compare the strings using the closest supported LCID.<8> The NSPI Protocol does not constrain how a server chooses this closest supported LCID. However, because the protocol intends for clients to be able to persist sorted string values across multiple NSPI connections to an NSPI server, a server SHOULD NOT modify its algorithm for choosing the closest LCID once an algorithm has been implemented because doing so would lead to inconsistent behavior of NSPI methods across multiple NSPI sessions. The server MUST minimally support the LCID NSPI_DEFAULT_LOCALE flag (2.2.4). When making comparisons of Unicode string values, if the server uses LCID NSPI_DEFAULT_LOCALE, the server MUST also use the flag NSPI_DEFAULT_LOCALE_COMPARE_FLAGS for the comparison. Otherwise, the server MUST use the flag NSPI_NON_DEFAULT_LOCALE_COMPARE_FLAGS.