ietf-openproxy
[Top] [All Lists]

Re: OCP transport nomination

2003-05-05 15:18:56

[ speaking as the beep guy... ]
    
    
    
OK, then there's no specification of the user-BEEP API for using TLS.
    
there is no specification of the user-BEEP API for XYZ, regardless of
the value of XYZ.

    
What support do the implementations of BEEP provide?  How are the
cryptographic preferences for each TLS connection specified?  My point
being that it would seem pretty easy for an OCPTRAN API implementor to
set up things in such a way that the user was responsible for opening
the correct kind of TLS connection and then passing the handle to it
to OCPTRAN.

isn't that sort of stuff up to each implementor? isn't the job of the
specification suppose to say things like what options are allowed,
without mandating a particular api, calling convention, etc.?
    
/mtr

    

<Prev in Thread] Current Thread [Next in Thread>