Re: [radext] Stephen Farrell's Yes on draft-ietf-radext-dynamic-discovery-13: (with COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Fri, 10 April 2015 09:44 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: radext@ietfa.amsl.com
Delivered-To: radext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED8C1B2B23; Fri, 10 Apr 2015 02:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 AyHsgbavQLER; Fri, 10 Apr 2015 02:44:46 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1C481B2B20; Fri, 10 Apr 2015 02:44:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 00101BEFA; Fri, 10 Apr 2015 10:44:44 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X5lflelDto3G; Fri, 10 Apr 2015 10:44:43 +0100 (IST)
Received: from [10.87.48.73] (unknown [86.46.18.59]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9B8C3BECF; Fri, 10 Apr 2015 10:44:43 +0100 (IST)
Message-ID: <55279B88.6050903@cs.tcd.ie>
Date: Fri, 10 Apr 2015 10:44:40 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: Stefan Winter <stefan.winter@restena.lu>, The IESG <iesg@ietf.org>
References: <20150409130848.17585.83178.idtracker@ietfa.amsl.com> <55276ED9.9010606@restena.lu>
In-Reply-To: <55276ED9.9010606@restena.lu>
OpenPGP: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="Hj3mQGUNKGarRXQRvklE3eoe6rNvnx0Vu"
Archived-At: <http://mailarchive.ietf.org/arch/msg/radext/oz-Lyxe1p3Z5CwaKHcfd5ldhLhU>
Cc: radext@ietf.org, radext-chairs@ietf.org, jounikor@gmail.com
Subject: Re: [radext] Stephen Farrell's Yes on draft-ietf-radext-dynamic-discovery-13: (with COMMENT)
X-BeenThere: radext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: RADIUS EXTensions working group discussion list <radext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/radext>, <mailto:radext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/radext/>
List-Post: <mailto:radext@ietf.org>
List-Help: <mailto:radext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/radext>, <mailto:radext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Apr 2015 09:44:48 -0000


On 10/04/15 07:34, Stefan Winter wrote:
> It's a bit tricky: a RADIUS server typically has a DNS hostname (and
> that may want to/need to be placed in the cert for arbitrary reasons),
> and serves NAI realms on a RADIUS level - but the two are not
> necessarily identical.
> So there would be several sAN:DNS entries in the cert, one or more
> pertaining to the hostname, one or more pertaining to the NAI realms served.
> I guess a CA policy could "fix" that ambiguity by hard-wiring that the
> first sAN:DNS in its certs would semantically mean "the host" and any
> following ones would be "NAI realms served" but it doesn't strike me as
> a terribly clean solution.

Fair enough yeah - if there's other DNS names involved then
probably the otherName thing is best.

Cheers,
S.