This was formulated for generality. In a pure firewall, no reservations occur or are needed, but the semantics were defined so that the invoker doesn't need to know the configuration of the middlebox.

Chisholm, Sharon (CAR:ZZ00) wrote:
Hi

The text shows up in a number of requests

For example, in the terminology section, there is the following definition

"policy reserve rule        A policy rule containing a reserve action.
                              The policy condition of this rule is
                              always true.  The action is the
                              reservation of just an IP address or a
                              combination of an IP address and a range
                              of port numbers on neither side, one side,
                              or both sides of the middlebox, depending
                              on the middlebox configuration."

 Sharon

-----Original Message-----
From: Martin Stiemerling [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 16, 2007 11:00 AM
To: Chisholm, Sharon (CAR:ZZ00)
Cc: [email protected]; Taylor, Tom-PT (CAR:AR00); Melinda Shore; Magnus Westerlund; Jürgen Quittek
Subject: Re: Generate Review of RFC 3989 as Proposed Standard

Hi Sharon,

Thank you very much for the review.

It looks like we can quickly fix issues 2 to 8 by adding appropriate clarifications.

But we have a question on issue No.1:
1. I didn't find where it was explained the reasoning behind being able to send a request that reserves stuff on neither side of the middlebox.
It would seem a waste of processing.
Which request are you referring to?

Thanks,

   Jürgen and Martin





_______________________________________________
Gen-art mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/gen-art

Reply via email to