Re: [TLS] Proposed Change to Certificate message (#654)

Martin Thomson <martin.thomson@gmail.com> Thu, 06 October 2016 09:25 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: tls@ietfa.amsl.com
Delivered-To: tls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5452129927 for <tls@ietfa.amsl.com>; Thu, 6 Oct 2016 02:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 QODuL4wXHupV for <tls@ietfa.amsl.com>; Thu, 6 Oct 2016 02:25:50 -0700 (PDT)
Received: from mail-qt0-x230.google.com (mail-qt0-x230.google.com [IPv6:2607:f8b0:400d:c0d::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DEBF129933 for <TLS@ietf.org>; Thu, 6 Oct 2016 02:25:40 -0700 (PDT)
Received: by mail-qt0-x230.google.com with SMTP id f6so5437842qtd.2 for <TLS@ietf.org>; Thu, 06 Oct 2016 02:25:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=V2G5s2SwQ9QItGVMgkCw3NwNx3VSbsGuSK32Odrfr7A=; b=jGPnfXfj+B6za5D/ERqtbV7klt4ajhRKlKDHxLApHLDZxis3rt6aTP7zPHfp4rAc7G Cy24k5FPX5W0fUYDDmX8G/rvbt8XJw0HDtXL5aspFAfjelh6Ifz/Ai9HelPad1A75NGo q20SxLUfmeSruHRg5aQZx1kDB7kYDPIa4yNgeK1sX5haGek0nqaI6Uk4A9L+6PbLyHfl mcbQszgXJOKtHcEIK+BUaihGBVJdeJ/rL10ZMqP+aAh8eG+ypOY7crC2QCRJmFIKaHKh w7a8NuUQGwt+MXA1IM2AYHoALjNqGDHdIjglb2p4oKCkLPFa8DhUPs9NdEAhc4gEOj/u GwOw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=V2G5s2SwQ9QItGVMgkCw3NwNx3VSbsGuSK32Odrfr7A=; b=EYQUmon4LmuNDQGy2E/Sg9V3s71vv+vkVZvlwIrquOnvYz0RbhyZrIPU75vjMhbJAZ kx7SWyIhOeSJzUq6gVK7yqU5iOJZLdNJOZBqrGI7nRzDbCc/C4aalPkFATR1f//dsT0E Da8DyWiVs/ckcqxqRR4rHT2ki4MvODpSIG84KAMHhtrIW4YcWxsHCl/s1k5eZWWG0olr sO7galgJT/oDP7XaUNqSrOknHyRwvQvnZFLuZ/0J6tdNCD8087im2KjdDg78ye7rit2G Orf9ZTONRJB9W8QGYo/8Q34ghYzshWZ8/1XNSQaZOEIbrnZr5YXRfqc3rD+/E9YnV5QH /5aQ==
X-Gm-Message-State: AA6/9RlX1OeEB1f82Rk6738fNpKE0i9EmmdCn7BVvgSdchcAUBeIiWqUvP6DGGWiswVmYMJNJEndLYEIUnzA9Q==
X-Received: by 10.200.53.54 with SMTP id y51mr13737521qtb.132.1475745938287; Thu, 06 Oct 2016 02:25:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Thu, 6 Oct 2016 02:25:37 -0700 (PDT)
In-Reply-To: <20161006064220.GA30076@LK-Perkele-V2.elisa-laajakaista.fi>
References: <CAOjisRyDx0Wa5tcFT3gN496jhf-AjLfDH4JNN+w70r8jBsxt5g@mail.gmail.com> <F157C00C-921E-48AB-BAB7-C8CA882D1A05@sn3rd.com> <20161005194028.GA26154@LK-Perkele-V2.elisa-laajakaista.fi> <CABkgnnXsytcfEatQVaz=Yi_E=HvTJT9b-aPafvD5BSUeboCp4g@mail.gmail.com> <20161006064220.GA30076@LK-Perkele-V2.elisa-laajakaista.fi>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 6 Oct 2016 20:25:37 +1100
Message-ID: <CABkgnnVGLOJkSa49favLe7gAJTfYGWYF5_ZHVUpnpcFnsoxaow@mail.gmail.com>
To: Ilari Liusvaara <ilariliusvaara@welho.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls/oLIGLdG0AzaGkbwt3m9Vh17lz24>
Cc: "tls@ietf.org" <TLS@ietf.org>
Subject: Re: [TLS] Proposed Change to Certificate message (#654)
X-BeenThere: tls@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls>, <mailto:tls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls/>
List-Post: <mailto:tls@ietf.org>
List-Help: <mailto:tls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Oct 2016 09:25:52 -0000

On 6 October 2016 at 17:42, Ilari Liusvaara <ilariliusvaara@welho.com>; wrote:
> Perhaps also put server_certificate_type/client_certificate_type
> there? That would eliminate the anomaly that one must know the
> server certificate type before sending the certiifcate.


Sounds like a perfect use for the CertificateRequest extension field,
for the client certificate anyway.