Re: MIDCOM-MIB: MaxIdleTime

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.

regards,
suresh

--- Martin Stiemerling <[email protected]> wrote:
> 
> 
> --On Dienstag, 22. Juni 2004 12:29 Uhr -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
> 


=====