[stir] Re: [art] Re: Re: Re: For those of you who follow this kind of stuff.

[Tim Bray <[e-mail]>]

 You guys are speaking in Sumerian :)  Is this something that any
particular chunk of the IETF (or of the industry or of society) should
worry about?  -T

On Oct 7, 2025 at 5:42:23 PM, Brett Nemeroff <[e-mail]>
wrote:

> Hello Roman,
>
> In my opinion, US Carriers are unlikely to accept vanilla RCD data because
> of the lack of defined KYC.  RCD is a very good vehicle for delivering the
> RCD, but it depends upon implicit trust of the originating service
> provider. “Vanilla” RCD offered like this to terminating service providers
> gives no assurance to the terminating service provider that the originator
> performed any specific KYC.
>
> CTIA’s BCID is based on RCD but details an ecosystem with specific KYC
> requirements. Participating in this ecosystem will allow for the delivery
> and native presentation of RCD.
>
> It’s worth noting that without a defined ecosystem for RCD such as BCID,
> RCD provides little (trust)  benefit over traditional CNAM other than the
> fingerprints of the originating service provider for enforcement purposes.
>
> -Brett
>
>
>
> Brett Nemeroff
> VP of Engineering - Voice
> [e-mail] <%7BE-mail%7D> | 1-512-203-3884
>
> [image: Logo.png] <https://www.numeracle.com/>
>
> Empowering Calls with
> Identity Management
> <https://www.numeracle.com/insights/entity-identity-management-to-empower-your-calls>
>
>
>
> * CONFIDENTIAL From: *Roman Shpount <[e-mail]>
> *Date: *Tuesday, October 7, 2025 at 7:24 PM
> *To: *Richard Shockey <[e-mail]>
> *Cc: *IETF STIR Mail List <[e-mail]>, [e-mail] <[e-mail]>
> *Subject: *[stir] Re: [art] Re: For those of you who follow this kind of
> stuff.
>
> You don't often get email from [e-mail]. Learn why this is
> important <https://aka.ms/LearnAboutSenderIdentification>
> In my day job, I see a lot of robocalls coming through the LEC local
> switches as TDM, as local re-origination with spoofed ANI.
>
> I would also love to sign Rich Call Data with my SPC token and not have
> wireless carriers discard this data. If I provide the information about my
> customer, I am unsure why I need to pay someone else to sign this
> information.
> _____________
> Roman Shpount
>
>
> On Tue, Oct 7, 2025 at 8:11 PM Richard Shockey <[e-mail]> wrote:
>
>
>
> It wont . You mean the legacy TDM/SS7 crap…this is the beginning of
> mandating all SIP in the US realtime US voice network as the British have
> done.
>
>
>
> I would not want to own a Tandem Access network.
>
>
>
> The US industry is pretty clear on this.  You only need to read the FCC
> 17-97 docket at the FCC ECFS website to understand where the players
> actually are.
>
>
>
> This again is my day job.
>
>
>
>
>
> Richard Shockey
>
> Shockey Consulting LLC
>
> Chairman of the Board SIP Forum
>
> www.shockey.us
>
> www.sipforum.org
>
> richard<at>shockey.us
>
> Skype-Linkedin-Facebook –Twitter  rshockey101
>
> PSTN [phone]
>
>
>
>
>
> *From: *Roman Shpount <[e-mail]>
> *Date: *Tuesday, October 7, 2025 at 7:37 PM
> *To: *Richard Shockey <[e-mail]>
> *Cc: *IETF STIR Mail List <[e-mail]>, <[e-mail]>
> *Subject: *[art] Re: [stir] For those of you who follow this kind of
> stuff.
>
>
>
> How would this work with PSTN links?
>
> _____________
> Roman Shpount
>
>
>
>
>
> On Tue, Oct 7, 2025 at 6:59 PM Richard Shockey <[e-mail]> wrote:
>
>
> The United States government is going to mandate Rich Call Data in the
> network.
>
> https://docs.fcc.gov/public/attachments/DOC-415059A1.pdf
>
>
> Richard Shockey
> Shockey Consulting LLC
> Chairman of the Board SIP Forum
> www.shockey.us <http://www.shockey.us>
> www.sipforum.org
>
> richard<at>shockey.us
> Skype-Linkedin-Facebook –Twitter rshockey101
> PSTN [phone]
>
>
>
>
>
>
> _______________________________________________
> stir mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>
> _______________________________________________ art mailing list --
> [e-mail] To unsubscribe send an email to [e-mail]
>
> _______________________________________________
> art mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>