IETF Logo Mail Archive

Re: [stir] Questions about stir-certificates

Sean Turner <sean@sn3rd.com> Sat, 11 November 2017 23:06 UTC

Return-Path: <sean@sn3rd.com>
X-Original-To: stir@ietfa.amsl.com
Delivered-To: stir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF5F8128B8E for <stir@ietfa.amsl.com>; Sat, 11 Nov 2017 15:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sn3rd.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 5UECu96VMiTh for <stir@ietfa.amsl.com>; Sat, 11 Nov 2017 15:06:29 -0800 (PST)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (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 86D1D1271DF for <stir@ietf.org>; Sat, 11 Nov 2017 15:06:29 -0800 (PST)
Received: by mail-pf0-x22c.google.com with SMTP id x7so9238979pfa.1 for <stir@ietf.org>; Sat, 11 Nov 2017 15:06:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=24nsqSZqHZ61LTjbvW7Q4I+rC3X5JWiDrlv2/jli2RE=; b=hANvvl4sF38Ad6OF4IwxTb3OOufizMYxpkwLOSraoCDEbs9KQ7WGGo5YUPwh2lByLB UdJUCG8FQjlIYpKMYrs5jYISOoN/TOP6qw+evaUrHWWBAtvAOQLNf37zVIGKEqhfrpnX M0q+qpIEsMpygMLlW0gfAG0Q0qIDCejykX7MM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=24nsqSZqHZ61LTjbvW7Q4I+rC3X5JWiDrlv2/jli2RE=; b=IfX9d3GW27phIfw3TOPk9WYHsXPl+dm7d5X6Us+g2hSvEiuw1FfZcIrRz3vUOwfH3H HGyjJEVIMWpFzwHJ2mpFbhmbDSSoDEKvvjlekXX9Xw7tOcIrZzWqGDCqk6whDRUyepJV e/szUclXYZsH6McC4zpFYHkFqQH4RkxpKQn57Oc3XzgGYtOsQIAuH2R0dMLRL79KBGL8 j4ASWB57OxvGda4Dey6zumxJXsnr8XAVTKLtjcVDUSjFApcac811RyU9hL6K09HaAAu5 r42i0vkXpoQ4eT/uGS55WujziFg2Kar1xKmk4Q8AFKApFilzQuAJz15i8bkyGBXljDeT ChMQ==
X-Gm-Message-State: AJaThX7nJSVW5wl5L+8YtrQMpCSWszlZ+Wxp9F8HS6k1NNuQhqzkHn21 j/Eyc5hrNzvkG8eovTkrFpVSmQ==
X-Google-Smtp-Source: AGs4zMZMho5F5UtDoVtVgjGmrMvZ4w3wMHsoTwZxQckEkc/SS2WRviepecLZabKPvb3JNfwUHL9fCw==
X-Received: by 10.99.167.12 with SMTP id d12mr4458512pgf.414.1510441589175; Sat, 11 Nov 2017 15:06:29 -0800 (PST)
Received: from [5.5.33.116] (vpn.snozzages.com. [204.42.252.17]) by smtp.gmail.com with ESMTPSA id r1sm2579317pfe.99.2017.11.11.15.06.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 11 Nov 2017 15:06:28 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CABkgnnWELeCBYUSOtado9FHjZEM6qj0GTYfrd6TYcDorYLZVwA@mail.gmail.com>
Date: Sun, 12 Nov 2017 07:06:22 +0800
Cc: "Peterson, Jon" <jon.peterson@team.neustar>, "stir@ietf.org" <stir@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <91DFEA38-6676-4931-A8D1-79292E396E00@sn3rd.com>
References: <D60E0087.1EEE44%jon.peterson@neustar.biz> <CABkgnnV41djmwJ2A8WkLv1Qu_zxAKPb8EJnuoFS1Zeog3momyQ@mail.gmail.com> <E4972898-9912-456F-92E5-1A6022B26A85@sn3rd.com> <CABkgnnUNmwT_-atKHzOATOJ4SPhsC1+Gy0Q_6XLtGo7owgE-kQ@mail.gmail.com> <5398BEAA-B532-4F4D-980C-43F6FB3584A8@sn3rd.com> <CABkgnnWELeCBYUSOtado9FHjZEM6qj0GTYfrd6TYcDorYLZVwA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/6DX_gFP4tQEQZLm_IlNnIXTFVPg>
Subject: Re: [stir] Questions about stir-certificates
X-BeenThere: stir@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Secure Telephone Identity Revisited <stir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/stir>, <mailto:stir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/stir/>
List-Post: <mailto:stir@ietf.org>
List-Help: <mailto:stir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/stir>, <mailto:stir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 11 Nov 2017 23:06:31 -0000

> On Nov 11, 2017, at 07:33, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> Only one comment (you got the rest).
> 
> On Fri, Nov 10, 2017 at 8:25 AM, Sean Turner <sean@sn3rd.com> wrote:
>>> Having the two match might not make sense if you consider the
>>> possibility for an operator to run their own subordinate CA.  I think
>>> that it would be reasonable for that CA to be constrained to the set
>>> of numbers that operator has, but if the EE cert has to match exactly
>>> it would prevent the operator from creating more narrowly constrained
>>> EE certs.
>> 
>> Ah here I wasn’t talking about the constraints themselves.  I was referring to the mechanism used, i.e., if the CA constrains with AIA the signer needs to also use an AIA, and vice versa.
> 
> The *same* AIA?

I was thinking that the subordinate could be further constrained.

spt

v2.23.0 | Report a Bug | By Email