A new Request for Comments is now available in online RFC libraries.
RFC 4809
Title: Requirements for an IPsec Certificate
Management Profile
Author: C. Bonatti, Ed.,
S. Turner, Ed.,
G. Lebovitz, Ed.
Status: Informational
Date: February 2007
Mailbox: Bonattic@ieca.com,
Turners@ieca.com,
gregory.ietf@gmail.com
Pages: 45
Characters: 98400
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-pki4ipsec-mgmt-profile-rqts-07.txt
URL: http://www.rfc-editor.org/rfc/rfc4809.txt
This informational document describes and identifies the requirements
for transactions to handle Public Key Certificate (PKC) lifecycle
transactions between Internet Protocol Security (IPsec) Virtual
Private Network (VPN) Systems using Internet Key Exchange (IKE)
(versions 1 and 2) and Public Key Infrastructure (PKI) Systems. These
requirements are designed to meet the needs of enterprise-scale IPsec
VPN deployments. It is intended that a standards track profile of a
management protocol will be created to address many of these
requirements. This memo provides information for the Internet community.
This document is a product of the Profiling Use of PKI in IPSEC
Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution
of this memo is unlimited.
This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@RFC-EDITOR.ORG
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
Authors, for further information.
The RFC Editor Team
USC/Information Sciences Institute
...
_______________________________________________
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce
