[sipcore] How to signal that a conversation is being recorded

Brian Rosen <br@brianrosen.net> Mon, 06 March 2023 22:51 UTC

Return-Path: <br@brianrosen.net>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B4FC152F11 for <sipcore@ietfa.amsl.com>; Mon, 6 Mar 2023 14:51:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.085
X-Spam-Level:
X-Spam-Status: No, score=-2.085 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=brianrosen.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DPOOGD8RPnBL for <sipcore@ietfa.amsl.com>; Mon, 6 Mar 2023 14:51:49 -0800 (PST)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 243BFC152F02 for <sipcore@ietf.org>; Mon, 6 Mar 2023 14:51:49 -0800 (PST)
Received: by mail-il1-x12f.google.com with SMTP id y9so6350122ill.3 for <sipcore@ietf.org>; Mon, 06 Mar 2023 14:51:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen.net; s=google; t=1678143107; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=ijMyQVclbNZJ6dSaXkbKhfj5lCAnHAm2wkReXn7Fwyg=; b=gjiKmzewZ4/DUqPNmvmyZ3vntqvAPyQWFHYoS379SVaEci0C33hAZBAm66qvuXX3ic JIe3hGItnOOXL4Xe/SS6PYjaGbgTdmCIa1P2RyeEIX7ueFd7UzdDuOE+2ZzPJ7OzUEbE QdO3c5APqxOcvQNhcncOrL3QYvu1ujP9RtUVY=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678143107; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ijMyQVclbNZJ6dSaXkbKhfj5lCAnHAm2wkReXn7Fwyg=; b=bQUGbxyxUDUtjsxrXceyucfCl4taQ310fAIxS6GnihJfsrEs2CM7XsaMYONb/DR1NB xKqxOWTc4NN/6OWTTvQR0CB0qk6J8OD6BknDxrQ0bIQUVG4VTP0a2qVk66+YhQnJidno hIOifLsCfdNp+pD+mFcijLAQbtddMktLt2Ga6V4i80mqP8pQowRjXQInnYG286kBH8bI 2OK2T/842V/gfg0yGNR7gOFzq5jW0Tex2fkFVL1pXwitgx01l55mH4bYIcL9dKNVE2W+ qFZlaGCDNb2U8WLNt+Qb6U9vjJnKS3ls+ZaEZ8c1XyjappaeGPwZ8KvZXg9uQcU64PuN C98g==
X-Gm-Message-State: AO0yUKWk5qCeeuUsXwABryHxyPmyXlHRiwA2tmgA2EwPrrIAMEnwJpZn SMFUHKd8umLB4oyk4647QVeXtsIQOEE55NcQM2Q=
X-Google-Smtp-Source: AK7set9abdym0+eCIRTfwR4IgE+FRly+BAfOyCRB/aruN4c2wn+UTeGipiVRiOztNiJx/pZOYjDrcg==
X-Received: by 2002:a92:d40d:0:b0:316:67be:1b99 with SMTP id q13-20020a92d40d000000b0031667be1b99mr650417ilm.0.1678143107583; Mon, 06 Mar 2023 14:51:47 -0800 (PST)
Received: from smtpclient.apple (dynamic-acs-24-154-121-237.zoominternet.net. [24.154.121.237]) by smtp.gmail.com with ESMTPSA id s23-20020a02c517000000b003f1929b34f2sm3633166jam.68.2023.03.06.14.51.46 for <sipcore@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Mar 2023 14:51:47 -0800 (PST)
From: Brian Rosen <br@brianrosen.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.300.101.1.3\))
Message-Id: <082A7485-5C3C-4356-88A8-6A333A07D60D@brianrosen.net>
Date: Mon, 06 Mar 2023 17:51:35 -0500
To: sipcore@ietf.org
X-Mailer: Apple Mail (2.3731.300.101.1.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/M7_hp9jmVwMbsmxRIog_7yUx7zE>
Subject: [sipcore] How to signal that a conversation is being recorded
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Mar 2023 22:51:53 -0000

Many are familiar with a requirement to insert an audible indication of a voice call being recorded, and in some circumstances, visible indication of a video recording.   SIPREC provides the recording mechanism, and it’s possible for the SIPREC client to insert the indications.  This doesn’t work very well in applications like emergency services, where recording often happens in multiple places.  We don’t want multiple media insertions.  The usual SIP way to do things like this is to pass the indication as data in signaling, and render the audio/video/whatever locally.

Suppose we wanted to do that: we would need to pass to all endpoints (think conference) the information that the session was being recorded.

Does that make sense?

What would you suggest we use to carry that indication?

Brian