today i am attending the FCP-4 meeting in the morning. we are spending time discussing what makes an I_T_L_Q nexus in fibre channel. the discussion revolves around some problems that are being experienced in the field during error recovery. so far there is some agreement around the fact that the Q portion of the nexus is a fully qualified combination of the OX_ID and RX_ID but there is belief that that is not enough. turns out if the target uses the S_ID and OX_ID combination then there should be sufficient information to fully identify the I/O process. however, during retries it is required to add the additional task retry identifier – if retires are enabled. Q is equal to OX_ID, RX_ID, and task retry identifier. otherwise a fully qualified OX_ID and RX_ID identifies the Q. how exciting is this.

Oh brother, I forgot what it was like to attend a T10 Standards committee meeting. This is my first meeting in probably 10 years (or more). The last time I was here SAS didn’t exists and was only a twinkle in George Penokie’s eye. Seeing how the meeting is in Las Vegas there is some hope of at least enjoying myself – or not. Right now they are arguing over a bit in the Report General command. It happens to take up a reserved bit which for some reason seems to be sacred to the group – hey isn’t that why we reserved those in the first place. How exciting is this – huh. The animation of the engineers is so enthralling that I think I need a coffee break (decaf only these days). Well I think I’ll write my post for SNW seeing how this is so exciting and important.