IETF Logo Mail Archive

[sipcore] Request for comments on draft-nser-sip-ai-problem-statement-00

Nicola Serafini <n.serafini@tutanota.com> Tue, 03 March 2026 22:45 UTC

Return-Path: <n.serafini@tutanota.com>
X-Original-To: sipcore@mail2.ietf.org
Delivered-To: sipcore@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 0E5EEC3C4490 for <sipcore@mail2.ietf.org>; Tue, 3 Mar 2026 14:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=tutanota.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PDmY6nzVTZnm for <sipcore@mail2.ietf.org>; Tue, 3 Mar 2026 14:45:07 -0800 (PST)
Received: from mail.w13.tutanota.de (mail.w13.tutanota.de [185.205.69.213]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 91608C3C448B for <sipcore@ietf.org>; Tue, 3 Mar 2026 14:45:07 -0800 (PST)
Received: from tutadb.w10.tutanota.de (w10.api.tuta.com [IPv6:fd:ac::d:10]) by mail.w13.tutanota.de (Postfix) with ESMTP id 8CB3011674B71 for <sipcore@ietf.org>; Tue, 3 Mar 2026 23:44:30 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1772577870; s=s1; d=tutanota.com; h=From:From:To:To:Subject:Subject:Content-Description:Content-ID:Content-Type:Content-Type:Content-Transfer-Encoding:Content-Transfer-Encoding:Cc:Date:Date:In-Reply-To:MIME-Version:MIME-Version:Message-ID:Message-ID:Reply-To:References:References:Sender; bh=me5ZzSU0EOrzX8AP8Fi6D/QK191fe7tNKajh6HrLX/4=; b=hiR3Exh6F3gh9Jlra1Gvm8+e72e60C6l6sfxyWy/4JVAkyZCbSawFQg9J4O3C7zE t23hBCMC+HrmSMe7L1Mh3zgFl+poOOtKRg1MjFlZSO2JLP6lqcI+g5+9e77/Nxhpjce iUM1axeuLK3dMuVTQN2yP/bDgi+A4k2fzwS++lo6pUqjOvwy9WU6yGGcdUhaJ3ZgCE+ KhT5qLGAg+gaTGPQNnjMvaMnhwvZemvZI5UEJERj6gSmtohyTRX2q2gFkMe9MpAauPZ Wjgm7Y1yQzy44j45W8UyAFKYiJmhvOji8gBO8eiRxbyJ4qJ0XWQNi+NYeZhVFYPasI9 bsMa4v2/9g==
Date: Tue, 03 Mar 2026 23:44:30 +0100
From: Nicola Serafini <n.serafini@tutanota.com>
To: Sipcore <sipcore@ietf.org>
Message-ID: <Omprx6X--F-9@tutanota.com>
References: <177205203012.2479425.356531315854799393@dt-datatracker-6ff7c68975-7k42g>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Feedback-ID: 013d28c49b4575172df5708f1f2be020249852fe44184143387ed937645a30d5961dd1f8dbe3ff36129eacddb837c2e7144a86c21d24e93296fc5f64892f9d228f:TurnOnPrivacy!:tutamail
Message-ID-Hash: GXQGD6QFWN4D76R23ZHIGTNL7X4WKHCK
X-Message-ID-Hash: GXQGD6QFWN4D76R23ZHIGTNL7X4WKHCK
X-MailFrom: n.serafini@tutanota.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-sipcore.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [sipcore] Request for comments on draft-nser-sip-ai-problem-statement-00
List-Id: SIP Core Working Group <sipcore.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/gJzb_9jMZiul-_wyguAW-b2GvcE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Owner: <mailto:sipcore-owner@ietf.org>
List-Post: <mailto:sipcore@ietf.org>
List-Subscribe: <mailto:sipcore-join@ietf.org>
List-Unsubscribe: <mailto:sipcore-leave@ietf.org>

Dear WG, we prepared a brief document and would like to share this early-stage problem statement that amis to identify a signaling-layer correlation gap in SIP-based real-time AI voice systems.

At this stage, our goal is to validate the problem space, scope, and relevance before further refining the proposal.

We would greatly appreciate any comments, suggestions, or guidance from the working group.


Thanks and regards,

--
Nicola



Date: Feb 25, 2026, 21:40
From: internet-drafts@ietf.org
To: n.serafini@tutanota.com
Subject: New Version Notification for draft-nser-sip-ai-problem-statement-00.txt


> A new version of Internet-Draft draft-nser-sip-ai-problem-statement-00.txt has
> been successfully submitted by Nicola Serafini and posted to the
> IETF repository.
>
> Name:     draft-nser-sip-ai-problem-statement
> Revision: 00
> Title:    Problem Statement for an AI-Session-ID in SIP
> Date:     2026-02-24
> Group:    Individual Submission
> Pages:    8
> URL:      https://www.ietf.org/archive/id/draft-nser-sip-ai-problem-statement-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-nser-sip-ai-problem-statement/
> HTML:     https://www.ietf.org/archive/id/draft-nser-sip-ai-problem-statement-00.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-nser-sip-ai-problem-statement
>
>
> Abstract:
>
>  This document describes a signaling-layer correlation gap in SIP-
>  based real-time AI voice systems.  Existing SIP identifiers provide
>  dialog and communication-session scope, but they do not define a
>  stable application-layer identifier capable of persisting across
>  topology changes, multi-dialog call control operations, federated
>  interconnects, or distributed processing environments.
>
>  The document analyzes current mechanisms and their limitations, and
>  motivates the need for a standardized SIP-carried identifier whose
>  semantics are restricted to application-layer correlation and out-of-
>  band context retrieval.
>
>
>
> The IETF Secretariat
>
>

v2.46.0 | Report a Bug | By Email | System Status