Subj : Re: Re^2:  Re^4:  Directly include binary data in messages
To   : James Coyle
From : Rob Swindell
Date : Mon Feb 28 2022 12:58 pm

 Re: Re: Re^2:  Re^4:  Directly include binary data in messages
 By: James Coyle to Tim Schattkowsky on Mon Feb 28 2022 10:15 am

> For these reasons, I was experimenting with opportunistic SSL for BINKP.
> With opportunistic SSL the connection is always on the same port and if both
> clients support SSL it will convert the connection prior to any
> authentication.

FYI, a few years ago, I applied for an IANA sanctioned TCP port number assignment for BINKPS (BINKP over implicit TLS, e.t port 24553). After a few back-and-forths, this was their final answer:
-=-=-=-=-=-
We have a response from the expert:

The reviews for port assignments is subject to RFCs 6335 and 7605. We have provided advice according to those docs.

The way forward that has been chosen and deployed is not consistent with those docs; we therefore do not recommend approval of the request.
-=-=-=-=-=-

So it looks like explicit/opportunistic TLS (e.g. STARTTLS) is the future for BINKP if it's going to become any kind of Internet standard.
--
                                           digital man (rob)

Synchronet "Real Fact" #86:
Stephen and Rob have a fledgling podcast at http://techdorks.net (also iTunes)
Norco, CA WX: 78.8�F, 11.0% humidity, 8 mph W wind, 0.00 inches rain/24hrs

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.