During the T10 Plenary meeting last week, we discussed withdrawing the Bridge Controller Commands (BCC) project (originally called Management Server Commands (MSC)).
This is the official description:
"BCC describes the command set for SCSI protocol bridge controller devices that bridge between various SCSI protocols like SPI, FCP, SRP, and iSCSI. "
The standard:
a) defines a W-LUN addressing scheme for addressing otherwise hidden bridges/gateways/routers in the path between an initiator port and a target port.
b) asks SPC-4 to define a peripheral device type of 10h for bridges
b) defines REPORT BRIDGE MAPPING and WAIT FOR BRIDGE MAPPING CHANGE commands to determine:
A) the capabilities of the bridge (e.g., does it intercept and emulate extended copy, access controls, persistent reservations, and other complex SCSI commands, or does it pass them through preserving unique initiator identities on the other side of
the bridge)
B) what address translation the bridge is performing in both directions (far-end target to near-end target, near-end initiator to far-end initiator) (e.g., in an iSCSI to FCP bridge, it would report the IP address <-> FC Port_Name mappings)
There seems to be no interest by protocol bridges or software in using the command set. Sideband mechanisms are apparently sufficient.
Unless someone objects (and starts making proposals, or shows that BCC has actually been implemented), the July T10 Plenary meeting will vote to withdraw the project.
---
Rob Elliott, HP Industry Standard Server Storage