NVMe hosts, controllers and NVM subsystems compare (e.g., for equality) NVMe Qualified Names used
by NVMe as binary strings without any text processing or text comparison logic that is specific to the
Unicode character set or locale (e.g., case folding or conversion to lower case, Unicode normalization). Any
such text processing:
a) may occur as part of entry of NVMe Qualified Names into NVMe hosts and NVM subsystems; and
b) should not occur as part of receiving NVMe Qualified Names via an NVMe connection, as shown
in Figure 137.
Upon entry (e.g., at point 1 in Figure 137, described as “input” in RFC4122), NVMe host software may
process an NVMe Qualified Name (e.g., for conversion to lower case based on the Unicode locale). Upon
entry (e.g., at point 3 in Figure 137, described as “input” in RFC4122), a controller may process an NVMe
Qualified Name (e.g., for conversion to lower case based on the Unicode locale). Upon receipt by the host
(e.g., at point 2 in Figure 137) of an NVMe Qualified Name from the controller, no text process (e.g., no
case folding) should occur. Upon receipt by the controller (e.g., at point 4 in Figure 137) of an NVMe
Qualified Name from the host, no text processing (e.g., no case folding) should occur.