= Сообщение: 6188 из 7128 ====================================== FTSC_PUBLIC = От : James Coyle 1:129/215 28 Feb 22 17:05:07 Кому : Rob Swindell 28 Feb 22 17:05:07 Тема : Re: Re^2: Re^4: Directly include binary data in messages FGHI : area://FTSC_PUBLIC?msgid=1:129/215+e4b54183 На : area://FTSC_PUBLIC?msgid=31649.ftsc_pub@1:103/705+2682e92b = Кодировка сообщения определена как: ASCII ================================== Ответ: area://FTSC_PUBLIC?msgid=31653.ftsc_pub@1:103/705+26834a89 ============================================================================== 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.
