<html 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)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 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:10.0pt;
font-family:"Aptos",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#467886;
text-decoration:underline;}
span.EmailStyle19
{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>
</head>
<body lang="EN-US" link="#467886" vlink="#96607D" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:12.0pt">Just as a follow up from the SIPit BOF discussion last night, we did end up having a very productive discussion with some definite interest in moving forward.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">There was support and critical mass for having an initial event (thinking after Thanksgiving) to starting with a bit of a hackathon style event where industry participants come together to discuss, first what
we want to focus on in a SIPit interop event, but also identify and discuss technical and standards issues, tools/conformance tools development and other ideas for what everyone is looking for.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">We want feedback on how we reconstitute SIPit and make it valuable to our members and the industry and potentially get back to a regular cadence.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">The consensus was that we could try having a hybrid event where we have a physical location available (could be Somos Office in Herdon, I’m happy to offer that, but other offers are very welcome as well).
We would also of course make remote participation available to make it accessible to as many participants as possible.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Looking forward to working with interested community members on moving this forward and appreciate the input. Feel free to reach out to me or on this list if you have any questions or want to be involved
and participate.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Thanks to everyone that made it to the BOF!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><o:p> </o:p></span></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="font-size:12.0pt;color:black">From:
</span></b><span style="font-size:12.0pt;color:black">Chris Wendt <cwendt@somos.com><br>
<b>Date: </b>Tuesday, September 16, 2025 at 12:32</span><span style="font-size:12.0pt;font-family:"Arial",sans-serif;color:black"> </span><span style="font-size:12.0pt;color:black">PM<br>
<b>To: </b>sipnoc25-attendees@sipforum.org <sipnoc25-attendees@sipforum.org><br>
<b>Subject: </b>BOF proposal: SIPit interoperability event topics<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-size:12.0pt">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"><br>
As Richard mentioned at the start of the day there is a number of folks that would like to continue the tradition of SIPit as a way for the technical and operational leaders in the industry to perform interop, product and though leaders to discuss the use and
needs within the standards, give feedback to the authors and implementers of the specs. It’s a great forum to get together and talk about the use of the specs in the real world to facilitate interoperability and how our services can interact in real networks.
Below is a proposed list of potential interop and discussions to be had at a SIPit event, but please add to the list and come up with other specs/interop that is needed by the industry.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Thanks!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">-Chris<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Potential topics to discuss:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Rich Call Data PASSporTs (<a href="https://datatracker.ietf.org/doc/html/rfc9795">RFC9795</a>) usage: within PASSporTs and identity headers, other usages OOB etc.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Rich Call Data Call-Info Usage (<a href="https://datatracker.ietf.org/doc/html/rfc9796">RFC9796</a>) usage for UNI interfaces to devices<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Certificate compliance to specifications and certificate policies:
<a href="https://datatracker.ietf.org/doc/html/rfc8226">RFC8226</a>/RFC9116/<a href="https://access.atis.org/apps/group_public/download.php/69428/ATIS-1000080.v005.pdf">ATIS-1000080.v005</a>/<a href="https://access.atis.org/higherlogic/ws/public/download/70989/ATIS-1000084.v003.pdf">ATIS-1000084.v003</a>
and <a href="https://authenticate.iconectiv.com/sites/authenticate/files/2025-02/CP_v1.4.2.pdf">
STI-GA Certificate Policy 1.4.2</a><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Delegate Certificates (<a href="https://datatracker.ietf.org/doc/html/rfc9060">RFC9060</a>/<a href="https://access.atis.org/higherlogic/ws/public/document?document_id=81651&wg_id=8ba10810-ca63-4d03-8155-018d2489bfb6">ATIS-1000092.v002</a>)
to sign enterprise calls for attestation uplift or for Rich Call Data authentication (<a href="https://access.atis.org/higherlogic/ws/public/document?document_id=81651&wg_id=8ba10810-ca63-4d03-8155-018d2489bfb6">ATIS-1000094.v002</a>) and Enhanced JWTClaimConstraints
(<a href="https://datatracker.ietf.org/doc/html/rfc9118">RFC9118</a>)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Use of ACME protocol (<a href="https://datatracker.ietf.org/doc/html/rfc8555">RFC8555</a>) and TNAuthList Authority Tokens (<a href="https://datatracker.ietf.org/doc/html/rfc9448">RFC9448</a>) otherwise known
as SPC tokens for Certificate Issuance via STI-CA<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Use of ACME protocol (<a href="https://datatracker.ietf.org/doc/html/rfc8555">RFC8555</a>) and TNAuthList Authority Tokens (<a href="https://datatracker.ietf.org/doc/html/rfc9448">RFC9448</a>) and JWTClaimConstraints
Authority Tokens (<a href="https://datatracker.ietf.org/doc/html/draft-wendt-acme-authority-token-jwtclaimcon-03">draft-wendt-acme-authority-token-jwtclaimcon-03</a>) for Delegate Certificate issuance via STI-SCA<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Use of the Vesper (<a href="https://datatracker.ietf.org/doc/html/draft-wendt-stir-vesper-05">draft-wendt-stir-vesper-05</a>) for establishing RTU and vetting framework for TNAuthList and JWTClaimConstraints
Authority tokens and Certificate Transparency (<a href="https://datatracker.ietf.org/doc/html/draft-wendt-stir-certificate-transparency-06">draft-wendt-stir-certificate-transparency-06</a>)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt">Message Authentication (<a href="https://datatracker.ietf.org/doc/html/rfc9475">RFC9475</a>)<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:12.0pt"> <o:p></o:p></span></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>