<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <tt>Hi,<br>
      <br>
      In the mean while, here it is:<br>
      <a class="moz-txt-link-freetext" href="https://www.slideshare.net/slideshow/embed_code/key/Ly9vOqcKuML5Nq">https://www.slideshare.net/slideshow/embed_code/key/Ly9vOqcKuML5Nq</a><br>
      <br>
      Regards,<br>
    </tt>
    <pre class="moz-signature" cols="72">Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com">https://www.opensips-solutions.com</a>
OpenSIPS Bootcamp Pre-Registration
  <a class="moz-txt-link-freetext" href="https://opensips.org/training/OpenSIPS_Bootcamp/">https://opensips.org/training/OpenSIPS_Bootcamp/</a>
</pre>
    <div class="moz-cite-prefix">On 11/26/19 2:52 PM, Jonathan Hulme
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:f3eac821-395e-d902-c112-dac5fc281b1c@hul.me.uk">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <p>Hi Bogdan,</p>
      <p>    Firstly good luck, secondly is this being streamed, or any
        recordings made available afterwards?</p>
      <p>Regards Jonathan<br>
      </p>
      <div class="moz-cite-prefix">On 26/11/2019 12:31, Bogdan-Andrei
        Iancu wrote:<br>
      </div>
      <blockquote type="cite"
        cite="mid:7bd02c95-300c-0379-67e5-38b211441d1d@opensips.org">
        <meta http-equiv="content-type" content="text/html;
          charset=UTF-8">
        <span><span id="ember1176" class="ember-view"><span>Hi All<br>
              <br>
              On 5th of December, I will talk at</span></span></span><span><span
            id="ember1176" class="ember-view"><a
              data-control-name="hashtag" target="_self"
href="https://www.linkedin.com/feed/hashtag/?highlightedUpdateUrns=urn%3Ali%3Aactivity%3A6605066211233460224&keywords=%23sipnoc2019&originTrackingId=7AFxItq%2BFji6frtUIfI3qg%3D%3D"
              id="ember1179" class="hashtag-link ember-view"
              moz-do-not-send="true"><span dir="ltr" id="ember1180"
                class="hashtag-a11y ember-view"><span></span></span></a><span>
              SIPNOC 2019 [1] about the new STIR/SHAKEN </span></span></span><span><span
            id="ember1176" class="ember-view"><span>implementation [2]
              in OpenSIPS 3.1</span></span></span><span><span
            id="ember1192" class="ember-view"><span>, about the usage
              models and the associated risks.<br>
              <br>
            </span></span></span><br>
        <span><span id="ember1192" class="ember-view"><span><span><span
                  id="ember1192" class="ember-view"><span>[1] <a
                      class="moz-txt-link-freetext"
                      href="https://www.sipforum.org/news-events/sipnoc-2019-overview/"
                      moz-do-not-send="true">https://www.sipforum.org/news-events/sipnoc-2019-overview/</a><br>
                    [2] <a class="moz-txt-link-freetext"
href="https://github.com/OpenSIPS/opensips/tree/master/modules/stir_shaken"
                      moz-do-not-send="true">https://github.com/OpenSIPS/opensips/tree/master/modules/stir_shaken</a><br>
                    <br>
                  </span></span></span><br>
              10:45am – 11:15am: The Usage Models and Risks of
              STIR/SHAKEN, Seen from the Pragmatism of an
              Implementation.<br>
            </span></span></span><br>
        <span><span id="ember1192" class="ember-view"><span>Abstracts: <br>
              There are many things still to be defined and settled in
              STIR/SHAKEN from the regulatory perspective. Nevertheless,
              this presentation wants to bring this topic under scrutiny
              from the point of view of an implementation in the
              OpenSIPS SIP Server. So, what are the possible STIR/SHAKEN
              usage scenarios from the perspective of how the SIP
              traffic is handled and, more important, how the
              certificates are managed. While a SIP server may cover the
              full horizontal of authorization, inspection and
              verification processes, it is more relevant to see what
              are the possible models when comes to certificate
              managing. And definitely there is a need for coexistence
              between a certificate-agnostic model and a certificate
              self-managing model, in order to answer to future
              standardization and usage challenges. ITSP, Telcos and
              Carries are to deploy and use STIR/SHAKEN  implementations
              in the real word, so are they fully aware of the security
              and performance risks introduced by such a service? Well,
              the exercise of producing such a STIR/SHAKEN
              implementation is a good way to answer these questions and
              get yourselves ready. <br>
              <br>
              <br>
              See you in Washington! <br>
            </span></span></span>
        <pre class="moz-signature" cols="72">-- 
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  <a class="moz-txt-link-freetext" href="https://www.opensips-solutions.com" moz-do-not-send="true">https://www.opensips-solutions.com</a>
OpenSIPS Bootcamp Pre-Registration
  <a class="moz-txt-link-freetext" href="https://opensips.org/training/OpenSIPS_Bootcamp/" moz-do-not-send="true">https://opensips.org/training/OpenSIPS_Bootcamp/</a>
</pre>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <pre class="moz-quote-pre" wrap="">_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@lists.opensips.org" moz-do-not-send="true">Users@lists.opensips.org</a>
<a class="moz-txt-link-freetext" href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" moz-do-not-send="true">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
      </blockquote>
    </blockquote>
    <br>
  </body>
</html>