IETF Logo Mail Archive

Re: [sipcore] Enabling the wildcard certificates for SIP TLS implementation

"Olle E. Johansson" <oej@edvina.net> Mon, 10 August 2020 08:03 UTC

Return-Path: <oej@edvina.net>
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 F107F3A0D01 for <sipcore@ietfa.amsl.com>; Mon, 10 Aug 2020 01:03:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jMVclhTk0rl2 for <sipcore@ietfa.amsl.com>; Mon, 10 Aug 2020 01:03:21 -0700 (PDT)
Received: from smtp7.webway.se (smtp7.webway.se [212.3.14.205]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D7273A0841 for <sipcore@ietf.org>; Mon, 10 Aug 2020 01:03:20 -0700 (PDT)
Received: from macbook-pro.webway.org (h-205-16.A165.corp.bahnhof.se [176.10.205.16]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp7.webway.se (Postfix) with ESMTPSA id 09DAC2172; Mon, 10 Aug 2020 10:03:17 +0200 (CEST)
From: "Olle E. Johansson" <oej@edvina.net>
Message-Id: <5BFABAC0-BCF4-4282-A457-F41BD3D142F2@edvina.net>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1DC88490-94AD-4444-9DC1-D5A8C6BB28DE"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Date: Mon, 10 Aug 2020 10:03:16 +0200
In-Reply-To: <CAJr_9Tau8iW7idbJLNhhKX5MA5PDhZxR0vmdcfva6_fMMBfKCA@mail.gmail.com>
Cc: Olle E Johansson <oej@edvina.net>, sipcore@ietf.org
To: Leonid Fainshtein <leonid.fainshtein@xorcom.com>
References: <CAJr_9Tau8iW7idbJLNhhKX5MA5PDhZxR0vmdcfva6_fMMBfKCA@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/xFCAyn2BJEaayC4MQhNOlh3lKsQ>
Subject: Re: [sipcore] Enabling the wildcard certificates for SIP TLS implementation
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Aug 2020 08:03:24 -0000


> On 6 Aug 2020, at 14:55, Leonid Fainshtein <leonid.fainshtein@xorcom.com> wrote:
> 
> Hi,
> The "7.2.  Comparing SIP Identities" of RFC-5922 prohibits the usage of wildcard certificates.
> The reasons for this limitation are not clear. The restriction only complicates the multi-home SIP servers configuration and maintenance. 
> I suggest enabling the wildcard certificates for SIP.

With wide-spread support for TLS SNI and free services like Letsencrypt I don’t really see a problem with not supporting wildcards.

On the other side, I do agree that the argumentation for this limitation is missing. I remember there was a widespread discussion
over multiple working groups about problems with wildcards. Let’s see if we can dig up something from other RFCs or if someone
has a clear argument.

/O

v2.23.0 | Report a Bug | By Email