IETF Logo Mail Archive

Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014

Francis Dupont <Francis.Dupont@fdupont.fr> Mon, 03 November 2014 23:26 UTC

Return-Path: <Francis.Dupont@fdupont.fr>
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 CF3B11A8878 for <dhcwg@ietfa.amsl.com>; Mon, 3 Nov 2014 15:26:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.146
X-Spam-Level:
X-Spam-Status: No, score=-2.146 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_FR=0.35, RP_MATCHES_RCVD=-0.594, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 stgaYsMrapqP for <dhcwg@ietfa.amsl.com>; Mon, 3 Nov 2014 15:26:39 -0800 (PST)
Received: from givry.fdupont.fr (givry.fdupont.fr [IPv6:2001:41d0:1:6d55:211:5bff:fe98:d51e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 389DD1A8851 for <dhcwg@ietf.org>; Mon, 3 Nov 2014 15:26:39 -0800 (PST)
Received: from givry.fdupont.fr (localhost [127.0.0.1]) by givry.fdupont.fr (8.14.3/8.14.3) with ESMTP id sA3NQVjh049671; Tue, 4 Nov 2014 00:26:31 +0100 (CET) (envelope-from dupont@givry.fdupont.fr)
Message-Id: <201411032326.sA3NQVjh049671@givry.fdupont.fr>
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
In-reply-to: Your message of Sun, 02 Nov 2014 21:32:42 GMT. <2134F8430051B64F815C691A62D9831832D7700C@XCH-BLV-504.nw.nos.boeing.com>
Date: Tue, 04 Nov 2014 00:26:31 +0100
Sender: Francis.Dupont@fdupont.fr
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/JD2KGlfobiBZZPctqRKHtLzWq1M
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-sedhcpv6-04 - Respond by Nov 3, 2014
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: Mon, 03 Nov 2014 23:26:41 -0000

 In your previous mail you wrote:

>  OK, I object to the removal of the client's ability to sign its
>  messages with its own private key (i.e., so that the server can
>  verify the signature using the client's public key). Let's talk
>  about it at IETF91.

=> the certificate wording in the draft requires some improvements but
a client can sign its messages with its own private key (the server can
verify the signature using the client's public key certificate).

Regards

Francis.Dupont@fdupont.fr

v2.23.0 | Report a Bug | By Email