IETF Logo Mail Archive

Re: [kitten] Any Interest in a Key Delivery Service?

Ken Hornstein <kenh@pobox.com> Wed, 13 September 2017 13:31 UTC

Return-Path: <kenh@pobox.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 AFFC5133036 for <kitten@ietfa.amsl.com>; Wed, 13 Sep 2017 06:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pobox.com; domainkeys=pass (1024-bit key) header.from=kenh@pobox.com header.d=pobox.com
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 9l_dTQOKRX66 for <kitten@ietfa.amsl.com>; Wed, 13 Sep 2017 06:31:57 -0700 (PDT)
Received: from sasl.smtp.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8C161321A1 for <kitten@ietf.org>; Wed, 13 Sep 2017 06:31:56 -0700 (PDT)
Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 056D5985B5; Wed, 13 Sep 2017 09:31:56 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=from:to:cc :subject:in-reply-to:references:mime-version:content-type:date :message-id; s=sasl; bh=v19n6qMQ+mOQJ1PpFOqScVTqmKY=; b=nywwVjgf PPlB/VJP4KajJCzaalRqxjlNOGHFOIWsN4mHewBCnQKdHLB0B4Ql0cgF3Kh5hWOC dIoThAgsYXvAyLRE4UTxaO8tNNqnlPLeNZFSLoY/qWmSoG/0mnx0vLXIjDA6SUAQ U8uXwhEX/uGdSF0KZXS8MB8Z3KExM/5+q3A=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=from:to:cc :subject:in-reply-to:references:mime-version:content-type:date :message-id; q=dns; s=sasl; b=FFjY1m5jPVVRCfVFvIFIoGJUAuiOl0BoQ9 jVmn5em94gq1qsVnE5fWCR/nuXTquvpXp8tIF94KflCLqKxJ/80F1H6ZUycK8BAp 17lkLrgggjWOznC2Aa8fcJfwN/La2+mAFbAMVh9TVaqF0woDG2ODgzmulU+q1RWk Q7O6R5rrc=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id F275C985B4; Wed, 13 Sep 2017 09:31:55 -0400 (EDT)
Received: from zoolander.cmf.nrl.navy.mil (unknown [134.207.12.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 67660985B1; Wed, 13 Sep 2017 09:31:55 -0400 (EDT)
From: Ken Hornstein <kenh@pobox.com>
To: "Henry B (Hank) Hotz, CISSP" <hbhotz@oxy.edu>
cc: "kitten@ietf.org <kitten@ietf.org>" <kitten@ietf.org>
In-Reply-To: <7BAC4A7B-5585-4CF0-8373-9BD54C3281FD@oxy.edu>
References: <2FB98F5F-3981-4EFF-8CFF-FF6B5B3D485C@oxy.edu> <20170913013057.B1BEE8E632@pb-smtp2.pobox.com> <7BAC4A7B-5585-4CF0-8373-9BD54C3281FD@oxy.edu>
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4 WIn3jU;bql;{2Uq%zw5bF4?%F&&j8@KaT?#vBGk}u07<+6/`.F-3_GA@6Bq5gN9\+s;_d gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;Mv(aiO2z~9n.w?@\>kEpSD@*e`
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Wed, 13 Sep 2017 09:31:54 -0400
X-Pobox-Relay-ID: E8FE84F8-9887-11E7-9AE3-9D2B0D78B957-90216062!pb-smtp2.pobox.com
Message-Id: <20170913133155.F275C985B4@pb-smtp2.pobox.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/kitten/0kb0Y17tuMuRfQ44np9a0K564J4>
Subject: Re: [kitten] Any Interest in a Key Delivery Service?
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 13 Sep 2017 13:31:59 -0000

>OK, so should we produce a spec that tells them how to do it, or would
>that just trigger NIH (not invented here)?

Good question!  In my experience the issues are a) lack of specification,
and b) getting people to implement the specification.

I do think it would be .... not worth the effort to go through the IETF
process to produce something for KMIP.  You need to work in their space
(OASIS).

--Ken

v2.23.0 | Report a Bug | By Email