RE: NOP-IN question

Ken,

There are MUSTs that require a target to send NOP-IN at times. See
10.4.11 on updating MaxCmdSN and 10.19 on resonding to an initiator
ping.  A requirement to have only one "on the wire" wouldn't be
consistant with that. Also, since StatSN isn't advanced for a NOP
initiated by the target and the one sent to update SN values gets no
response from the initiator, the target doesn't know whether that type
of SN is still in transit.  Possibly at one time there was text about
not sending too many of the target-initiated ping NOP-In PDUs but I
don't see anything in the RFC.

Regards,
Pat 

-----Original Message-----
From: Sandars, Ken [mailto:[email protected]] 
Sent: Wednesday, September 26, 2007 5:18 PM
To: Ken Craig; [email protected]
Subject: RE: [Ips] NOP-IN question

Hi Ken,

I can't recall that limit being suggested, nor can I find anything in
the docs.
Given the number of reasons a Nop-In may be generated it seems like an
unusual hurdle to have introduced (ping response, target-initiated ping,
target soliciting ExpStatSN, target advertising new CmdSN counter
values).


Cheers,
Ken Sandars

-----Original Message-----
From: Ken Craig [mailto:[email protected]] 
Sent: Saturday, 22 September 2007 04:40
To: [email protected]
Subject: [Ips] NOP-IN question

During my Target development I convinced myself that somewhere in the
RFC I read that only one Target originated NOP IN was allowed on the
wire at a time per Connection.  However I can no longer find anything
like that in the latest RFC or addendums.  I would like to know if I was
dreaming or can someone point me to a place somewhere where the
statement is made.

Thanks,
Ken Craig


_______________________________________________
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