Re: MIDCOM-MIB: MaxIdleTime

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)?

Thanks,

    Juergen
-- 
Juergen Quittek        [email protected]        Tel: +49 6221 90511-15
NEC Europe Ltd.,       Network Laboratories        Fax: +49 6221 90511-55
Kurfuersten-Anlage 36, 69115 Heidelberg, Germany   http://www.ccrle.nec.de

> regards,
> suresh
>
> --- Martin Stiemerling <[email protected]> wrote:
>>
>>
>> --On Dienstag, 22. Juni 2004 12:29 h -0400 Melinda Shore
>> <[email protected]> wrote:
>>
>> | On Monday, June 21, 2004, at 09:34 AM, Martin Stiemerling wrote:
>> |> Policy Reserve Rule (PRR) reserves just an external IP address and
>> |> port number at NAT, but does not necessarily allocated any NAT
>> |> binding. So MaxIdleTime is not required in PRR, since in anyway no
>> |> data can pass the NAT bindings (sessions are not generated at all).
>> |
>> | Martin - I have a question about this.  If the PRR is used in some sense
>> | to do admission control (are the resources being requested available?),
>> | should
>> | the duration of the binding be considered in making an admission control
>> | decision?
>>
>> The duration of the binding can be considered in admission control.  PRR
>> implements a lifetime parameter that indicates how long the reservation
>> itself should be kept alive at the middlebox.  If the middlebox decides
>> that this lifetime is too big (or even too small) it can reject it with an
>> error message.
>>
>>   Martin
>>
>> |
>> | Thanks,
>> |
>> | Melinda
>> |
>>
>>
>>
>> _______________________________________________
>> midcom mailing list
>> [email protected]
>> https://www1.ietf.org/mailman/listinfo/midcom
>>
>
>
> =====
>
>
> _______________________________________________
> midcom mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/midcom