Re: [dispatch] SASL Authentication for SIP

Rick van Rein <rick@openfortress.nl> Mon, 17 October 2022 07:52 UTC

Return-Path: <vanrein@vanrein.org>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84C29C14CE36 for <dispatch@ietfa.amsl.com>; Mon, 17 Oct 2022 00:52:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.647
X-Spam-Level:
X-Spam-Status: No, score=-6.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, T_SPF_TEMPERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=kpnmail.nl
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 j8dYzK6Q5BWz for <dispatch@ietfa.amsl.com>; Mon, 17 Oct 2022 00:52:01 -0700 (PDT)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.168]) (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 D7D3BC14CF1F for <dispatch@ietf.org>; Mon, 17 Oct 2022 00:51:52 -0700 (PDT)
X-KPN-MessageId: 8deba591-4df0-11ed-be70-005056aba152
Received: from smtp.kpnmail.nl (unknown [10.31.155.38]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 8deba591-4df0-11ed-be70-005056aba152; Mon, 17 Oct 2022 09:51:48 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kpnmail.nl; s=kpnmail01; h=content-type:mime-version:message-id:subject:to:from:date; bh=YCSf5lgN48oXFJ0QYMhrV1jm/CCX6RTPrTzvQyDAf/g=; b=KRvvJS2UZ7ymr80vaFBG3i0u26tfYZjvZo25DbZ5hqYil7pEXIM2Oo3mUFWtlM7Nf/R0O4CQYHwr2 oLqvkNkiL61xFoEtb7k+C5m31rEal/s2Ro9u5YodZd1NW+RswPtsHKo77Q1X04F5xwPJBs8ENgP2pG cwQ26m0wZnLwkhV4=
X-KPN-MID: 33|G6a0hWZMduXMpVX6s9ris2+gc34WoN1km4gcMRCWuAqubkTe522btLi8eA4Bm7s QNrU2R5yPvn9QqZblOuCMRi3i/flI1kFw5hQ4l25h/uE=
X-KPN-VerifiedSender: No
X-CMASSUN: 33|BFutzlpJk+tvaiK2igzsOIqqmeMQhGRhvUFXiGB1MTnEIBPtCYoZQH9qsXuKWgC ul7iBy5Mr7Gwzitnfi+zDLg==
X-Originating-IP: 77.173.183.203
Received: from fame.vanrein.org (77-173-183-203.fixed.kpn.net [77.173.183.203]) by smtp.xs4all.nl (Halon) with ESMTPSA id 8e9f79be-4df0-11ed-b5e8-005056abf0db; Mon, 17 Oct 2022 09:51:50 +0200 (CEST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id 8852929E8B; Mon, 17 Oct 2022 07:51:49 +0000 (UTC)
Date: Mon, 17 Oct 2022 07:51:49 +0000
From: Rick van Rein <rick@openfortress.nl>
To: dispatch@ietf.org
Message-ID: <20221017075149.GB15330@openfortress.nl>
Mail-Followup-To: dispatch@ietf.org
References: <20221015195315.GA11346@openfortress.nl> <CABcZeBMHshP_C36+E7UPXfPoug87RAu6faw4EMkQ=qWdCeZzuA@mail.gmail.com> <20221016065327.GA12615@openfortress.nl> <CABcZeBOgiisAm+k=m4tSor-brTeaN5Y22HOz=JBTckcGZt0h9A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABcZeBOgiisAm+k=m4tSor-brTeaN5Y22HOz=JBTckcGZt0h9A@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/5cAGqLGQ20XDk8_qAiBd-DSW9eI>
Subject: Re: [dispatch] SASL Authentication for SIP
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Oct 2022 07:52:08 -0000

Hello,

> I'm not really following this. Users authenticate to domains with passwords
> (at least sometimes) but I would expect inter-domain authentication to be
> done with TLS mutual auth.

Ah, yes.  TLS is transport protection, usually between the proxies of
a domain.  It does not allow end-to-end authentication between the
parties.  Also, any encryption or key derivation that might be based on
the end-to-end assurance is lost for the end points.  (The proxy may be
operated by an external party.)

> Also, my sense is that authentication is not the primary barrier to
> inter-domain calling.

Of course there are more issues; IPv4/IPv6, MTU, and probably more.

> More or less. It's hard to see the IETF doing successful work in this space
> if providers aren't interested.

This is reasonable, but it does yield a catch-22 situation.  Can you
explain how this is commonly resolved?

I can see how a very large vendor would simply push their ideas out,
and not all technical ideas should be standardised.  OTOH, there is a
need to have standards before adoption can occur.

Since I have no implementation, I pull back the proposal, but please
give some guidance what to do before filing with Dispatch again.

-Rick