[hiprg] fwd: New Version Notification for draft-irtf-hiprg-revocation-00
Dacheng Zhang <zhangdacheng@huawei.com> Mon, 07 June 2010 16:55 UTC
Return-Path: <zhangdacheng@huawei.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C455428C919 for <hiprg@core3.amsl.com>; Mon, 7 Jun 2010 09:55:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.904
X-Spam-Level: **
X-Spam-Status: No, score=2.904 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_SUB_RAND_LETTRS4=0.799]
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 xl3MdIoiw-GG for <hiprg@core3.amsl.com>; Mon, 7 Jun 2010 09:55:26 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 4251128C13B for <hiprg@irtf.org>; Sun, 6 Jun 2010 19:55:53 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3M007G6ISVBE@szxga04-in.huawei.com> for hiprg@irtf.org; Mon, 07 Jun 2010 10:55:43 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3M0040BISVZS@szxga04-in.huawei.com> for hiprg@irtf.org; Mon, 07 Jun 2010 10:55:43 +0800 (CST)
Received: from z00133208 ([10.110.98.81]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L3M000H7ISUPV@szxml06-in.huawei.com> for hiprg@irtf.org; Mon, 07 Jun 2010 10:55:43 +0800 (CST)
Date: Mon, 07 Jun 2010 10:55:42 +0800
From: Dacheng Zhang <zhangdacheng@huawei.com>
To: hiprg@irtf.org
Message-id: <002101cb05ec$eb8a9620$51626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="us-ascii"
Content-transfer-encoding: 7bit
Thread-index: Acr/FpnoPRDKQNEeToqlGGn9JGrSmwG1iOow
Subject: [hiprg] fwd: New Version Notification for draft-irtf-hiprg-revocation-00
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jun 2010 16:55:27 -0000
A new version of I-D, draft-irtf-hiprg-revocation-00.txt has been successfully submitted by Dacheng Zhang and posted to the IETF repository. Filename: draft-irtf-hiprg-revocation Revision: 00 Title: Host Identifier Revocation in HIP Creation_date: 2010-05-29 WG ID: Independent Submission Number_of_pages: 18 Abstract: This document mainly analyzes the key revocation issue with host identities (HIs) in the Host Identity Protocol (HIP). Generally, key revocation is an important functionality of key management systems; it is concerned with the issues of removing antique cryptographic keys from operational usages when they are not secure or not secure enough any more. This functionality is particularly important for the security systems expected to execute for long periods. This document also attempts to investigate several key issues that a designer of HI revocation mechanisms need to carefully consider. The IETF Secretariat.
- [hiprg] fwd: New Version Notification for draft-i… Dacheng Zhang