IETF Logo Mail Archive

Re: [dispatch] SASL Authentication for SIP

Eric Rescorla <ekr@rtfm.com> Tue, 18 October 2022 17:23 UTC

Return-Path: <ekr@rtfm.com>
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 99B6DC1524DB for <dispatch@ietfa.amsl.com>; Tue, 18 Oct 2022 10:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20210112.gappssmtp.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 9HOj-765PRXF for <dispatch@ietfa.amsl.com>; Tue, 18 Oct 2022 10:23:46 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 16F4DC1524BC for <dispatch@ietf.org>; Tue, 18 Oct 2022 10:23:46 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id o65so12340520iof.4 for <dispatch@ietf.org>; Tue, 18 Oct 2022 10:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=+GgDBtLWnWo3+KMowi0qusSBoN76FrOnzTG3Id3oxCs=; b=F/fAvI8TdH0VOJHdsHxgLSP2KQ8hL+GhkY8q4nWuep/yaVGd/KqMcSSHUORONCD18g B6pKuFznW8BWeci+J6+3h43w3KA1vqbT4rjy8TM1Ry8nZ3lVVLlw7efsEf00tA6hSL1N Z2QJy3JEopTY8nI1KApYl14nX+9rpSHu5b4oy0e7mmZ+bnBH+j8CLOr8qjBTZDr4nyEh rwL7LMar3ioTSv9w02q70UDwJibKC/7AL8BvjDqGSIrZn4o2R6xM5YSSK+B3nIpS0SH2 KqdGplNLgTwCVTerm/qvLkX98S0jaX1rwytjo8M7juPaQIHgF9H6XdjsEdOCiKETmD1o jGHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=+GgDBtLWnWo3+KMowi0qusSBoN76FrOnzTG3Id3oxCs=; b=uD1qrpYmRi15XhIr9bp9Mw1TvOZSjimvUBe9Jt0exjwxqDOyFcaJ8QsfMLtrFNPSWq kDwcNdsx+WeMkgr+wH7dhlkpV8RDBPjgZgybrhVyhFmkZww9A5hFrTW/v/g32rYK3kXs dedC1jbX3M1y4rnM1WYzzYzPrUwbOapxxZL7mC2gdQomhrH61UunqnFYZQXt2X1CWX97 T1wdenhUU4WhIR5Lvuc8X550auw6dtcE+r8LepEN6bZqHElFiv7N4UJw62UCZz8hUf0i dQEbOPzeN13qO3a7s0JRy0e5mKQjPQYCRP2ZoMfiOziDd8WMGth1sXMGCNP8+DFMqynD 4bIw==
X-Gm-Message-State: ACrzQf3EtxMHxBPpiI+IYpZ+0rbJTLlvlEoDD9bDNM+sxLM+nSt7Pgc7 snVz2vGSku0aLVgCk6/rDHQsddu6CqySzT3VKXZjgor0OFk=
X-Google-Smtp-Source: AMsMyM6jKZPGS7uaVjS93s8Ve2fq8l9PPj1Wncxn0JtZ5tMDOFn8DoQvr6mYvWRy7JssoLMRCTt+dpGczJ4vicKn3jg=
X-Received: by 2002:a05:6638:4689:b0:363:b7f4:1372 with SMTP id bq9-20020a056638468900b00363b7f41372mr2641742jab.137.1666113824769; Tue, 18 Oct 2022 10:23:44 -0700 (PDT)
MIME-Version: 1.0
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> <20221018165943.GA19985@openfortress.nl>
In-Reply-To: <20221018165943.GA19985@openfortress.nl>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 18 Oct 2022 10:23:08 -0700
Message-ID: <CABcZeBNe0M2yfq8tojBpLHHmP4TRMf-yscY=_zoXFpJA2=8Lbw@mail.gmail.com>
To: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000ae657b05eb525a3c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/LvmwcpfIZP0W2xtpreGJtnST7Zg>
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 17:23:50 -0000

On Tue, Oct 18, 2022 at 10:00 AM Rick van Rein <rick@openfortress.nl> wrote:

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

Yes. But if we had certificates for people with RFC 822-style names,
then it would slot in neatly. The problem is that we do not. But this
is not a problem that will be fixed by slotting in SASL.

-Ekr

v2.23.0 | Report a Bug | By Email