Re: [kitten] RFC 5742 review of draft-hotz-kx509

Nico Williams <nico@cryptonector.com> Wed, 06 June 2012 18:08 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1F2421F87DF for <kitten@ietfa.amsl.com>; Wed, 6 Jun 2012 11:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.262
X-Spam-Level:
X-Spam-Status: No, score=-2.262 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OW+CwxSIlaL for <kitten@ietfa.amsl.com>; Wed, 6 Jun 2012 11:08:19 -0700 (PDT)
Received: from homiemail-a98.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id 88F7B21F877A for <kitten@ietf.org>; Wed, 6 Jun 2012 11:08:19 -0700 (PDT)
Received: from homiemail-a98.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTP id 008D82C20E5 for <kitten@ietf.org>; Wed, 6 Jun 2012 11:02:50 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a98.g.dreamhost.com (Postfix) with ESMTPSA id 1EAF82C2174 for <kitten@ietf.org>; Wed, 6 Jun 2012 10:45:32 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9172603pbc.31 for <kitten@ietf.org>; Wed, 06 Jun 2012 10:45:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.224.233 with SMTP id rf9mr14709905pbc.141.1339004730693; Wed, 06 Jun 2012 10:45:30 -0700 (PDT)
Received: by 10.68.15.134 with HTTP; Wed, 6 Jun 2012 10:45:30 -0700 (PDT)
In-Reply-To: <4FCF90FD.2050809@cs.tcd.ie>
References: <4FC6AEDA.4010709@cs.tcd.ie> <4FCF3F47.10205@cs.tcd.ie> <BD0411A9-F243-46EB-B318-3A0994A17559@jpl.nasa.gov> <4FCF90FD.2050809@cs.tcd.ie>
Date: Wed, 06 Jun 2012 12:45:30 -0500
Message-ID: <CAK3OfOiKcgHjb8mO2kH62fFaR640un669tQ0D_xGLTUp5CJ7Lw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: kitten@ietf.org, draft-hotz-kx509@tools.ietf.org, "Henry B. Hotz" <hotz@jpl.nasa.gov>, Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: [kitten] RFC 5742 review of draft-hotz-kx509
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
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, 06 Jun 2012 18:08:20 -0000

On Wed, Jun 6, 2012 at 12:18 PM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
> On 06/06/2012 06:11 PM, Henry B. Hotz wrote:
>> Your comment about the underscore is interesting.  Since we're documenting an existing protocol, the underscore is what it is.  Should we resolve the issue by requesting an exception, or by deleting the request for an addition to the registry?
>
> I don't even know what requesting an exception might mean for
> an IANA registry to be honest. It sounds like a bunch of work
> for someone in any case;-)

My guess is that when the IANA looks at this I-D on the RFC-Editor
queue they'll point this out, at which point the author(s) will point
out the need for an exception, which IANA should probably take to
require comment/consensus from KITTEN WG, which surely will be easy to
obtain.

> If you're ok with leaving it out, I suspect that might be the
> easier option all right.
>
> I suppose you could register without the illegal character
> and note in the text that current deployments use "_" and
> not "-" in the name but I'm not sure that'd be useful.

I'd rather the registry reflect reality :/  Let's try that first.

Nico
--