IETF Logo Mail Archive

Re: [Acme] [stir] NYTimes.com: How Do You Stop Robocalls?

"Olle E. Johansson" <oej@edvina.net> Tue, 13 July 2021 07:11 UTC

Return-Path: <oej@edvina.net>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74B393A1ACF; Tue, 13 Jul 2021 00:11:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vf8MjuSGc_ts; Tue, 13 Jul 2021 00:11:07 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [IPv6:2a02:920:212e::205]) (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 761333A1ACC; Tue, 13 Jul 2021 00:11:02 -0700 (PDT)
Received: from smtpclient.apple (h-176-10-205-16.A165.corp.bahnhof.se [176.10.205.16]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp7.webway.se (Postfix) with ESMTPSA id DD15C1900; Tue, 13 Jul 2021 09:10:59 +0200 (CEST)
From: "Olle E. Johansson" <oej@edvina.net>
Message-Id: <357B6EDB-C403-4539-B760-F76118F3E7B5@edvina.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A2FC50DD-500D-4F8F-93B7-E1FAA8CDE4FF"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Tue, 13 Jul 2021 09:10:59 +0200
In-Reply-To: <CAD5OKxvYMERn9++0-igHxCLf5=DwPGH7E-T+OzH1NNiGZp0tHA@mail.gmail.com>
Cc: Mary Barnes <mary.ietf.barnes@gmail.com>, "stir@ietf.org" <stir@ietf.org>, "acme@ietf.org" <acme@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
To: Roman Shpount <roman@telurix.com>
References: <B0BBFDFA-4203-4660-A982-80A5B8DED746@contoso.com> <CAHBDyN57-8-ctw8L-5ob_ti2azBwEGqyEApGVSMwJgNM68Uscw@mail.gmail.com> <CAD5OKxsy3xODy2mXHJcKB=ihwdOeLLYiLaDpORa4B33j7TUuhw@mail.gmail.com> <FDA56FC9-ADDD-4A5C-8624-3F0CC822E230@edvina.net> <CAD5OKxvYMERn9++0-igHxCLf5=DwPGH7E-T+OzH1NNiGZp0tHA@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/CEegSnsa6hArHAv_ne5CbWADdno>
Subject: Re: [Acme] [stir] NYTimes.com: How Do You Stop Robocalls?
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2021 07:11:13 -0000


> On 13 Jul 2021, at 09:06, Roman Shpount <roman@telurix.com> wrote:
> 
> On Tue, Jul 13, 2021 at 2:33 AM Olle E. Johansson <oej@edvina.net <mailto:oej@edvina.net>> wrote:
>> 13 juli 2021 kl. 06:58 skrev Roman Shpount <roman@telurix.com <mailto:roman@telurix.com>>:
>> 
>>  At the same time, SIP over TLS has many performance and reliability issues that would need to be addressed before it is ready for industry-wide deployment.
> 
> There’s also a lack of applicable standards for TLS usage, as I’ve pointed out a few times, but the working group seems to have no energy to fix. SIP over TLS from the SIP phone side requires implementation of SIP outbound, which we never successfully tested at any SIPit. I know of a few implementations now, but haven’t tested them together.
> 
> We have built a SIP Outbound implementation with TLS. It kind of works but helped us identify plenty of problems both from reliability and scalability points of view.
> 
> In the meantime, I am more concerned with more and more PII being sent in SIP INVITE, especially with RCD. It might be legally required to encrypt it when sending such data over the public internet, which would require TLS or VPN connections for all service providers. Together with increased SIP INVITE size, TLS essentially becomes the requirement. At this point, I am more concerned with making service provider to service provider use cases working.

I would love to have a discussion on that - either on the sipcore list or somewhere else. I gave a lot of input to the SIPconnect update but there’s still a lot of work to do on the server2server case.

/O

v2.23.0 | Report a Bug | By Email