[RPSEC] FW: I-D ACTION:draft-liu-ospfv3-automated-keying-req-01.txt
Liu Ya <liuya@huawei.com> Wed, 11 July 2007 01:09 UTC
Return-path: <rpsec-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1I8QhY-0005Jh-MA; Tue, 10 Jul 2007 21:09:08 -0400
Received: from rpsec by megatron.ietf.org with local (Exim 4.43)
id 1I8QhX-0005CW-LO
for rpsec-confirm+ok@megatron.ietf.org; Tue, 10 Jul 2007 21:09:07 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1I8QhX-0005B0-9h; Tue, 10 Jul 2007 21:09:07 -0400
Received: from szxga03-in.huawei.com ([61.144.161.55])
by chiedprmail1.ietf.org with esmtp (Exim 4.43)
id 1I8QhW-0002jg-EH; Tue, 10 Jul 2007 21:09:07 -0400
Received: from huawei.com (szxga03-in [172.24.2.9])
by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
(built Aug
8 2006)) with ESMTP id <0JKZ00L4SPTFB3@szxga03-in.huawei.com>; Wed,
11 Jul 2007 09:08:03 +0800 (CST)
Received: from huawei.com ([172.24.1.24])
by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
(built Aug
8 2006)) with ESMTP id <0JKZ00GACPTEQV@szxga03-in.huawei.com>; Wed,
11 Jul 2007 09:08:03 +0800 (CST)
Received: from l52008 ([10.111.12.58])
by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14
(built Aug
8 2006)) with ESMTPA id <0JKZ00HS8PT60S@szxml04-in.huawei.com>; Wed,
11 Jul 2007 09:08:02 +0800 (CST)
Date: Wed, 11 Jul 2007 09:07:54 +0800
From: Liu Ya <liuya@huawei.com>
To: rpsec@ietf.org, msec@ietf.org, ospf@ietf.org
Message-id: <0d2a01c7c357$ec0f1150$3a0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/mixed; boundary="Boundary_(ID_Gaxjm66XcimoVhgdPwnjRw)"
Thread-index: AcfDQKb49Ch5PWV1QYe2wsyzopRAEAAFhlUA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b2809b6f39decc6de467dcf252f42af1
Cc:
Subject: [RPSEC] FW: I-D ACTION:draft-liu-ospfv3-automated-keying-req-01.txt
X-BeenThere: rpsec@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing Protocol Security Requirements <rpsec.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
<mailto:rpsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/rpsec>
List-Post: <mailto:rpsec@ietf.org>
List-Help: <mailto:rpsec-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rpsec>,
<mailto:rpsec-request@ietf.org?subject=subscribe>
Errors-To: rpsec-bounces@ietf.org
Hi all, The requirement doc for OSPFv3 IPSec automated group key management has been updated to -01. Compared with the -00 doc, the stuff was reorganized, and some possible solutions and their specific requirements were added. Comments are welcome. Thanks, LIU Ya -----Original Message----- From: Internet-Drafts@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: Wednesday, July 11, 2007 6:15 AM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-liu-ospfv3-automated-keying-req-01.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : OSPFv3 Automated Group Keying Requirements Author(s) : Y. Liu, et al. Filename : draft-liu-ospfv3-automated-keying-req-01.txt Pages : 15 Date : 2007-7-10 RFC4552 describes how to provide authentication/confidentiality to OSPFv3 using IPsec. It specifies that same IPsec SA parameters be configured for both inbound and outbound SAs to provide the "one to many" security for multicast OSPFv3 communications over broadcast links (e.g., Ethernet). Manual keying is specified as the mandatory and default group key management solution. However, issues of scalability and security exist with manual keying. It is better to replace manual keying with automated group key management. This document discusses the requirements on OSPFv3 automated group key management, assuming that the centralized group key management architecture introduced in [RFC4046] is used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-liu-ospfv3-automated-keying- req-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-liu-ospfv3-automated-keying-req-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-liu-ospfv3-automated-keying-req-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft.
_______________________________________________ RPSEC mailing list RPSEC@ietf.org https://www1.ietf.org/mailman/listinfo/rpsec