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