IETF Logo Mail Archive

Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6

Ted Lemon <Ted.Lemon@nominum.com> Fri, 20 February 2015 02:23 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95ED01A1B6D for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 18:23:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 Y8SsPGrxdxAf for <dhcwg@ietfa.amsl.com>; Thu, 19 Feb 2015 18:23:50 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 444D81A1B6B for <dhcwg@ietf.org>; Thu, 19 Feb 2015 18:23:50 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 21111DA0153 for <dhcwg@ietf.org>; Fri, 20 Feb 2015 02:23:50 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DC57D53E07B; Thu, 19 Feb 2015 18:23:49 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Thu, 19 Feb 2015 18:23:50 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <201502192320.t1JNKpVY001185@givry.fdupont.fr>
Date: Thu, 19 Feb 2015 21:23:09 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <92978990-CA64-4B73-BED3-050042DAE95B@nominum.com>
References: <201502192320.t1JNKpVY001185@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/dhcwg/4z166hRguosgi3X5520drpWELkU>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, 神明達哉 <jinmei@wide.ad.jp>
Subject: Re: [dhcwg] on use case discussion for draft-ietf-dhc-sedhcpv6
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Feb 2015 02:23:51 -0000

On Feb 19, 2015, at 6:20 PM, Francis Dupont <Francis.Dupont@fdupont.fr> wrote:
> as far as I know the proposed client->server authentication uses
> (X.509 public key) certificates, and TOFU is only one of the possible
> options.

Right, but I think there is almost no chance that this would be deployed in practice, which was one of my objections to the proposal.   What value does it add to have a PKI-authenticated key on the client?

> => this can lead to a chicken and egg issue, in particular if someone
> adds privacy consideration. I suggest to target first easy cases, even
> they have little technical incentive...

What's the chicken/egg issue?   Do you mean because the server is allocating a scarce resource, and would want the client to authenticate first?

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