IETF Logo Mail Archive

Re: [dispatch] SASL Authentication for SIP

Rick van Rein <rick@openfortress.nl> Tue, 18 October 2022 16:59 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 ED5AFC1524C3 for <dispatch@ietfa.amsl.com>; Tue, 18 Oct 2022 09:59:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 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, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_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 u0CSEeBV0Kp8 for <dispatch@ietfa.amsl.com>; Tue, 18 Oct 2022 09:59:48 -0700 (PDT)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.169]) (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 03095C1524B4 for <dispatch@ietf.org>; Tue, 18 Oct 2022 09:59:46 -0700 (PDT)
X-KPN-MessageId: 432a1140-4f06-11ed-823a-005056abad63
Received: from smtp.kpnmail.nl (unknown [10.31.155.38]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 432a1140-4f06-11ed-823a-005056abad63; Tue, 18 Oct 2022 18:59:43 +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=zED7c6Bcq/GZxtpT+L4AYmUc7mhEgIDhJ86tnIzSHsc=; b=tcmHboRhQH1+ODjm2T8QjkB5rDta3pTnxJdm/j79uL/OnVro4vnbhOE5Mk5HF7hTkYw7A5eHN1NDr DvKyscBz/s15snl091Ak7VV+aIVwX/irUeusTP+OGJwcgE4l0S3bq5eRsJGIu0q5qhmK477c0mzeEG pYAgjFPYbu19W2Ps=
X-KPN-MID: 33|U0g9x4uE8EU2dHkHszzy6jGg9IDoj2x2GDb9QZeSx2lUSPYY3d8DTo99yqXPkUy j03XUMqzhU9PzwQJWMWVZCFJPPICuA4BUrCRcni8LiRc=
X-KPN-VerifiedSender: No
X-CMASSUN: 33|jxLUgU1xPAV9DANTNzNntBsN1YcGHWzHAnb9iFOyncaL84jJaywOmy5LAYmLu4f HYQuNFNK7mme+gfxA9bCxKA==
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 4333a5d4-4f06-11ed-b5e8-005056abf0db; Tue, 18 Oct 2022 18:59:43 +0200 (CEST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id 4AD302A0A1; Tue, 18 Oct 2022 16:59:43 +0000 (UTC)
Date: Tue, 18 Oct 2022 16:59:43 +0000
From: Rick van Rein <rick@openfortress.nl>
To: dispatch@ietf.org
Message-ID: <20221018165943.GA19985@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> <20221017075149.GB15330@openfortress.nl> <CABcZeBP0d=NovvnrjMqmMbW+r=vBMuv51KBS3L4WK-S5QsPgGw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <CABcZeBP0d=NovvnrjMqmMbW+r=vBMuv51KBS3L4WK-S5QsPgGw@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/7m80dgDfhtLsak57XYMWv2rtXTk>
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: Tue, 18 Oct 2022 16:59:55 -0000

Hi Eric,

> The general assumption has been that any end-to-end authentication
> will be done by digitally signing the SIP messages. Probably the most
> plausible at the moment is to base it on STIR/Passport. It's not
> clear to me why SASL would help here.

STIF/PASSporT only handles phone numbers.

Certificate signing could also be used, but for crossover between hitherto
unknown domains that pretty much requires (for maximum leniency on the
client account side) a Client DANE registration for a domain CA, or a TTP
that signs every users and each and every alias they might think of.

-Rick

v2.46.0 | Report a Bug | By Email | System Status