[SRP] Proposed Agenda - Feb 1

Simpson, Cris cris.simpson at intel.com
Thu Jan 31 22:50:58 PST 2002


* From the T10 Reflector (t10 at t10.org), posted by:
* "Simpson, Cris" <cris.simpson at intel.com>
*
  
Feb 1 0900-1100 PST
  1-888-316-5901,  1-617-801-9781   Passcode: 8774.4560  

Old Business_____________________________________________________

1. Expressing SRP IB ServiceID extensions in IPv6-like :: format
     Response from Marjorie

2. Review 02-064r2, Ed's SE notification proposal 
     ftp://ftp.t10.org/t10/document.02/02-064r2.pdf

3. 02-004 status

4. February 8 meeting - conflicts w/T11
     Skip, meet on 15th? 

New Business______________________________________________________ 

Discussion of open technical comments

1. HP #1 - Persistent port identifiers
    State that SRP port identifiers have the properties of names (see SAM-2:
persistence, world-wide unique in context of SRP).

2. HP Page 25 Line 32
    The port identifier fields, at 16B, are too small to carry identifiers
as used by iSCSI. This may prove problematical as we attempt to merge iSCSI
and SRP for use with iWARP.

3. IBM #50
  (At disconnect) "Discard any subsequent messages received on that RDMA
channel."
   I recommend adding into this list a statement that other SCSI related
   parameters (e.g., mode pages, logs) not be effected by the disconnect. 
   This should avoid the hole the FC has dug for itself in this area.

4. IBM #57 

  "The following list describes all circumstances where an SRP response
shall not be returned for an SRP request:
    a) If an SRP request conveys a SCSI command and SAM-2 specifies that
STATUS is not returned for that command, then an SRP response shall not be
returned for the SRP request;"

I am not aware of a SCSI command that specifies that status not be
returned. If there is such a thing then an e.g., would be helpful. If there
is no such thing then this item should be deleted.

5. IBM #65 - Removing non-CMDs from flow control
The only SRP request that even needs to have multiple outstanding
requests in [is?] the command. All others should not be streamed but 
should be interlocked and some should be allowed to occur at any 
time. This all needs to be looked at to make sure the
design point is what we really want.

6. intel0173 -
Change the value of IB IOControllerProfile:Send Message Depth from Reserved
to be the Maximum Initiator Request Limit.  This allows initiators to
efficiently allocate buffers

7. intel0174
IB IOControllerProfile:RDMA Read Depth (reserved -> Maximum IOC-issued RDMA
depth). Allows inits to effficiently allocate RDMA resources

8. intel0175 -
Send Message Size (rsvd -> MAXIMUM INITIATOR TO TARGET IU SIZE) 
    Eliminates need to guess this value




--
Cris Simpson                                          503.712.4333         
Intel EPG/ACD Architecture                           Hillsboro, OR   
PGP Fingerprint:0DA0 418E A27B 0B76 5F02  3DD4 0546 6D13 F88A 1E60
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org




More information about the T10 mailing list