RE: DefaultTime2Retain Negotiation during Discovery Session

-----Original Message-----
From: William Studenmund [mailto:[email protected]]
Sent: Saturday, August 18, 2007 8:29 AM
To: RAM SUNEE
Cc: Ips
Subject: Re: [Ips] DefaultTime2Retain Negotiation during Discovery
Session
Importance: High


On Aug 18, 2007, at 8:08 AM, RAM SUNEE wrote:

> Hello,
>
> During LoginOperational negotiation phase of Discovery Session,
> Initiator
> didn't initiate negogiation for DefaultTime2Retain key.
> Target tried to negotiate for this key a value of 0,but initiator
> tried to
> enter full feature phase without responding to this specific key.
> In this case what target is supposed to do?

What do you mean "tried to enter full feature phase without
responding"? It sent back an empty PDU requesting transitioning to
FFP? Did the target correctly not offer to transition to FFP (did not
set the 'T' bit in the login response)? The target should not set the
'T' bit and it should wait for the initiator to answer, and eventually
time out the login.

 From the RFC:
12.16.  DefaultTime2Retain

    Use: LO Senders: Initiator and Target Scope: SW

    DefaultTime2Retain=<numerical-value-0-to-3600>

    Default is 20.  Result function is Minimum.

So it's valid to negotiate in a discovery session.

RAM> Target didn't set 'T' bit when it sent Login response with
DefaultTime2Retain key.
What I mean here is that Intiator responded back with a Login request with
an empty PDU(no keys), requesting transition to FFP.
Because initiator responded back here, there is no question of timing out
the login.What is the correct way the target should handle this?



> Also, if the same situation happens during Normal Session,what the
> target is
> supposed to do?

Same thing.

Take care,

Bill



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