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

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

Well the answer sucks, but your foresight in this issue was awesome :)

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

I hadn't considered the IANA aspect of this.  I have no experience with that stuff so naturally I yield to those who do.  Is it a dead end to try again?

I can see BINKPS not having a large enough use-case to warrant a port. But if they did give us BINKP port then I feel there is a case to be made that they must also support the secure version of it.

If you are still willing to support a STARTTLS BINKP I am down to pick that up again and work on something together (and with whoever else wants to join in). I can look for a backup of the code that did it (this weekend) and send something your way, or we can start from scratch... Whatever works for you.

... Just another prisoner of gravity!

--- Mystic BBS v1.12 A48 2022/02/28 (Windows/64)
* Origin: Sector 7 * Mystic WHQ (1:129/215)