RFC 3585: IPsec Configuration Policy Information Model
In plain English — editorial summary, not part of the RFC
This document presents an object-oriented information model of IP Security (IPsec) policy designed to facilitate agreement about the content and semantics of IPsec policy, and enable derivations of task- specific representations of IPsec policy such as storage schema, distribution representations, and policy specification languages used to configure IPsec-enabled endpoints. The information model described in this document models the configuration parameters defined by IPSec. The information model also covers the parameters found by the Internet Key Exchange protocol (IKE). Other key exchange protocols could easily be added to the information model by a simple extension. Further extensions can further be added easily due to the object-oriented nature of the model. This information model is based upon the core policy classes as defined in the Policy Core Information Model (PCIM) and in the Policy Core Information Model Extensions (PCIMe). [STANDARDS-TRACK]
Document record
- Document ID
- RFC3585
- Published
- August 2003
- Authors
- J. Jason; L. Rafalow; E. Vyncke
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 88
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3664The AES-XCBC-PRF-128 Algorithm for the Internet Key Exchange Protocol (IKE)Obsoleted
January 2004
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 3602The AES-CBC Cipher Algorithm and Its Use with IPsecCurrent
September 2003
- RFC 3566The AES-XCBC-MAC-96 Algorithm and Its Use With IPsecCurrent
September 2003
- RFC 4302IP Authentication HeaderCurrent
December 2005
- RFC 4303IP Encapsulating Security Payload (ESP)Current
December 2005
- RFC 4306Internet Key Exchange (IKEv2) ProtocolObsoleted
December 2005
- RFC 4307Cryptographic Algorithms for Use in the Internet Key Exchange Version 2 (IKEv2)Obsoleted
December 2005
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?