Re: [sipcore] SASL Authentication for SIP
Rick van Rein <rick@openfortress.nl> Fri, 14 October 2022 17:33 UTC
Return-Path: <vanrein@vanrein.org>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AFA0C1524CC for <sipcore@ietfa.amsl.com>; Fri, 14 Oct 2022 10:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.646
X-Spam-Level:
X-Spam-Status: No, score=-6.646 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, 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 fmthso3MhnY1 for <sipcore@ietfa.amsl.com>; Fri, 14 Oct 2022 10:33:14 -0700 (PDT)
Received: from ewsoutbound.kpnmail.nl (ewsoutbound.kpnmail.nl [195.121.94.170]) (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 7B719C1524C9 for <sipcore@ietf.org>; Fri, 14 Oct 2022 10:33:10 -0700 (PDT)
X-KPN-MessageId: 4047a024-4be6-11ed-8a67-005056ab378f
Received: from smtp.kpnmail.nl (unknown [10.31.155.40]) by ewsoutbound.so.kpn.org (Halon) with ESMTPS id 4047a024-4be6-11ed-8a67-005056ab378f; Fri, 14 Oct 2022 19:33:01 +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=v0EE6HUUdQz0qmPAg9wW4xx100I2eBiOeTnSlHQkOa8=; b=r83KJWgYNWPKZxxMTZvuYWE6F/mEruc9oRGSqWFWENktZSflgsVZsiDvcE0Seend97P4t+E5XECM1 eG0qPer0HGMn153mLRlbS4m7Jb8w9byG51l9HoQ2gfzzMR0Ww2+mqikVlVXd2kCRbJ3QV5ND+DA7am s15zoWwBOdpakEok=
X-KPN-MID: 33|60yYhrszUi3xJk9gx19TzLVYtkSTiN3w7zlHFLAj+GpK1K1oZH9j7chfBVQHChE zlUITVxh4gzKR0gmPClFxbWhgo8Ei31Hbs1o7RXdlypw=
X-KPN-VerifiedSender: No
X-CMASSUN: 33|6LmqtQg/Mz7wn2HxRA5Cpvwcc73BvU8zzz1cboauNEcB4OhbM8OU4xuCDv56nYZ 210TP0G3wd1zbHLcXTGHvkQ==
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 44979936-4be6-11ed-9eb8-005056ab7584; Fri, 14 Oct 2022 19:33:08 +0200 (CEST)
Received: by fame.vanrein.org (Postfix, from userid 1000) id 4E6EC29BB9; Fri, 14 Oct 2022 17:33:08 +0000 (UTC)
Date: Fri, 14 Oct 2022 17:33:08 +0000
From: Rick van Rein <rick@openfortress.nl>
To: sipcore@ietf.org
Message-ID: <20221014173308.GA8165@openfortress.nl>
References: <20221014162340.GA7844@openfortress.nl> <69DDB655-0B52-4D14-A67A-54EC9A7D7DFE@brianrosen.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <69DDB655-0B52-4D14-A67A-54EC9A7D7DFE@brianrosen.net>
User-Agent: Mutt/1.5.20 (2009-06-14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/PC_Fbocmig8BeBzrTF6BvHeSap8>
Subject: Re: [sipcore] SASL Authentication for SIP
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Oct 2022 17:33:20 -0000
Hello Brian / SIPcore, Thanks for responding. > Are you planning on requesting dispatch for your document? Not sure what you mean by "requesting dispatch", but... ...I would like to have this considered as a formal extension to SIP. Through our work in draft-vanrein-diameter-sasl, it enables authenticated calls between domain names. ...this is early work, and has not been implemented yet. The underlying HTTP-SASL work has already shown to work really well. -Rick
- [sipcore] SASL Authentication for SIP Rick van Rein
- Re: [sipcore] SASL Authentication for SIP Brian Rosen
- Re: [sipcore] SASL Authentication for SIP Rick van Rein
- Re: [sipcore] SASL Authentication for SIP Brian Rosen
- Re: [sipcore] SASL Authentication for SIP Rick van Rein
- Re: [sipcore] SASL Authentication for SIP Olle E. Johansson
- Re: [sipcore] SASL Authentication for SIP Rick van Rein
- Re: [sipcore] SASL Authentication for SIP Olle E. Johansson