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

Roman Shpount <roman@telurix.com> Tue, 13 July 2021 16:19 UTC

Return-Path: <roman@telurix.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 5BDC93A1A22 for <stir@ietfa.amsl.com>; Tue, 13 Jul 2021 09:19:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=telurix.com
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 X2X8cLD6UrQG for <stir@ietfa.amsl.com>; Tue, 13 Jul 2021 09:19:35 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B7AC3A1A5C for <stir@ietf.org>; Tue, 13 Jul 2021 09:19:35 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id d15so5750050qte.13 for <stir@ietf.org>; Tue, 13 Jul 2021 09:19:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telurix.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sqTk2DIX1Ex5wMNSW6TNSlQ+C5h4SFXqDULXaLunTRk=; b=IrHqVW51lNZsCTuZ+5ZNNN8OMaBSXcneTj45lP5cLz9rRMnytesisLWQGOBMzCcZgd GKw5UEdNiCXghhuj8inEQsVBxSPPvP7MrAdNsavluyf3oXR8gmkBIO+s2xBh/NZbVLtf NyhRP/su+ctmR5L+AlV1TQseLSXVoDc0UFYgs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sqTk2DIX1Ex5wMNSW6TNSlQ+C5h4SFXqDULXaLunTRk=; b=gt1L0iMUrAnQxWbMjFR3lkNINuK8UZ70siDIAA+TicmIkDwtJJDVk+WJfGYF5Jut/S OEh+inRxUruAHBxzJmiZezFT5lzTdZwH8GY7+5150q1+lTHC4KfSOXA/b/HhhsGkL4X5 jclVeehKa6CL12Jdoq0Pl1yqxnqqNeCRN7NxMRJjV7EzF7rY6Mv0AC7Dif16CqNiD8G4 9fmFwEVhK92/IUbLvF2vjJ3z2E3Qd84yhY+7OUso3zDGrkCJQHmml8ikhVkLPweqfZAH vd8T2gyHZD+Li7eao4MPCjW58D3VTrHRg7wllwTtxBwOhOAFBtblo108iyU2/WSFt913 Mjaw==
X-Gm-Message-State: AOAM533+1napTrEt+MCf/Cb19kKPf1FCcxUb6ESI272IBVl922X2Mz67 i/I1LlDQQz7cKCcxnrFc8IfB0CUtEtfb5Q==
X-Google-Smtp-Source: ABdhPJxX8soEx5pF0y2SzafQm48AQHq07cZ5Wse5wq1VGmL++u0YeqLjqTHtjKxrOGiZNXHcCIZoFg==
X-Received: by 2002:aed:3161:: with SMTP id 88mr3066576qtg.368.1626193173430; Tue, 13 Jul 2021 09:19:33 -0700 (PDT)
Received: from mail-yb1-f171.google.com (mail-yb1-f171.google.com. [209.85.219.171]) by smtp.gmail.com with ESMTPSA id u184sm8081399qkd.53.2021.07.13.09.19.32 for <stir@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 13 Jul 2021 09:19:32 -0700 (PDT)
Received: by mail-yb1-f171.google.com with SMTP id a16so35702248ybt.8 for <stir@ietf.org>; Tue, 13 Jul 2021 09:19:32 -0700 (PDT)
X-Received: by 2002:a25:10d4:: with SMTP id 203mr6858181ybq.454.1626193171989; Tue, 13 Jul 2021 09:19:31 -0700 (PDT)
MIME-Version: 1.0
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> <520D5CDF-0CC3-42DB-93A4-2A1BAE129928@vigilsec.com>
In-Reply-To: <520D5CDF-0CC3-42DB-93A4-2A1BAE129928@vigilsec.com>
From: Roman Shpount <roman@telurix.com>
Date: Tue, 13 Jul 2021 12:19:20 -0400
X-Gmail-Original-Message-ID: <CAD5OKxvqmjLBB9opmrj6Lqh0-XcN+bFG8G7Z7cmKqHQGQBcYXg@mail.gmail.com>
Message-ID: <CAD5OKxvqmjLBB9opmrj6Lqh0-XcN+bFG8G7Z7cmKqHQGQBcYXg@mail.gmail.com>
To: Russ Housley <housley@vigilsec.com>
Cc: "Olle E. Johansson" <oej@edvina.net>, IETF STIR Mail List <stir@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005a49b805c7039aec"
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/HVjTbHC8Bznh79D5cmu2gilsSNs>
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:19:40 -0000

SIPCORE is definitely a better place for discussing TLS related issues, but
it was dead quiet for a long time.

What is definitely on topic in STIR is getting the report on RFC
implementation status and organizing an interop event for Identity
implementations. This, most likely, will result in a set of issues that
should be addressed in SIPCORE. The need to implement and deploy STIR might
provide the required energy in SIPCORE to addresses the existing issues.

Best,
_____________
Roman Shpount


On Tue, Jul 13, 2021 at 12:07 PM Russ Housley <housley@vigilsec.com> wrote:

> 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> 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
>
>
>