Re: [kitten] Is id-pkinit-san misnamed? Can it be reused by kca?

Jeffrey Hutzelman <jhutz@cmu.edu> Thu, 05 December 2013 21:17 UTC

Return-Path: <jhutz@cmu.edu>
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 AA7D51AE180 for <kitten@ietfa.amsl.com>; Thu, 5 Dec 2013 13:17:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] autolearn=ham
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 VlvB1c02d8np for <kitten@ietfa.amsl.com>; Thu, 5 Dec 2013 13:17:51 -0800 (PST)
Received: from smtp01.srv.cs.cmu.edu (smtp01.srv.cs.cmu.edu [128.2.217.200]) by ietfa.amsl.com (Postfix) with ESMTP id A7C1B1AE149 for <kitten@ietf.org>; Thu, 5 Dec 2013 13:17:51 -0800 (PST)
Received: from [128.2.193.239] (minbar.fac.cs.cmu.edu [128.2.193.239]) (authenticated bits=0) by smtp01.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id rB5LHivK008821 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Thu, 5 Dec 2013 16:17:45 -0500 (EST)
Message-ID: <1386278264.9407.142.camel@minbar.fac.cs.cmu.edu>
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nico Williams <nico@cryptonector.com>
Date: Thu, 05 Dec 2013 16:17:44 -0500
In-Reply-To: <20131205205812.GB21240@localhost>
References: <24661_1386227942_rB57J0KZ025231_20131205071852.GO21240@localhost> <1386276313.9407.139.camel@minbar.fac.cs.cmu.edu> <20131205205004.GA21240@localhost> <20131205205812.GB21240@localhost>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.2.3-0ubuntu6
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0
X-Scanned-By: mimedefang-cmuscs on 128.2.217.200
Cc: kitten@ietf.org, jhutz@cmu.edu
Subject: Re: [kitten] Is id-pkinit-san misnamed? Can it be reused by kca?
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: Thu, 05 Dec 2013 21:17:53 -0000

On Thu, 2013-12-05 at 14:58 -0600, Nico Williams wrote:
> On Thu, Dec 05, 2013 at 02:50:07PM -0600, Nico Williams wrote:
> > Thanks.  Should we file an erratum against RFC4556 to rename it?
> 
> Just did.

No, that's not merely editorial; it's the name of an identifier in what
is effectively a published interface.  Even though it doesn't affect
anything on the wire, it does affect things that import the ASN.1
module, so a name change would be backward-incompatible.  I think we're
better off leaving it alone and just clarifying that it's intended use
is more general than just PKINIT.

-- Jeff