ietf-openproxy
[Top] [All Lists]

RE: AW: Using XML in OCP transport

2003-05-07 16:14:42

On 19:25 07/05/03, Alex Rousskov said:
On Wed, 7 May 2003, jfcm wrote:
> I set-up my credibility filter to the support of DNS value added
> services.  Obviously XML does not fit the job.

Why not? If XML is only used for BEEP channel management and OCP is
optimized to reuse existing session channles, then I do not see how
XML [performance] prevents OCP from adapting DNS. Can you clarify?

Sure.
complexity, bandwidth, delay, size of the transported information.
Security. I do not say any need for XML in the current needs I cover
(DNS calls, acess redirection, IDNA, authorization of access).

Just security precludes using an existing library without reviewing
entirely. etc.

> There may be different support however.  But was it expected is a
> lean, simple, stuff, robust and secure. Most of the initial
> aplications will be security. Where the flow will be authorised to
> go across, or will be trown away. Then it will probably be URL
> conversion (payment gateways could use that).

How does limited use of XML in OCP prevent the above adaptations?

What do you name limited use of XML? In the type of exchanges
I consider (returning an ACE label for an IDN) can you quanty the
overhead?

The OPES procesor (your wording) filters the proposed DNs and
send them to be rewriten to an OPES server (may be 10 to 15
characters). They are worked on for may possible services :
- conversion in ACE label
- conversion of an ITLD
- permitted access
- security check/taping/statistics (cf. Cisco current reponse to
  tapping legislations)
- etc ...
The new DN is returned. may be 10 to 25 characters so it
may proceed toward the nameserver.

Another application of interest: antispaming strategy. An OPES
processor an MTA calls the sending UA to check the validity
of the mailid (to check the origin) and permits the mail to proceeed.
Sends the MailID (may be 10 to 50 chars) and receives a Y/N.

Another application of interest a cookie server. I load the
data there, not on the caller's machine. When a cookie is called
my OPES processor captures the call and reroute to my cookie
server. Very low, well established, non XML processes.

I have nothing aganst XML when it brings a plus. I just say it
isnot always the case. So it should not be mandatory.
jfc