IETF Logo Mail Archive

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

worley@ariadne.com Wed, 04 March 2026 20:39 UTC

Return-Path: <dale.worley@comcast.net>
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 0C919C467FC5 for <sipcore@mail2.ietf.org>; Wed, 4 Mar 2026 12:39:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 ATp8UXpJ1Cr8 for <sipcore@mail2.ietf.org>; Wed, 4 Mar 2026 12:39:20 -0800 (PST)
Received: from resqmta-h2p-567354.sys.comcast.net (resqmta-h2p-567354.sys.comcast.net [IPv6:2001:558:fd02:2446::5]) (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 ED659C467FB3 for <sipcore@ietf.org>; Wed, 4 Mar 2026 12:39:19 -0800 (PST)
Received: from resomta-h2p-555359.sys.comcast.net ([96.102.179.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resqmta-h2p-567354.sys.comcast.net with ESMTPS id xkhzvz7BXjZuOxszwv5K4x; Wed, 04 Mar 2026 20:39:12 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1772656752; bh=o4WV/Q61IS5rKCJxfYexi2tJF+HH8Ud5PklwoJ5UDsg=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=FvvHel/NhJCQci+H+TPnt7Q2U/GoacImRZzsWaF8qlte/YgSbvD90RRjzs+oJSqAU rn0bPUhcNXWrV7fQNQK9ZBHgA9139JC8ObJoEPd5tc0VRNuXIqXChF3Av60Xvyg6Av aHTaG0qRjzZxFuWS7A+PR3POiz3ITrBJuRVWFHhCH0xWM+LdNQRdM9Fpc86WtbXCzo jJT1U8zw3S++zmbZq7fvMcBAdxJNDmvvZADerWcvSwPU6iakRV83BDuAZzWMF1KF/D Lg03JbAPvWborPnZwEVDRAonsCKUa3xdwVnTlWkMZhcOn1C0pDDQ3lADow1Y0kffGb yqo43xuBGAb4w==
Received: from hobgoblin.ariadne.com ([75.69.170.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 256/256 bits) (Client did not present a certificate) by resomta-h2p-555359.sys.comcast.net with ESMTPSA id xsztvovbsGwTmxszvv4pcc; Wed, 04 Mar 2026 20:39:12 +0000
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 624Kd9nD2968183 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 4 Mar 2026 15:39:09 -0500
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 624Kd8fq2968172; Wed, 4 Mar 2026 15:39:09 -0500
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to Dale.Worley@comcast.net using -f
From: worley@ariadne.com
To: Nicola Serafini <n.serafini=40tutanota.com@dmarc.ietf.org>
In-Reply-To: <Omprx6X--F-9@tutanota.com> (n.serafini=40tutanota.com@dmarc.ietf.org)
Sender: worley@ariadne.com
Date: Wed, 04 Mar 2026 15:39:08 -0500
Message-ID: <874imvl47n.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4xfOvavHmnA4AApzDPKV0z6cOH1rP0/o0Mm7Jx4pF0T/D39/Sq+tG2zsdcy0OM3Z+FYMZVtCE8HDM6AEigTvKOWjmS/+ZFWyIzhPkyXk5SAZMIN01JSCej qGJhIhxxyL7JwflRyikSiN1dV+RD1+TUK+G0X8qUN/vSA7RLvhQZp2XEeyhYhnZZ8Fyh32K32PeaXxIVa/0ib2d2fCw564XkbMYJZuan5js+e105i6nsD+ME sXxccKylkJKvQ4a6yWL2yg==
Message-ID-Hash: MGERHC76SDQEJXQBVGSOK7XPACZYNRNL
X-Message-ID-Hash: MGERHC76SDQEJXQBVGSOK7XPACZYNRNL
X-MailFrom: dale.worley@comcast.net
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
CC: sipcore@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [sipcore] Re: 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/V6iTmyjlulgjcYbXCskSrYKDtGY>
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>

It seems to me that a lot of these requirements are requirements on
various SIP UAs, proxies, etc., so the problem isn't so much a matter of
designing the mechanism within the SIP protocol itself as cataloging all
of the requirements on all of the SIP devices to support it.

At least one aspect of this need can be satisfied within current SIP:
When a UA wishes to transfer a dialog to another UA, it can send a REFER
in the dialog with

    Refer-to:  ...destination...?AI-Session-ID=...identifier...

Then the UA to which the dialog is transferred will see a header
"AI-Session-ID: ...identifier...".

Dale

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