IETF Logo Mail Archive

Re: [kitten] draft-ietf-krb-wg-pkinit-alg-agility-07 Re: now that I've volunteered....

Nico Williams <nico@cryptonector.com> Wed, 01 April 2015 16:43 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34DC71AD0BA for <kitten@ietfa.amsl.com>; Wed, 1 Apr 2015 09:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.044
X-Spam-Level:
X-Spam-Status: No, score=-1.044 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 zP3sos8x102N for <kitten@ietfa.amsl.com>; Wed, 1 Apr 2015 09:43:47 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 93FD91AD289 for <kitten@ietf.org>; Wed, 1 Apr 2015 09:43:05 -0700 (PDT)
Received: from homiemail-a84.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTP id 12CDE1DE094 for <kitten@ietf.org>; Wed, 1 Apr 2015 09:43:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=HUGS1uWQKb+bfZ52AKdL viUbHzg=; b=Q3Xz0K3THwwI0zsFWyVS3HsFKOIf5tVydLcpoo4fjyGaoCjPxe/Z Zxkj+FZjIEdHvdybNYLTKSRU7LoamfXuLLr66d6As7ZXPXjmTypL4fui7xvbKxkt 7E1RnozilULEvj5Vom8OzZYMB7uiplvRqR6LPn8/hQEhUYCkDX+y1J8=
Received: from mail-ie0-f178.google.com (mail-ie0-f178.google.com [209.85.223.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a84.g.dreamhost.com (Postfix) with ESMTPSA id C596E1DE058 for <kitten@ietf.org>; Wed, 1 Apr 2015 09:43:02 -0700 (PDT)
Received: by iedfl3 with SMTP id fl3so53877145ied.1 for <kitten@ietf.org>; Wed, 01 Apr 2015 09:43:00 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.107.164.69 with SMTP id n66mr65031638ioe.82.1427906580816; Wed, 01 Apr 2015 09:43:00 -0700 (PDT)
Received: by 10.64.130.66 with HTTP; Wed, 1 Apr 2015 09:43:00 -0700 (PDT)
In-Reply-To: <ldvy4mcq0rw.fsf@sarnath.mit.edu>
References: <alpine.GSO.1.10.1411192205490.19231@multics.mit.edu> <962591069.3713128.1427479391512.JavaMail.yahoo@mail.yahoo.com> <ldv1tkatgzr.fsf@sarnath.mit.edu> <ldva8ysrgri.fsf@sarnath.mit.edu> <CAK3OfOj8q+90XQuCNcdqesteLCpEaVsE46-jbmnr+an_cxM68A@mail.gmail.com> <ldvy4mcq0rw.fsf@sarnath.mit.edu>
Date: Wed, 01 Apr 2015 11:43:00 -0500
Message-ID: <CAK3OfOhNq57yQihKBvgb=Tt45=EN=vS5OcPbk6wz_kXpxWCGcg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tom Yu <tlyu@mit.edu>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/KNxnhwhLHlfvd0la49QLB8-XBC0>
Cc: Kitten WG <kitten@ietf.org>
Subject: Re: [kitten] draft-ietf-krb-wg-pkinit-alg-agility-07 Re: now that I've volunteered....
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten/>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Apr 2015 16:43:48 -0000

On Tue, Mar 31, 2015 at 5:07 PM, Tom Yu <tlyu@mit.edu> wrote:
> Nico Williams <nico@cryptonector.com> writes:
>> On Tue, Mar 31, 2015 at 4:36 PM, Tom Yu <tlyu@mit.edu> wrote:
>>> We can debate whether the component identifiers for the KDF OIDs should
>>> be just <hashname> or ah-<hashname>.
>>
>> I don't think that would be a breaking change, though in general OID
>> naming changes could be.  The safe way to do this would be to leave
>> compatibility values behind:
>>
>> id-pkinit-kdf-sha384 OBJECT IDENTIFIER ::= id-pkinit-kdf-ah-sha384
>>
>> But I don't care.
>
> I was intending to indicate, e.g., { id-pkinit-kdf sha384(4) } vs
> { id-pkinit-kdf ah-sha384(4) } , not the reference identifiers for the
> entire OIDs (id-pkinit-kdf-ah-sha384 vs id-pkinit-kdf-sha384).

What's the difference?  But I don't care anyways.  It's just a
non-breaking symbol change.

v2.23.0 | Report a Bug | By Email