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

[Chris Wendt]

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/20250916/d2aae292/attachment.html>