We are having discussions on capability negotiation in the PANA WG also. I
thought on copying their required functionality here to see if we need this
in OCP. PAA and PAC are the peers.
A)
Pac <-- Paa: i support x,y and z
Pac --> Paa: i would like to use y
B)
Pac --> Paa: enable x
Pac <-- Paa: status (ok, failed)
C)
Pac <-- Paa: you must use y
Pac --> Paa: status (ok, failed)
D)
Pac --> Paa: what do you support?
Pac <-- Paa: i support x,y and z
Regards,
Reinaldo
-----Original Message-----
From: Alex Rousskov [mailto:rousskov(_at_)measurement-factory(_dot_)com]
Sent: Monday, April 21, 2003 11:00 AM
To: ietf-openproxy(_at_)imc(_dot_)org
Subject: RE: Capability Negotiation for OCP
On Mon, 21 Apr 2003, Abbie Barbir wrote:
how about Authentication/Authorization/encrytption.
how/when these will be negotiated/supported etc. Are we
talking about
another encapsulation (like HTTPS or SASL) here or what?
It would depend on the transport protocol selection, I think.
If the transport protocol already has mechanisms to support
Authentication/Authorization/encrytption, then those
mechanisms should be reused. IMO, possibility of this kind of
reuse would be the primary advantage of selecting an existing
application transport (e.g., BEEP) compared to new low-level OCPTRAN.
Since so many things depend on the transport now, we need to select
transport(s) as soon as possible.
Alex.