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

Russ Housley <housley@vigilsec.com> Tue, 13 July 2021 16:07 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D84E3A1A00 for <stir@ietfa.amsl.com>; Tue, 13 Jul 2021 09:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 kriHO2Pp_U1Z for <stir@ietfa.amsl.com>; Tue, 13 Jul 2021 09:07:35 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7646F3A19FE for <stir@ietf.org>; Tue, 13 Jul 2021 09:07:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id CED60300232 for <stir@ietf.org>; Tue, 13 Jul 2021 12:07:34 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id v3ZrIArpSSR6 for <stir@ietf.org>; Tue, 13 Jul 2021 12:07:28 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 86383300C04; Tue, 13 Jul 2021 12:07:28 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <520D5CDF-0CC3-42DB-93A4-2A1BAE129928@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F55D8D7C-748D-4403-9289-6028E8CA6DE0"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Tue, 13 Jul 2021 12:07:27 -0400
In-Reply-To: <CAD5OKxuW5PCQQHT7nYrrD6zJuuppPYhUTqyw5q-_rKdKYKaMLw@mail.gmail.com>
Cc: IETF STIR Mail List <stir@ietf.org>
To: Roman Shpount <roman@telurix.com>, "Olle E. Johansson" <oej@edvina.net>
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> <357B6EDB-C403-4539-B760-F76118F3E7B5@edvina.net> <CAD5OKxuW5PCQQHT7nYrrD6zJuuppPYhUTqyw5q-_rKdKYKaMLw@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/8nolr7NvCLdaVa59tK4WIoHwzDs>
Subject: Re: [stir] [Acme] NYTimes.com: How Do You Stop Robocalls?
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Jul 2021 16:07:41 -0000

These are interesting topics, but the are relly off topic for STIR.  Is SIPCORE a better place for this discussion?

> On Jul 13, 2021, at 11:35 AM, Roman Shpount <roman@telurix.com> wrote:
> 
> On Tue, Jul 13, 2021 at 3:11 AM Olle E. Johansson <oej@edvina.net <mailto:oej@edvina.net>> wrote:
> 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.
> 
> 
> The areas I wanted to investigate were:
> 1. Handling TLS connection failure at all stages of an INVITE transaction. Design a test suite for proxies and SBC to test this behavior.
> 2. Support for multiple bidirectional TLS connections between two SIP endpoints or two clusters of SIP endpoints
> 3. Dealing with slow proxy thread or slow proxy in the cluster when processing SIP transactions
> 4. Best practices for high-performance TLS connections between proxies, including connection reuse, connection resumption, cipher suites, etc
> 5. Look at SIP-over-QUIC as a next-generation secure SIP transport
> 
> Best Regards,
> _____________
> Roman Shpount
>  
> _______________________________________________
> stir mailing list
> stir@ietf.org
> https://www.ietf.org/mailman/listinfo/stir