[kitten] PKCROSS

Nico Williams <nico@cryptonector.com> Thu, 11 July 2013 21:40 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 8247F11E812F for <kitten@ietfa.amsl.com>; Thu, 11 Jul 2013 14:40:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.042
X-Spam-Level:
X-Spam-Status: No, score=-2.042 tagged_above=-999 required=5 tests=[AWL=-0.065, 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 CN5Gifxx8LpG for <kitten@ietfa.amsl.com>; Thu, 11 Jul 2013 14:40:04 -0700 (PDT)
Received: from homiemail-a71.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id 9469011E818E for <kitten@ietf.org>; Thu, 11 Jul 2013 14:40:04 -0700 (PDT)
Received: from homiemail-a71.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a71.g.dreamhost.com (Postfix) with ESMTP id 2723942807A for <kitten@ietf.org>; Thu, 11 Jul 2013 14:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:date:message-id:subject:from:to:content-type; s= cryptonector.com; bh=M3yU8G9jE/tZ+8UwYGGKO9RteBI=; b=iwRsRrWtl5W JmxpX+Wy97cwx/0qeFrxhXZibNFDAkFyb60DnFvnDAc3lhvSse3huNS8rBY0rUi5 eKY1v2kau9uWJGLGW3cXcI/sUMpTAtU+fV3Vk95/ncq2r8jo0614iICCHVDqmCDn Uqd+tBxQ0LUR3LBWDTjwc47Nm8ThOeWI=
Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a71.g.dreamhost.com (Postfix) with ESMTPSA id B002A428079 for <kitten@ietf.org>; Thu, 11 Jul 2013 14:40:03 -0700 (PDT)
Received: by mail-we0-f176.google.com with SMTP id t56so7351927wes.21 for <kitten@ietf.org>; Thu, 11 Jul 2013 14:40:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=w7uUcfWFfQRFgT6X77p7fnK9RkpMwmcXQrYfymuFTvM=; b=Je0VJ8wdJRDzGOk9sVzjAF77xiktG32YzP5mO2e2VlA9kYpNCAa6/C2gAt6vdftcZt wSgDWkRBxCc1XR8BqC4MX7w3i0en4dnlMkHr/ZimjLoGYcf5sHfF/xgG2GPfn1RpWs6i yf+d4qUWgUhvl5pc0HqTsfBZNbVCy9MCpWAiEIph+fv/gA924S8PJLhemZmr/ZS2Kjum tDTDa2deDXB5qHa+e1rJ0NacS3y3bEkK+tbtDUHzrWYP3LpK0NU4njBYy3BxXHzLCF5B C/CbqgAhVcDtm74+TsAW9COMyoOR8XcmJzerspI2k0sJBocRkqGzhy9EZ+rp8s6ZLX+x iWEg==
MIME-Version: 1.0
X-Received: by 10.194.48.116 with SMTP id k20mr22653254wjn.23.1373578802221; Thu, 11 Jul 2013 14:40:02 -0700 (PDT)
Received: by 10.217.38.138 with HTTP; Thu, 11 Jul 2013 14:40:02 -0700 (PDT)
Date: Thu, 11 Jul 2013 16:40:02 -0500
Message-ID: <CAK3OfOj-g9WYcuLNk0bcWQ7TG3DLWJAnAPuDCKfSOZaF2YJZRA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: kitten@ietf.org
Content-Type: text/plain; charset="UTF-8"
Subject: [kitten] PKCROSS
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: Thu, 11 Jul 2013 21:40:09 -0000

I note this text in the current charter:

  Prepare a standards-track protocol to solve the use cases addressed
        by draft-hotz-kx509-01 including new support for digital
        signatures.

The thought occurs that Kerberos + kx509 + PKINIT can be a sort of
PKCROSS.  That makes me very interested.  It shouldn't be very
difficult to build that almost entirely out of off-the-shelf protocol
pieces.  It's not trival though: we'd definitely need policy for
handling PKIX trust paths, and it wouldn't minimize the need for PK
crypto.

PKCROSS -or similar- is not in-charter at this time.

Just a thought,

Nico
--