IETF Logo Mail Archive

Re: [karp] Call for WG adoption: draft-mahesh-karp-rkmp-04

Sam Hartman <hartmans-ietf@mit.edu> Mon, 29 July 2013 08:23 UTC

Return-Path: <hartmans@mit.edu>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 904F321F9A0C for <karp@ietfa.amsl.com>; Mon, 29 Jul 2013 01:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 C3P4LxaUySLv for <karp@ietfa.amsl.com>; Mon, 29 Jul 2013 01:23:26 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id CCAFC21F9DB0 for <karp@ietf.org>; Mon, 29 Jul 2013 01:23:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 4926020118; Mon, 29 Jul 2013 04:22:42 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wfWgNYRvgR8F; Mon, 29 Jul 2013 04:22:38 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (dhcp-4332.meeting.ietf.org [130.129.67.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Mon, 29 Jul 2013 04:22:37 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 1A15587FB4; Mon, 29 Jul 2013 04:23:09 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Russ Housley <housley@vigilsec.com>
References: <51F6173E.70007@joelhalpern.com> <19780515-2383-452C-B1E8-33CB033AA2D6@vigilsec.com>
Date: Mon, 29 Jul 2013 04:23:09 -0400
In-Reply-To: <19780515-2383-452C-B1E8-33CB033AA2D6@vigilsec.com> (Russ Housley's message of "Mon, 29 Jul 2013 03:47:25 -0400")
Message-ID: <tslehahydua.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: "karp@ietf.org" <karp@ietf.org>
Subject: Re: [karp] Call for WG adoption: draft-mahesh-karp-rkmp-04
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for key management for routing and transport protocols <karp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/karp>, <mailto:karp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/karp>
List-Post: <mailto:karp@ietf.org>
List-Help: <mailto:karp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/karp>, <mailto:karp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jul 2013 08:23:37 -0000

>>>>> "Russ" == Russ Housley <housley@vigilsec.com> writes:

    Russ> I am confused by the approach taken in this draft.  I only
    Russ> skimmed it.  We defined a crypto key table, and that document
    Russ> is close to IESG approval.  I think that IKEv2 should be used
    Russ> to populate the key table, and then TCP-AO can pull keying
    Russ> material from the table, as is already described, at least
    Russ> partially, in the key table document.  Russ

RKMP is intended to work with the key table draft as you describe.
With the specific case of TCP-AO there are some additional complexities
because of abstractions created by the TCP-AO spec.
It's certainly intended to be the case that rows are added to the key
table by RKMP and it's intended to be the case that TCP-AO interacts
with the key table in a manner similar to how it handles manual keying
with regard to RKMP.

If we got some details wrong, I think we can fix that after WG adoption.

v2.23.0 | Report a Bug | By Email