ietf-openproxy
[Top] [All Lists]

Re: Start on OPES protocol work

2003-02-17 03:06:12
On 03:28 17/02/03, Reinaldo Penno said:
Hi,

the capability negotiation was in part to avoid having to repeat fields in
the packets since the two ends would have agreed in the protocol version and
several other parameters. Some other protocols where there is some form of
capability negotiation (specially routing protocols) repeat the version
number in the packets, but routing is something that doesn't change often
(at least in theory) and you can put thousands of routes in one packet, so
overhead is not an issue.

I see the the callout protocol having a control phase and a data phase. In
the control phase the version number will be in the packet (in the header or
as another parameter) so that the two ends can agree in the minimum set of
semantics. In the data phase where the opes processor is making the callout
work for its meal, there is no need to the version number (and others)
anymore.

Some people might argue that a version number in the packets make debugging
easier...but we can also achieve this by having a standardized list of
operations (for each protocol version) that a opes processor can request. Of
course extensions should go though this WG and normal IETFT process. Just
like PPP extensions.

what do you think?

IMHO there should be several layers.

1. the link. Is the service here. What are the general paramenters of the service (version, owner, rates, oerating terms and conditions, etc.). Also is the link in operation (last time of exchange)

2. the connexion. What is the accepted traffic rate, the type of encryption, the accepted protocols, etc. Also is the connexion alive (last time of an exchange)

3. the cession. Who is demanding, who is paying, the defaults to be used, the service priority, etc. Radom key of the pseudo-random ref. Last exchange pseudo-random ref, expected next exchange pseudo-random ref.

jfc



---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.454 / Virus Database: 253 - Release Date: 10/02/03
<Prev in Thread] Current Thread [Next in Thread>