= Сообщение: 6189 из 7128 ====================================== FTSC_PUBLIC = От : Alexey Vissarionov 2:5020/545 01 Mar 22 04:40:04 Кому : Rob Swindell 01 Mar 22 04:40:04 Тема : Directly include binary data in messages FGHI : area://FTSC_PUBLIC?msgid=2:5020/545+621d8338 На : area://FTSC_PUBLIC?msgid=31649.ftsc_pub@1:103/705+2682e92b = Кодировка сообщения определена как: CP866 ================================== ============================================================================== Good ${greeting_time}, Rob!
28 Feb 2022 12:58:50, you wrote to James Coyle:
RS> FYI, a few years ago, I applied for an IANA sanctioned TCP port RS> number assignment for BINKPS (BINKP over implicit TLS, e.t port RS> 24553). After a few back-and-forths, this was their final answer: >>> 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.
Very predictable. There are only 65534 ports, and reserving them to some specific applications is very unwise.
That's why SRV NS RRs were invented (and documented by FTSC since 2013).
RS> So it looks like explicit/opportunistic TLS (e.g. STARTTLS) is RS> the future for BINKP if it's going to become any kind of Internet RS> standard.
For now, we have two working implementations for encrypted connection - SSH, supported by binkd since version 1.1a-22 released in 2013, and SSL/TLS, supported by binkd since the same version (requires a companion software to accept incoming connections, but may run on HTTPS port in conjunction with nginx) and Mystic (as JC wrote earlier).
The use of SSH and HTTPS ports has an advantage of multiplexing the incoming connections among different applications.
-- Alexey V. Vissarionov aka Gremlin from Kremlin gremlin.ru!gremlin; +vii-cmiii-ccxxix-lxxix-xlii
