
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Updated to sip/2<div class=""><br class=""></div><div class=""><a href="https://www.ietf.org/archive/id/draft-johansson-sip-alpn-02.html" class="">https://www.ietf.org/archive/id/draft-johansson-sip-alpn-02.html</a></div><div class=""><br class=""></div><div class="">Thanks for the feedback!</div><div class=""><br class=""></div><div class="">/O<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 21 Aug 2021, at 17:04, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" class="">s.safarov@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="auto" class="">I see some registered names contains protocol version.<div dir="auto" class="">May need use "sip/2" as registered name?</div><div dir="auto" class=""><br class=""></div><div dir="auto" class=""><a href="https://medium.com/geekculture/exploring-application-layer-protocol-negotiation-alpn-c47b5ec3b419" class="">https://medium.com/geekculture/exploring-application-layer-protocol-negotiation-alpn-c47b5ec3b419</a></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 18, 2021, 2:09 PM Olle E. Johansson <<a href="mailto:oej@edvina.net" class="">oej@edvina.net</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word;line-break:after-white-space" class=""><br class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">On 18 Aug 2021, at 11:59, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" target="_blank" rel="noreferrer" class="">s.safarov@gmail.com</a>> wrote:</div><br class=""><div class=""><div dir="auto" class="">Why not register "msrp" extension in this draft?</div></div></blockquote>Simply because I personally did not need it. But you are right, we do have an MSRP module that can share the same port, very much like XHTTP.</div><div class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Also I think we need customer extension support here.</div><div dir="auto" class="">Via TLS we can send Kamailio DMQ messages.</div><div dir="auto" class="">Generally we can use "sip" extension, but user defined will be more accurate.</div><div dir="auto" class=""><br class=""></div><div dir="auto" class="">Say we can define extensions prefix "user-defined-“</div></div></div></blockquote>I will have to go back to the ALPN rfc and check if there’s any mention of user-defined. THat would propably be a larger addition to the ALPN function, so it would require a full RFC publication.</div><div class=""><br class=""></div><div class="">Thanks for the feedback!</div><div class="">/O<br class=""><blockquote type="cite" class=""><div class=""><div dir="auto" class=""><div dir="auto" class=""><br class=""></div></div><br class=""><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Aug 17, 2021, 6:46 PM Olle E. Johansson <<a href="mailto:oej@edvina.net" target="_blank" rel="noreferrer" class="">oej@edvina.net</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Kamailians!<br class="">

<br class="">

I’ve written a very short IETF draft in order to register a SIP TLS ALPN:<br class="">

<a href="https://datatracker.ietf.org/doc/draft-johansson-sip-alpn/" rel="noreferrer noreferrer noreferrer" target="_blank" class="">https://datatracker.ietf.org/doc/draft-johansson-sip-alpn/</a><br class="">

<br class="">

An ALPN is a short code used in TLS connection setup to inform the server of the “next protocol” after TLS connection is setup. This way, a server listening to a port, like 5061 and 443, can support multiple protocols on the same port. <br class="">

<br class="">

In Kamailio, we support HTTP 1 and SIP because they’re very much alike, but if there’s a need to support other protocols it will be hard, like MSRP. With ALPN support we could when using TLS.<br class="">

<br class="">

In addition, newer versions of HTTP will be harder to support using the same parser. ALPN makes it easier.<br class="">

<br class="">

I do hope the registration will come through. If so, maybe we can discuss what’s needed to support ALPN for SIP and HTTP in the TLS code.<br class="">

<br class="">

Cheers,<br class="">

/O<br class="">

_______________________________________________<br class="">

Kamailio (SER) - Development Mailing List<br class="">

<a href="mailto:sr-dev@lists.kamailio.org" rel="noreferrer noreferrer" target="_blank" class="">sr-dev@lists.kamailio.org</a><br class="">

<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" rel="noreferrer noreferrer noreferrer" target="_blank" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br class="">

</blockquote></div>

_______________________________________________<br class="">Kamailio (SER) - Development Mailing List<br class=""><a href="mailto:sr-dev@lists.kamailio.org" target="_blank" rel="noreferrer" class="">sr-dev@lists.kamailio.org</a><br class=""><a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" target="_blank" rel="noreferrer" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br class=""></div></blockquote></div><br class=""></div>_______________________________________________<br class="">

Kamailio (SER) - Development Mailing List<br class="">

<a href="mailto:sr-dev@lists.kamailio.org" target="_blank" rel="noreferrer" class="">sr-dev@lists.kamailio.org</a><br class="">

<a href="https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev" rel="noreferrer noreferrer" target="_blank" class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev</a><br class="">

</blockquote></div>

_______________________________________________<br class="">Kamailio (SER) - Development Mailing List<br class=""><a href="mailto:sr-dev@lists.kamailio.org" class="">sr-dev@lists.kamailio.org</a><br class="">https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev<br class=""></div></blockquote></div><br class=""></div></body></html>