<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<font size="+1">Peter,<br>
<br>
the initial rollout of S/S does not include delegated
certificates. It's being rushed so at least basic call
blocking/tracing can be done by tier one carriers. It is usable in
the limited design but doesn't cover all use cases. Using the
public CA is still the work in progress from my understanding.<br>
<br>
Delegated certs is a much more complex call flow and has potential
holes in the vetting process of the call flow chain. It has to
allow for a customer to pass the call through several App/CPAAS
providers before hitting the telco operators so the number of
companies that need to be properly vetted for ownership and right
to use information is MUCH larger.<br>
<br>
I think eventually it will be effective in cutting down the number
of rogue callers and catching the ones that are egregious
offenders.<br>
<br>
~Glen<br>
<br>
</font><br>
<div class="moz-cite-prefix">On 12/18/2019 21:09, Peter Beckman
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:alpine.BSF.2.20.1912190007520.8519@nog2.angryox.com">On
Tue, 17 Dec 2019, Calvin Ellison wrote:
<br>
<br>
<blockquote type="cite">If you want to keep up to date on this,
join the ATIS IP NNI and SIP Forum
<br>
mailing lists. You'll see frequent notifications as the policy
and protocol
<br>
documents get updated.
<br>
<br>
On Tue, Dec 17, 2019 at 3:49 PM Peter Beckman
<a class="moz-txt-link-rfc2396E" href="mailto:beckman@angryox.com"><beckman@angryox.com></a> wrote:
<br>
<br>
<blockquote type="cite"> In my case, we use different
termination carriers than our origination
<br>
carriers in many situations. If we are authorized to use a
DID for
<br>
CallerID, but it is not from the termination carrier, how
does the
<br>
termination carrier know to set the attestation to full?
<br>
<br>
</blockquote>
<br>
This one of the things being worked out. There are frameworks
for
<br>
certificate delegation and TN authorization, but I can't speak
to the
<br>
details.
<br>
</blockquote>
<br>
Awesome to hear Calvin. I was under the impression that the
STIR/SHAKEN
<br>
standard had been ratified by the participating carriers and they
were
<br>
moving forward. I have not seen anything about cert delecation
and TN
<br>
authorization in the technical specs.
<br>
<br>
Is STIR/SHAKEN not really completed and ready for deployment yet?
The FCC
<br>
and larger carriers seem to be moving forward with test
implementations
<br>
without of TN authorization and delegation.
<br>
<br>
Beckman
<br>
---------------------------------------------------------------------------
<br>
Peter Beckman
Internet Guy
<br>
<a class="moz-txt-link-abbreviated" href="mailto:beckman@angryox.com">beckman@angryox.com</a>
<a class="moz-txt-link-freetext" href="http://www.angryox.com/">http://www.angryox.com/</a>
<br>
---------------------------------------------------------------------------
<br>
_______________________________________________
<br>
VoiceOps mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Glen Gerhard
<a class="moz-txt-link-abbreviated" href="mailto:glen@cognexus.net">glen@cognexus.net</a>
858.324.4536
Cognexus, LLC
7891 Avenida Kirjah
San Diego, CA 92037
</pre>
</body>
</html>