From nobody Thu Apr 3 02:50:43 2014 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 030161A0020; Thu, 3 Apr 2014 02:50:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham 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 7MyeQjx5v7k3; Thu, 3 Apr 2014 02:50:33 -0700 (PDT) Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 19AB01A001F; Thu, 3 Apr 2014 02:50:33 -0700 (PDT) Received: from [192.168.1.133] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 8356C180150F; Thu, 3 Apr 2014 11:50:28 +0200 (CEST) Message-ID: <533D2EE3.3030709@pi.nu> Date: Thu, 03 Apr 2014 11:50:27 +0200 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: "mpls@ietf.org" , karp@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/karp/MLOimunWFw3dnDK1ROL79c7URNw Cc: "mpls-chairs@tools.ietf.org" , "VIGOUREUX, MARTIN \(MARTIN\)" , draft-ietf-mpls-ldp-hello-crypto-auth@tools.ietf.org Subject: [karp] Implementatins of draft-ietf-mpls-ldp-hello-crypto-auth ?? 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Apr 2014 09:50:39 -0000 Working Group, We are preparing the Shepherd write-up for draft-ietf-mpls-ldp-hello-crypto-auth and need to know about existing implementations. If you have an implementation please send a mail to the working group mailing list, the working group chairs or the document shepherd to let us know. Mails directly to chairs or shepherd is fully acceptable. /Loa mpls wg co-chair document shepherd -- Loa Andersson email: loa@mail01.huawei.com Senior MPLS Expert loa@pi.nu Huawei Technologies (consultant) phone: +46 739 81 21 64 From nobody Mon Apr 21 15:28:40 2014 Return-Path: X-Original-To: karp@ietfa.amsl.com Delivered-To: karp@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) 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-Level: 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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, tim.polk@nist.gov, hartmans-ietf@mit.edu, zhangdacheng@huawei.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 http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist 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