FUJITA Tomonori wrote: > Or Gerlitz <ogerlitz@xxxxxxxxxxxx> wrote: >> Vendor specific ID type is problematic since it should include T10 vendor ID >> (see 7.6.3.3) where stgt is not related to any specific vendor. The same reasoning >> holds for NAA, EUI64 and T10 ID types. SCSI Name String (SNS - 7.6.3.11) is the only >> ID type which doesn't require explicit authority-assigned vendor ID. Sorry, but I was a bit unclear here, confused vendor specific IDs - 7.6.3.3 with T10 IDs - 7.6.3.4 > stgt uses 'IET' T10 vendor ID? > http://www.t10.org/lists/vid-alph.htm#VID_I The registered T10 vendor id is not used along the lines of 7.6.3.4 - that is the vendor ID type set by stgt is "vendor specific" (0x0) and not T10 (0x1) {see table 298 — identifier type field} and the vendor specific identifier used is the "...deadbeaf..." and not the T10 registered one. All in all, it seems something has to change (both regarding the association and the vendor identification). Indeed, fixing things to comply with T10 is possible, however we believe the SNS approach allows the user to set its own target name, configurable through the standard stgt management mechanisms, which may improve/ease target identification and network manageability. Or. -- To unsubscribe from this list: send the line "unsubscribe stgt" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
