Re: [stir] Publication has been requested for draft-ietf-stir-servprovider-oob-05

Ben Campbell <ben@nostrum.com> Sun, 17 March 2024 01:19 UTC

Return-Path: <ben@nostrum.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 1BB01C14F6AE for <stir@ietfa.amsl.com>; Sat, 16 Mar 2024 18:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.116
X-Spam-Level:
X-Spam-Status: No, score=0.116 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_DISCARD=1.8, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, KHOP_HELO_FCRDNS=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 1yCcuWKOLdDK for <stir@ietfa.amsl.com>; Sat, 16 Mar 2024 18:19:24 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 28489C14F5FA for <stir@ietf.org>; Sat, 16 Mar 2024 18:19:24 -0700 (PDT)
Received: from smtpclient.apple (dhcp-9066.meeting.ietf.org [31.133.144.102]) (authenticated bits=0) by nostrum.com (8.18.1/8.18.1) with ESMTPSA id 42H1JHHL050545 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Sat, 16 Mar 2024 20:19:19 -0500 (CDT) (envelope-from ben@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1710638361; bh=hcMNCxDOFZ8kp15zvIgiQgU8TbV9A26yXAGVeLNLBto=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=c41Wn554OF4UYoRtjv9PAI+cbAuYTMHPa8f3Oikp4hMTl1/W9rKePwbWJBqXvODvH OjizmF5G2/azfFkf6uoQwRn559/U//oUMTA1yobWkmB2uDcz7ovY7uuhUpbN9ezAAS rMyTEITFsTA/ybl4DxQW3N0tu83brCdGA6pEQBzQ=
X-Authentication-Warning: raven.nostrum.com: Host dhcp-9066.meeting.ietf.org [31.133.144.102] claimed to be smtpclient.apple
From: Ben Campbell <ben@nostrum.com>
Message-Id: <863E2FBF-73DC-4D52-B9B7-FD7AAEBFEEB8@nostrum.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_D8F6673B-D52A-40F3-BB17-877948C0DFA1"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Date: Sun, 17 Mar 2024 11:19:11 +1000
In-Reply-To: <CAL0qLwb40w9mNrPfigS_DW1dErj14g28fpRNORoXqkBUA7p8tA@mail.gmail.com>
Cc: Russ Housley <housley@vigilsec.com>, Richard Shockey <richard@shockey.us>, Pierce Gorman <Pierce.Gorman@numeracle.com>, IETF STIR Mail List <stir@ietf.org>
To: "Murray S. Kucherawy" <superuser@gmail.com>
References: <170689342892.43577.13483715713883494287@ietfa.amsl.com> <CAL0qLwb9LUsGuj4AwczOne9GCTT6NvuZJyZYPaeaZdRvaFGUzQ@mail.gmail.com> <97C689F5-C32D-4EAF-AC76-942CB3296341@shockey.us> <01E7796C-203A-4344-A656-EF85817B0E35@nostrum.com> <0D740856-CBE3-446F-B953-363DAC625558@shockey.us> <CH3PR13MB67474302850984AE2B8723C8E12B2@CH3PR13MB6747.namprd13.prod.outlook.com> <77BCC004-8794-4C24-99FE-3D34001DEF5E@shockey.us> <CH3PR13MB674769F00AFF5F6F58E44D7EE12A2@CH3PR13MB6747.namprd13.prod.outlook.com> <0D0ADAF6-967E-4D8B-BC78-450BC9733A8B@shockey.us> <CAL0qLwY-hCHP7k-tdrZg6icJ64CbL21btg-XsJkpBEvB9yRK+Q@mail.gmail.com> <3BE21F04-2FA6-4B4F-B625-93B4CF49CAA2@vigilsec.com> <CAL0qLwb40w9mNrPfigS_DW1dErj14g28fpRNORoXqkBUA7p8tA@mail.gmail.com>
X-Mailer: Apple Mail (2.3774.500.171.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/MSO2LoU-V9ZMQD9DflyniIgzB88>
Subject: Re: [stir] Publication has been requested for draft-ietf-stir-servprovider-oob-05
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 17 Mar 2024 01:19:28 -0000


> On Mar 17, 2024, at 10:55 AM, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
> On Sun, Mar 17, 2024 at 10:50 AM Russ Housley <housley@vigilsec.com <mailto:housley@vigilsec.com>> wrote:
>> 
>> 
>>> On Mar 16, 2024, at 8:47 PM, Murray S. Kucherawy <superuser@gmail.com <mailto:superuser@gmail.com>> wrote:
>>> 
>>> On Thu, Mar 14, 2024 at 8:48 AM Richard Shockey <richard@shockey.us <mailto:richard@shockey.us>> wrote:
>>>>  
>>>> OOB just sucks. I do not know one carrier that wants to implement it
>>>> 
>>> 
>>> The shepherd writeup for this document claims:
>>>    The shepherd is aware of multiple non-public implementation efforts, but
>>>    is not aware of any publicly available reports.
>>> Are these two claims in conflict?  If so, which is right?
>> 
>> I do not see a conflict.  People have said that they are doing implementations, but they are not sharing any details or interoperability reports.
> 
> Hi Russ,
> 
> So there are implementations, but none by carriers?  Or are you disagreeing with Richard's claim?

There are vendor implementations or plans for implementations. Carriers may or may not deploy them. I suspect Richard (who I hope will correct me if I am wrong) is referring to “major” or “top-tier carriers”, but the full set of STIR/SHAKEN stakeholders is considerably larger and more diverse than just the major carriers. There are certainly proponents for OOB solutions in the ATIS Non-IP Call Authentication group.

But in any case, I think the discussion has turned to politics and market forces, which are not really in scope for STIR. My opinion as chair is that the working group has _rough_ consensus to publish it. Certainly not perfect consensus.

Thanks!

Ben.