[sipnoc25-attendees] BOF proposal: SIPit interoperability event topics

[Chris Wendt]

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.

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.

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.

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.

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.

Thanks to everyone that made it to the BOF!


From: Chris Wendt <cwendt at somos.com>
Date: Tuesday, September 16, 2025 at 12:32 PM
To: sipnoc25-attendees at sipforum.org <sipnoc25-attendees at sipforum.org>
Subject: BOF proposal: SIPit interoperability event topics
Hi All,

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.

Thanks!

-Chris

Potential topics to discuss:

Rich Call Data PASSporTs (RFC9795<https://datatracker.ietf.org/doc/html/rfc9795>) usage: within PASSporTs and identity headers, other usages OOB etc.
Rich Call Data Call-Info Usage (RFC9796<https://datatracker.ietf.org/doc/html/rfc9796>) usage for UNI interfaces to devices

Certificate compliance to specifications and certificate policies: RFC8226<https://datatracker.ietf.org/doc/html/rfc8226>/RFC9116/ATIS-1000080.v005<https://access.atis.org/apps/group_public/download.php/69428/ATIS-1000080.v005.pdf>/ATIS-1000084.v003<https://access.atis.org/higherlogic/ws/public/download/70989/ATIS-1000084.v003.pdf> and STI-GA Certificate Policy 1.4.2<https://authenticate.iconectiv.com/sites/authenticate/files/2025-02/CP_v1.4.2.pdf>

Delegate Certificates (RFC9060<https://datatracker.ietf.org/doc/html/rfc9060>/ATIS-1000092.v002<https://access.atis.org/higherlogic/ws/public/document?document_id=81651&wg_id=8ba10810-ca63-4d03-8155-018d2489bfb6>) to sign enterprise calls for attestation uplift or for Rich Call Data authentication (ATIS-1000094.v002<https://access.atis.org/higherlogic/ws/public/document?document_id=81651&wg_id=8ba10810-ca63-4d03-8155-018d2489bfb6>) and Enhanced JWTClaimConstraints (RFC9118<https://datatracker.ietf.org/doc/html/rfc9118>)

Use of ACME protocol (RFC8555<https://datatracker.ietf.org/doc/html/rfc8555>) and TNAuthList Authority Tokens (RFC9448<https://datatracker.ietf.org/doc/html/rfc9448>) otherwise known as SPC tokens for Certificate Issuance via STI-CA

Use of ACME protocol (RFC8555<https://datatracker.ietf.org/doc/html/rfc8555>) and TNAuthList Authority Tokens (RFC9448<https://datatracker.ietf.org/doc/html/rfc9448>) and JWTClaimConstraints Authority Tokens (draft-wendt-acme-authority-token-jwtclaimcon-03<https://datatracker.ietf.org/doc/html/draft-wendt-acme-authority-token-jwtclaimcon-03>) for Delegate Certificate issuance via STI-SCA

Use of the Vesper (draft-wendt-stir-vesper-05<https://datatracker.ietf.org/doc/html/draft-wendt-stir-vesper-05>) for establishing RTU and vetting framework for TNAuthList and JWTClaimConstraints Authority tokens and Certificate Transparency (draft-wendt-stir-certificate-transparency-06<https://datatracker.ietf.org/doc/html/draft-wendt-stir-certificate-transparency-06>)

Message Authentication (RFC9475<https://datatracker.ietf.org/doc/html/rfc9475>)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.sipforum.org/pipermail/sipnoc25-attendees/attachments/20250917/45e1f93b/attachment-0001.html>