Re: MIDCOM-MIB: MaxIdleTime

--- Juergen Quittek <[email protected]> wrote:
> Hi Suresh,
> 
> --On 28.06.2004 22:11 h -0700 Pyda Srisuresh wrote:
> 
> > Martin,
> >
> > MaxIdletime is a key attribute of the NAT binding. When you issue a PRR
> > request, a Binding is created by the NAT module, if there isnt one already
> > present. Just that the Binding is not activiated. If a Binding is already
> > present, the PRR will enforce changes to the attributes of the exisiting
> NAT
> > binding.
> >
> > SO, it is necessary to set the MaxIdletime attribute with the PRR request.
> 
> Still, it is just a reservation This policy rule is not enabled before
> it is explicitly switched to 'enabled' state by the PER transaction.
> 
> So, why should a MIDCOM agent specify a maximum idle time in addition
> to the lifetime of the reservation when the reservation is idle anyway
> for its entire lifetime (by its definition)?
> 

[suresh] I agree, MaxIdletime seems optional for PRR. However, I would expect a
PER to follow a PRR in vast majority of the cases. In those cases, the midcom
client is able to reuse the lifetime and maxideltime settings in the PRR, by
merely setting the midcomRuleAdminStatus to Enable to execute a PER.

> Thanks,
> 
>     Juergen

cheers,
suresh
<... stuff deleted>

=====