Re: [karp] I-D Action: draft-ietf-karp-crypto-key-table-07.txt

Russ Housley <housley@vigilsec.com> Tue, 12 March 2013 17:56 UTC

Return-Path: <housley@vigilsec.com>
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 F0A1811E8103 for <karp@ietfa.amsl.com>; Tue, 12 Mar 2013 10:56:05 -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=[AWL=0.000, 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 UtT0ZSJZNBAJ for <karp@ietfa.amsl.com>; Tue, 12 Mar 2013 10:56:05 -0700 (PDT)
Received: from odin.smetech.net (mail.smetech.net [208.254.26.82]) by ietfa.amsl.com (Postfix) with ESMTP id B954611E8106 for <karp@ietf.org>; Tue, 12 Mar 2013 10:56:00 -0700 (PDT)
Received: from localhost (unknown [208.254.26.81]) by odin.smetech.net (Postfix) with ESMTP id D10519A4078 for <karp@ietf.org>; Tue, 12 Mar 2013 13:56:24 -0400 (EDT)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([208.254.26.82]) by localhost (ronin.smetech.net [208.254.26.81]) (amavisd-new, port 10024) with ESMTP id kwmIgmg+jE2m for <karp@ietf.org>; Tue, 12 Mar 2013 13:55:35 -0400 (EDT)
Received: from dhcp-5419.meeting.ietf.org (dhcp-5419.meeting.ietf.org [130.129.84.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 6CF359A4075 for <karp@ietf.org>; Tue, 12 Mar 2013 13:56:22 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20130312174956.29201.68199.idtracker@ietfa.amsl.com>
Date: Tue, 12 Mar 2013 13:55:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <293EAC7A-F774-4997-9337-A118F565A241@vigilsec.com>
References: <20130312174956.29201.68199.idtracker@ietfa.amsl.com>
To: karp@ietf.org
X-Mailer: Apple Mail (2.1085)
Subject: Re: [karp] I-D Action: draft-ietf-karp-crypto-key-table-07.txt
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: Tue, 12 Mar 2013 17:56:06 -0000

This document reflects the two changes discussed in the KARP session that is still taking place.  The changes look exactly as discussed to me.  Thanks for the prompt action Sam.

Russ


On Mar 12, 2013, at 1:49 PM, internet-drafts@ietf.org wrote:

> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Keying and Authentication for Routing Protocols Working Group of the IETF.
> 
> 	Title           : Database of Long-Lived Symmetric Cryptographic Keys
> 	Author(s)       : Russell Housley
>                          Tim Polk
>                          Sam Hartman
>                          Dacheng Zhang
> 	Filename        : draft-ietf-karp-crypto-key-table-07.txt
> 	Pages           : 11
> 	Date            : 2013-03-12
> 
> Abstract:
>   This document specifies the information contained in a conceptual
>   database of long-lived cryptographic keys used by many different
>   security protocols.  The database is designed to support both manual
>   and automated key management.  In addition to describing the schema
>   for the database, this document describes the operations that can be
>   performed on the database as well as the requirements for the
>   security protocols that wish to use the database.  In many typical
>   scenarios, the security protocols do not directly use the long-lived
>   key, but rather a key derivation function is used to derive a short-
>   lived key from a long-lived key.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-karp-crypto-key-table
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-karp-crypto-key-table-07
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-karp-crypto-key-table-07
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> karp mailing list
> karp@ietf.org
> https://www.ietf.org/mailman/listinfo/karp