Re: target opcodes allowed for discovery sessions

When I look at 3.3 it says the target must reject all other requests. But I don't think a NOP-out is a request. Is there another part of the draft that says the initiator can't send a NOP-out during discovery?

Eddy
  ----- Original Message ----- 
  From: Julian Satran 
  To: Paul Hughes 
  Cc: IP Storage Mailing List (E-mail) 
  Sent: Tuesday, November 21, 2006 2:38 AM
  Subject: Re: [Ips] target opcodes allowed for discovery sessions



  As I re-read the draft I can't find any text that forbids a target to send NOP-IN in a discovery session. 
  But that was definitely not the intent and don't be surprised if some initiator will drop your session. 
  Also Mallikarjun may want to mention this oversight in the implementation guide. 

  Julo 


        "Paul Hughes" <[email protected]> 
        21/11/06 06:11 
       To "IP Storage Mailing List \(E-mail\)" <[email protected]>  
              cc  
              Subject [Ips] target opcodes allowed for discovery sessions 

              

       



  Is a target allowed to send an Asynchronous Message PDU to request a logout of a discovery session? 
  Is a target allowed to send a NOP-In PDU to an initiator on a connection that's part of a discovery session?  If so, should I assume that the TTT must be 0xFFFFFFFF since the initiator isn't allowed to send a NOP-Out PDU on a discovery session? 

  Thanks, 
  Paul 

  _______________________________________________
  Ips mailing list
  [email protected]
  https://www1.ietf.org/mailman/listinfo/ips





------------------------------------------------------------------------------


  _______________________________________________
  Ips mailing list
  [email protected]
  https://www1.ietf.org/mailman/listinfo/ips

_______________________________________________
Ips mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/ips