RFC 3586: IP Security Policy (IPSP) Requirements

In plain English — editorial summary, not part of the RFC

This document describes the problem space and solution requirements for developing an IP Security Policy (IPSP) configuration and management framework. The IPSP architecture provides a scalable, decentralized framework for managing, discovering and negotiating the host and network security policies that govern access, authorization, authentication, confidentiality, data integrity, and other IP Security properties. This document highlights such architectural components and presents their functional requirements. [STANDARDS-TRACK]

Document record

Document ID

RFC3586

Published

August 2003

Authors

M. Blaze; A. Keromytis; M. Richardson; L. Sanchez

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

10

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC3586

Topics

• IPSP
• Internet Protocol Security Policy
• data integrity
• authentication
• host network

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 3566The AES-XCBC-MAC-96 Algorithm and Its Use With IPsecCurrent

  September 2003

• RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted

  June 2003

• RFC 3647Internet X.509 Public Key Infrastructure Certificate Policy and Certification Practices FrameworkCurrent

  November 2003

• RFC 3709Internet X.509 Public Key Infrastructure: Logotypes in X.509 CertificatesObsoleted

  February 2004

• RFC 3820Internet X.509 Public Key Infrastructure (PKI) Proxy Certificate ProfileCurrent

  June 2004

• RFC 3278Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)Obsoleted

  May 2002

• RFC 3195Reliable Delivery for syslogCurrent

  November 2001

• RFC 3156MIME Security with OpenPGPCurrent

  August 2001

Also filed under

• PROPOSED STANDARD
• 2003
• IETF stream
• sec area