Re: [stir] I-D Action: draft-ietf-stir-certificates-17.txt

Sean Turner <sean@sn3rd.com> Thu, 14 December 2017 17:59 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 EF242126DFF for <stir@ietfa.amsl.com>; Thu, 14 Dec 2017 09:59:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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] 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 KGzhMBfIsoEU for <stir@ietfa.amsl.com>; Thu, 14 Dec 2017 09:59:07 -0800 (PST)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (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 8905A124BAC for <stir@ietf.org>; Thu, 14 Dec 2017 09:59:07 -0800 (PST)
Received: by mail-pf0-x234.google.com with SMTP id y89so4161921pfk.0 for <stir@ietf.org>; Thu, 14 Dec 2017 09:59:07 -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=CRaMswTRrguag7xDREMSeWuNvrbXY0BsJV8mpf6ZtTg=; b=kICS5qajfZanbFckNJIRUJFvY5o743WiIr9Drf/tcspQ22RQOwwfkhFibpXsDeLJNh h9c18rizWrNGe6KP7Yk61TkiLfc7WxKvVfXkIoKVNjHj1jpwjT6j8F4wkBdrDcKdbB3G gNh2IAmwn2BbX99PNtIFa7nRjiiawGJ4Udnfc=
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=CRaMswTRrguag7xDREMSeWuNvrbXY0BsJV8mpf6ZtTg=; b=dgtt2yWumEuWs31I6TzO3Au7XRu65bC4qhJj8DES4ZcQkZdUYP77QBabIETqrAAi1W 5PAD8qYmtrXUSQe+QLFHkNQz3Dn4+4P4eXKpMVLW4DBRVY3Q0OUcUxuw61NhtduMNUvu 30QREcJidV2u9ztDdm6kSDfsVQolKgpbkfnM/1hDHR8dqdm6AzZVuhZVJgUbbYGKA7rz Im03r2vhTOZCLORGG6jLbjAblO/ck3MtblBALSaZY3GBWUKywfmAaIEpx5prZz7cTkaU QFVH2KRq2grPC4WufMKKrOuHb0eDFc0MfQgxod2lo2+8LPCDAqkwZ0N9Ws3hPEKZoZ5t jSYg==
X-Gm-Message-State: AKGB3mKFtrLEDcqoMf5KL8Jeq+is/L5vBIeDEuhqLcc3HJXIGMttxD8l Ws59kIr5b6cFspYL502aAoXz9g==
X-Google-Smtp-Source: ACJfBouogpHs3fYF0M/ORNlL6q2TgJURZVTFyfToLHf1reJFVMrEHNby3g9ev65AXJbh+qdEAthFHw==
X-Received: by 10.98.95.68 with SMTP id t65mr10502529pfb.45.1513274347186; Thu, 14 Dec 2017 09:59:07 -0800 (PST)
Received: from [5.5.33.190] (vpn.snozzages.com. [204.42.252.17]) by smtp.gmail.com with ESMTPSA id j17sm7730933pgv.40.2017.12.14.09.59.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Dec 2017 09:59:06 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\))
From: Sean Turner <sean@sn3rd.com>
In-Reply-To: <CABkgnnXCizOyLkJzSR-MHo97O2feOiGXfOVFZeQPoNzj4m452g@mail.gmail.com>
Date: Thu, 14 Dec 2017 12:59:01 -0500
Cc: IETF STIR Mail List <stir@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <07AB7CB1-E5A2-45EE-B90E-B11E6A04C018@sn3rd.com>
References: <151326691971.6099.4107849780973461328@ietfa.amsl.com> <7E30739D-C21C-466E-8C3A-8395171C253D@sn3rd.com> <CABkgnnXCizOyLkJzSR-MHo97O2feOiGXfOVFZeQPoNzj4m452g@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
X-Mailer: Apple Mail (2.3445.5.20)
Archived-At: <https://mailarchive.ietf.org/arch/msg/stir/sOVoU8tgiIgiWPEFrGbdiHfFQQ8>
Subject: Re: [stir] I-D Action: draft-ietf-stir-certificates-17.txt
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: Thu, 14 Dec 2017 17:59:09 -0000

Bit to quick in my response, to address the 2nd point:

> On Dec 14, 2017, at 11:42, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> "123"+900 is now equivalent to "123"+876, which means that you have
> two ways to represent the same thing.  Don't we try to avoid that in
> certificates?  (I mean otherwise we'd use BER...)

As far encoding something the same way: I’d be worried if “123”+900 and “123”+876 resulted in the same DER code, but it doesn’t.

spt