<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Aptos;
panose-1:2 11 0 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
p.xmsonormal, li.xmsonormal, div.xmsonormal
{mso-style-name:x_msonormal;
margin:0in;
font-size:12.0pt;
font-family:"Aptos",sans-serif;}
span.EmailStyle22
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="#467886" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">Apologies, the messaging landscape document is ATIS-1000101 and here is the correct link to the document:
<a href="https://access.atis.org/higherlogic/ws/public/download/78258/ATIS-1000101.pdf">
https://access.atis.org/higherlogic/ws/public/download/78258/ATIS-1000101.pdf</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div id="mail-editor-reference-message-container">
<div>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="margin-bottom:12.0pt"><b><span style="color:black">From:
</span></b><span style="color:black">Chris Wendt <cwendt@somos.com><br>
<b>Date: </b>Tuesday, September 16, 2025 at 7:29</span><span style="font-family:"Arial",sans-serif;color:black"> </span><span style="color:black">AM<br>
<b>To: </b>David Frankel <dfrankel@zipdx.com>, sipnoc25-attendees@sipforum.org <sipnoc25-attendees@sipforum.org><br>
<b>Subject: </b>Re: [EXTERNAL] [sipnoc25-attendees] BOF - Text Messaging Threats & Compliance<o:p></o:p></span></p>
</div>
<div>
<div>
<p class="MsoNormal">Hi David,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It’s a great topic. Just yesterday we had our ATIS/SIP Forum IPNNI Task Force meeting, the standards group most associated with SHAKEN, for those that aren’t aware. And we had a discussion about a path forward to creating an interested
group that focuses on messaging. We recently published a messaging landscape document ATIS-1000100
<span style="color:black"><a href="https://www.sipforum.org/download/voip-interconnection-over-the-public-internet-atis-1000100/">https://www.sipforum.org/download/voip-interconnection-over-the-public-internet-atis-1000100/</a> in which we took the first steps
to try to identify the messaging landscape related to authentication and fraud and opportunities to address these issues.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">As many of you know the messaging world works much differently than the voice world, the companies are often the same but the people are different, the regulation is different, the interconnectivity is different,
and there is a shift from SMS to RCS that seems to suffer from same fraud issues as well.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">So, i think it would be great to talk through these issues and see if there is any potential paths forward we can identify related to this community or work that can happen in IPNNI or a new group focused on these
issues.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">Thanks again for bringing it up David! And very supportive of a BOF session on this topic.<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black"><o:p> </o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="color:black">-Chris<o:p></o:p></span></p>
</div>
</div>
<div id="ms-outlook-mobile-body-separator-line">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="98%" align="center">
</div>
<div id="divRplyFwdMsg">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:black"> sipnoc25-attendees-bounces@sipforum.org <sipnoc25-attendees-bounces@sipforum.org>
on behalf of David Frankel <dfrankel@zipdx.com><br>
<b>Sent:</b> Monday, September 15, 2025 11:52:05 PM<br>
<b>To:</b> sipnoc25-attendees@sipforum.org <sipnoc25-attendees@sipforum.org><br>
<b>Subject:</b> [EXTERNAL] [sipnoc25-attendees] BOF - Text Messaging Threats & Compliance</span>
<o:p></o:p></p>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><strong><span style="font-family:Helvetica">[THIS MESSAGE IS FROM AN EXTERNAL SOURCE REVIEW CAREFULLY]</span></strong><span style="font-family:Helvetica"><o:p></o:p></span></p>
<div class="MsoNormal" align="center" style="text-align:center"><span style="font-family:Helvetica">
<hr size="0" width="100%" align="center">
</span></div>
</div>
<div>
<p class="xmsonormal">Hi fellow SIPNOC’ers –<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">The SIPNOC overview makes references to Text Authentication and Robotext mitigation, but there isn’t anything on the program agenda explicitly addressing texting.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">How about a Tuesday night BoF on this broad topic? I have a few specific morsels I can take a few minutes to share:<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">1) I’ve worked with an academic group that’s demonstrated an AI-based capability to engage with pig butchers at scale, following the bad actors from SMS to other messaging platforms over multiple interactions lasting weeks or months, culminating
in a financial ask. I’m hoping to connect this team with telecom providers that can help them take this to a next level, with the goal of learning enough about the fraudsters’ operations so they can be intercepted before causing further financial harm. What
they’ve done so far is, I think, pretty cool.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">2) Separately, our Robocall Surveillance Platform has collected hundreds of thousands of unsolicited text messages (both SMS and MMS). We analyze message contents and track senders (by NNID for 10DLC source numbers). I can share what we
are seeing, including messages that apparently originate from SIMboxes.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">3) We query short-code senders with HELP and capture their responses. I can report on code-holders’ compliance with the mandate to respond to these requests.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">Please let me know if you’d like to participate and if there are other texting topics you’d like to add. If I get minimal interest, I’ll ask Marc for a room and a time and we’ll hope to drive attendance and have a good discussion. We can
prioritize our agenda to reflect group priorities.<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">I have a handout for #1 – if you’re interested and aren’t able to attend the BoF please ask me for that (or email for a softcopy).<o:p></o:p></p>
<p class="xmsonormal"> <o:p></o:p></p>
<p class="xmsonormal">David Frankel<o:p></o:p></p>
<p class="xmsonormal"><a href="http://www.rraptor.org/">www.rraptor.org</a> <o:p>
</o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>