IETF Logo Mail Archive

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

Bill Mills <wmills_92105@yahoo.com> Wed, 01 April 2015 22:19 UTC

Return-Path: <wmills_92105@yahoo.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 CD7BB1A87BF for <kitten@ietfa.amsl.com>; Wed, 1 Apr 2015 15:19:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.109
X-Spam-Level:
X-Spam-Status: No, score=-0.109 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 OmviWDijxnvO for <kitten@ietfa.amsl.com>; Wed, 1 Apr 2015 15:19:06 -0700 (PDT)
Received: from nm28.bullet.mail.bf1.yahoo.com (nm28.bullet.mail.bf1.yahoo.com [98.139.212.187]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8180C1A87A5 for <kitten@ietf.org>; Wed, 1 Apr 2015 15:19:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1427926745; bh=eNKnWWn/S2CLyjS1A2t09XjQBQKwyYjC2oUS3ivH1sg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=geh1HeEYu+5k19IBDpqXxZ3hJWdNcdHtg1BTXdHk+ffBn8MaHO/T2qJ3y3s98LXNOFW6iWND6Bo/z0gfEBx7VAcf30rvd0cZgCBOjz0TfdwrGktVgmBBLQl+waODYkkzKaCXExiDjy/ZhjK5kdg9NJ8y95T+9xNtqTiCeXyBrCZypVzYbMxAozsGp8QI722lXIt7XhgEeAhcmrWXwO/1xKOhXZGURIannXQd6fHvlG/4CIJxxCdqlSosNLi7AFTcjP/kISeI+E4AGyvWh+hqWwzmEkMm01y+/fkwN3AOuXaBENZMfEks2BhRuu/GzyXU6I1R9zozW1zr2Gx4e4Zi9w==
Received: from [98.139.215.140] by nm28.bullet.mail.bf1.yahoo.com with NNFMP; 01 Apr 2015 22:19:05 -0000
Received: from [98.139.212.197] by tm11.bullet.mail.bf1.yahoo.com with NNFMP; 01 Apr 2015 22:19:05 -0000
Received: from [127.0.0.1] by omp1006.mail.bf1.yahoo.com with NNFMP; 01 Apr 2015 22:19:05 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 735793.94850.bm@omp1006.mail.bf1.yahoo.com
X-YMail-OSG: uJShqSsVM1moWwTYEIqN7dlbXihTxqvfUdkaTSrJEPcDpG26u56y0Jj5gV4pRYL 6MQ2Q78utNS07KnWPwCPCDOxNd1oN5L9eEcnaCd7dWXb15gdiO_cSAtnytDBrGBkovUoB1ze.mFT kbdTs72w0L0nVmAT0Fcig.5Xpi8WvLV2Jzo0tNulJEqJ9ru2dYVboyGFa1oZyHbs5ez1z6YFyoOm Neb74dN.kYpNcubHx5mZ9p5EnqW2PoOAIEHHyQvRhD6YyKrnvwieTG6CUN2IiqgsobX6ri00Olbl _4JZk76W48pEv3bjoOwtEoMQ5wpS2o_pxUQyYJInjDdDtt8_zLMiA5jMZuLQU2JBgSa_7QSghcv. pGsMoTRyb57yYEFDpk0L.lnDnrLrONbbTiDjtTXnFylU4Rj1ueURyYD0Y7KKEsMBM_r.84jp024r ux47a6V5qRsyhxXYPps9Sy0tsqU.vh4qLaeAPU2L_6RRMBiCkv0zUV9Uf3ZdZVQj6qBCjBBb..Er rtBRsmFF2E0NE9ZiTzjgNRZ6MedBYa4z1dri8QTGTMXD9JjWcPp2sRj6Z8mljjOysogCJ8jN9V8u Yj2Pq5fcAjgi1
Received: by 66.196.80.117; Wed, 01 Apr 2015 22:19:05 +0000
Date: Wed, 01 Apr 2015 22:19:04 +0000
From: Bill Mills <wmills_92105@yahoo.com>
To: Nico Williams <nico@cryptonector.com>, Tom Yu <tlyu@mit.edu>
Message-ID: <202609050.3973897.1427926744182.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAK3OfOhNq57yQihKBvgb=Tt45=EN=vS5OcPbk6wz_kXpxWCGcg@mail.gmail.com>
References: <CAK3OfOhNq57yQihKBvgb=Tt45=EN=vS5OcPbk6wz_kXpxWCGcg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_3973896_1399659502.1427926744177"
Archived-At: <http://mailarchive.ietf.org/arch/msg/kitten/zRBeBmtIm5WJxqtwgNS3LZ9Wxvw>
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
Reply-To: Bill Mills <wmills_92105@yahoo.com>
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 22:19:08 -0000

Suggested changes updated to https://github.com/sweetums/idrafts
Still one open question on "I don't presently have an opinion on <hashname> vs. ah-<hashname>..." 


     On Wednesday, April 1, 2015 9:43 AM, Nico Williams <nico@cryptonector.com> wrote:
   

 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