Protocol Action: 'Dynamic Symmetric Key Provisioning Protocol (DSKPP)' to Proposed Standard
The IESG <iesg-secretary@ietf.org> Tue, 14 September 2010 14:28 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D5283A699D; Tue, 14 Sep 2010 07:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level:
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCe76rRiO7QW; Tue, 14 Sep 2010 07:28:27 -0700 (PDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 184213A691A; Tue, 14 Sep 2010 07:28:26 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Protocol Action: 'Dynamic Symmetric Key Provisioning Protocol (DSKPP)' to Proposed Standard
X-Test-IDTracker: no
Message-ID: <20100914142826.31046.30529.idtracker@localhost>
Date: Tue, 14 Sep 2010 07:28:26 -0700
Cc: Internet Architecture Board <iab@iab.org>, keyprov mailing list <keyprov@ietf.org>, keyprov chair <keyprov-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 14:28:28 -0000
The IESG has approved the following document: - 'Dynamic Symmetric Key Provisioning Protocol (DSKPP)' <draft-ietf-keyprov-dskpp-14.txt> as a Proposed Standard This document is the product of the Provisioning of Symmetric Keys Working Group. The IESG contact persons are Tim Polk and Sean Turner. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-keyprov-dskpp/ Technical Summary DSKPP is a client-server protocol for initialization (and configuration) of symmetric keys to locally and remotely accessible cryptographic modules. The protocol can be run with or without private-key capabilities in the cryptographic modules, and with or without an established public-key infrastructure. Two variations of the protocol support multiple usage scenarios. With the four-pass variant, keys are mutually generated by the provisioning server and cryptographic module; provisioned keys are not transferred over-the-wire or over-the-air. The two-pass variant enables secure and efficient download and installation of pre- generated symmetric keys to a cryptographic module. Working Group Summary I would note that we seem to have had more discussion of issues connected with XML style and semantics than on the problem. In particular there does not seem to be a perfect answer to the problem of how to manage versioning of XML protocols. Media type review was initiated 4/22 by the AD. Document Quality The document is a product of the KEYPROV working group. Personnel Document Shepherd is Phillip Hallam-Baker. Tim Polk is the responsible AD. RFC Editor Note Note that RFC 2781 should be an informative reference; normative reference should be ISO 10646 Reference as written in RFC 2781. [ISO-10646] ISO/IEC 10646-1:1993. International Standard -- Information technology -- Universal Multiple-Octet Coded Character Set (UCS) -- Part 1: Architecture and Basic Multilingual Plane. 22 amendments and two technical corrigenda have been published up to now. UTF-16 is described in Annex Q, published as Amendment 1. Many other amendments are currently at various stages of standardization. A second edition is in preparation, probably to be published in 2000; in this new edition, UTF-16 will probably be described in Annex C. Probably should refer to ISO 10646:2003???