Re: [sipcore] How to signal that a conversation is being recorded
Paul Kyzivat <paul.kyzivat@comcast.net> Tue, 07 March 2023 03:08 UTC
Return-Path: <paul.kyzivat@comcast.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 B7C01C14F747 for <sipcore@ietfa.amsl.com>; Mon, 6 Mar 2023 19:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.798
X-Spam-Level:
X-Spam-Status: No, score=-2.798 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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 (2048-bit key) header.d=comcast.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 YRpYlcnrnXb3 for <sipcore@ietfa.amsl.com>; Mon, 6 Mar 2023 19:08:16 -0800 (PST)
Received: from resqmta-a1p-077720.sys.comcast.net (resqmta-a1p-077720.sys.comcast.net [96.103.146.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8AABC14F738 for <sipcore@ietf.org>; Mon, 6 Mar 2023 19:08:15 -0800 (PST)
Received: from resomta-a1p-077050.sys.comcast.net ([96.103.145.228]) by resqmta-a1p-077720.sys.comcast.net with ESMTP id ZNH4pfayFvty5ZNeXp40BS; Tue, 07 Mar 2023 03:06:13 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1678158373; bh=M+MlRrkt0rutakt3Ti47mc+FtSOC66h/rZtRj9PQrxM=; h=Received:Received:Message-ID:Date:MIME-Version:Subject:To:From: Content-Type:Xfinity-Spam-Result; b=FGMbcXlKneGaElce/D8/+EjuVOmPS0Dz36O+xSTrzGpNCxTdR5AbgDVwfYbqLHaVp nUtxwE8wGCI7R3oYoHzVO6LDRXimKxUHnVN5KLZ3kjWeNylcFAo8SE/WXZh74MzzgN iwbNkLNk+0sEC2v6KWH1NxIDm3HcX6vkxrkB/mv2+Xs5+vQTg7rCz843CpZJuYGOeq 9Ccs3xvBTTBgyjcz3XNAuJuegB6Ya9gMMcTbkCvpfAgmFIiVRRW9vKTG6qz5etYnhO VFdn4pEU1e/kJjzosVfgllmUU9JALqUQsjExgd/N1+YpRnE2Chk+g6il0zqbvVpMlh cm8N4CtmdQRLQ==
Received: from [192.168.1.52] ([73.143.251.114]) by resomta-a1p-077050.sys.comcast.net with ESMTPA id ZNeBpCH7NI85kZNeBp7uPo; Tue, 07 Mar 2023 03:05:52 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvhedrvddtledgheegucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedtudenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrrghulhcumfihiihivhgrthcuoehprghulhdrkhihiihivhgrthestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepjeeiueegleelteehtdeluefgieelveelfeffjeeftedtgfffjedvveetteekffefnecuffhomhgrihhnpehivghtfhdrohhrghenucfkphepjeefrddugeefrddvhedurdduudegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghloheplgduledvrdduieekrddurdehvdgnpdhinhgvthepjeefrddugeefrddvhedurdduudegpdhmrghilhhfrhhomhepphgruhhlrdhkhiiiihhvrghtsegtohhmtggrshhtrdhnvghtpdhnsggprhgtphhtthhopedupdhrtghpthhtohepshhiphgtohhrvgesihgvthhfrdhorhhg
X-Xfinity-VMeta: sc=0.00;st=legit
Message-ID: <25cd2876-3536-c494-f1fd-152ed0013751@comcast.net>
Date: Mon, 06 Mar 2023 22:05:51 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.8.0
Content-Language: en-US
To: sipcore@ietf.org
References: <082A7485-5C3C-4356-88A8-6A333A07D60D@brianrosen.net>
From: Paul Kyzivat <paul.kyzivat@comcast.net>
In-Reply-To: <082A7485-5C3C-4356-88A8-6A333A07D60D@brianrosen.net>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/H4jECmljhpnu08lio-Mr7BCQZrw>
Subject: Re: [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: Tue, 07 Mar 2023 03:08:19 -0000
Brian, Are there legal constraints here? I presume that the party doing the recording has a legal obligation to ensure an indication makes it to the other participants that are being recorded. OTOH there may be others in the call that might wish to suppress the indication, to one or more of the participants. If the indication is in the signaling, then everybody in the signaling path has an opportunity to meddle with the indication. That is potentially also true if the indication is in the media. But it may at least be a lot harder to do. I have no recommendation yet, just exploring. Thanks, Paul On 3/6/23 5:51 PM, Brian Rosen wrote: > 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 > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore
- [sipcore] How to signal that a conversation is be… Brian Rosen
- Re: [sipcore] How to signal that a conversation i… Paul Kyzivat
- Re: [sipcore] How to signal that a conversation i… Brian Rosen
- Re: [sipcore] How to signal that a conversation i… worley
- Re: [sipcore] How to signal that a conversation i… Brian Rosen
- Re: [sipcore] How to signal that a conversation i… Paul Kyzivat
- Re: [sipcore] How to signal that a conversation i… Ranjit Avasarala (Nokia)
- Re: [sipcore] How to signal that a conversation i… Brian Rosen
- Re: [sipcore] How to signal that a conversation i… Ranjit Avasarala (Nokia)
- Re: [sipcore] How to signal that a conversation i… Robert Sparks
- Re: [sipcore] How to signal that a conversation i… Ranjit Avasarala
- Re: [sipcore] How to signal that a conversation i… Brian Rosen