<div dir="ltr"><div dir="ltr">By reading the RFCs I was able to grasp 75% of it, it's well written and covers your <b>clear </b>constraint, at least on how to verify the SIP header comes from a trustworthy authority (If you agree on the root authority)<br><div>Practically implementing STIR/SHAKEN has bureaucracy involved.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 24, 2023 at 9:38 PM Jawaid Bazyar via VoiceOps <<a href="mailto:voiceops@voiceops.org">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Is there a good clear document somewhere describing how STIR/SHAKEN is supposed to work?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Oct 24, 2023 at 9:33 PM Matthew Crocker via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
> On Oct 24, 2023, at 9:13 PM, Peter Beckman via VoiceOps <<a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br>
> <br>
> CAUTION: This email originated from outside of Crocker. Do not click links or open attachments unless you recognize the sender and know the content is safe.<br>
> <br>
> <br>
> The challenge is how do you authenticate the end "carrier" or service<br>
> provider?<br>
> <br>
<br>
STIR/SHAKEN<br>
<br>
<br>
> Sure, anyone who leases numbers directly from NANPA can look up the carrier<br>
> of record and exchange traffic directly, but any business who also leases<br>
> numbers INDIRECTLY gets cut out and still needs to pay their upstream<br>
> carrier(s) to place/receive calls, either by channels or per minute, even<br>
> if their upstream is directly peered and not transiting the PSTN at all.<br>
> <br>
> If this would be for the end user, then NANPA would have to delegate to the<br>
> leasee, the leasee delegate to the reseller, the reseller to the end user,<br>
> then the end user could publish their VoIP contact info, and anyone could<br>
> call directly via VoIP, cutting out all of the middle peers.<br>
> <br>
> But, as another person said, this is ripe for abuse, and with no motivation<br>
> by NANPA or the larger carriers to make calls less expensive for the<br>
> reseller or end user, I see this going nowhere. Until there is some value<br>
> in NANPA (plus all the other country telephony organizations) and the<br>
> direct carriers leasing numbers to do so.<br>
> <br>
> Beckman<br>
> <br>
>> On Tue, 24 Oct 2023, Ross Tajvar via VoiceOps wrote:<br>
>> <br>
>> I can think of a few ways that could be adapted into a platform more like<br>
>> an Internet exchange, but as others have said, it just doesn't seem worth<br>
>> it.<br>
>> <br>
>> On Tue, Oct 24, 2023, 5:31 PM Jawaid Bazyar via VoiceOps <<br>
>> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br>
>> <br>
>>> I think schemes like DUNDI (and some of the others mentioned here) suffer<br>
>>> from a trust issue – what’s to prevent operator X from poisoning the<br>
>>> protocol with bogus “stolen” numbers?<br>
>>> <br>
>>> <br>
>>> <br>
>>> On Tue, Oct 24, 2023 at 5:25 PM Jared Smith via VoiceOps <<br>
>>> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br>
>>> <br>
>>>> On Tue, Oct 24, 2023 at 8:49 AM Mike Hammett via VoiceOps <<br>
>>>> <a href="mailto:voiceops@voiceops.org" target="_blank">voiceops@voiceops.org</a>> wrote:<br>
>>>> <br>
>>>>> This was in another thread, but I broke it out into it's own<br>
>>>>> conversation. Someone had asked:<br>
>>>>> <br>
>>>>> ---<br>
>>>>> I am joining this thread late, but, would anyone out there be interested<br>
>>>>> in exchanging traffic with other carriers directly over SIP?<br>
>>>>> <br>
>>>> <br>
>>>> Just another point of VoIP history trivia at this point... but in<br>
>>>> addition to things like ENUM and ITAD, Mark Spencer of Asterisk fame also<br>
>>>> invented Dundi, which was an encrypted peer-to-peer protocol for route<br>
>>>> advertisement and discovery. As far as I know, very few people besides me<br>
>>>> ever put it in production, but it worked really well at the time. (Of<br>
>>>> course, it's been about 17 or 18 years now since I used it in production.)<br>
>>>> <br>
>>>> -Jared<br>
>>>> _______________________________________________<br>
>>>> VoiceOps mailing list<br>
>>>> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
>>>> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
>>>> <br>
>>> _______________________________________________<br>
>>> VoiceOps mailing list<br>
>>> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
>>> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
>>> <br>
>> <br>
> <br>
> ---------------------------------------------------------------------------<br>
> Peter Beckman Internet Guy<br>
> <a href="mailto:beckman@angryox.com" target="_blank">beckman@angryox.com</a> <a href="https://www.angryox.com/" rel="noreferrer" target="_blank">https://www.angryox.com/</a><br>
> ---------------------------------------------------------------------------<br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
> _______________________________________________<br>
> VoiceOps mailing list<br>
> <a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><b>Pinchas S. Neiman</b></div><div>Software Engineer At ESEQ Technology Corp.</div><div>845.213.1229 #2</div><img width="200" height="68" src="https://ci3.googleusercontent.com/mail-sig/AIorK4z1Lx063u893FlkIV1C3aJbVPjgKnaA2Xu8q_iPdyFOnK_JX05usgghpAIwmPqB-1t-3fdaShNHoCPf7fFwa1twYZt-xjsBZheqmsCQrg"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div>