[karp] RFC 7210 on Database of Long-Lived Symmetric Cryptographic Keys

rfc-editor@rfc-editor.org Mon, 21 April 2014 22:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: karp@ietfa.amsl.com
Delivered-To: karp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id BBBBE1A02F7; Mon, 21 Apr 2014 15:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.174
X-Spam-Status: No, score=-102.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 7Bb2HM-miCWq; Mon, 21 Apr 2014 15:28:34 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 3CD741A02F6; Mon, 21 Apr 2014 15:28:33 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 17F0D1801B1; Mon, 21 Apr 2014 15:27:46 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20140421222746.17F0D1801B1@rfc-editor.org>
Date: Mon, 21 Apr 2014 15:27:46 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/karp/lNWosewkNdyjCT5yjdHaZAwFIUo
Cc: drafts-update-ref@iana.org, karp@ietf.org, rfc-editor@rfc-editor.org
Subject: [karp] RFC 7210 on Database of Long-Lived Symmetric Cryptographic Keys
X-BeenThere: karp@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Apr 2014 22:28:39 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7210

        Title:      Database of Long-Lived Symmetric Cryptographic Keys 
        Authors:    R. Housley, T. Polk, S. Hartman, D. Zhang
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2014
        Mailbox:    housley@vigilsec.com, 
        Pages:      14
        Characters: 32642
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-karp-crypto-key-table-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7210.txt

This document specifies the information contained in a conceptual database 
of long-lived cryptographic keys used by many different routing protocols 
for message security.  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 routing protocols that 
wish to use the database.  In many typical scenarios, the 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.

This document is a product of the Keying and Authentication for Routing Protocols Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC