RFC 3457: Requirements for IPsec Remote Access Scenarios

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

IPsec offers much promise as a secure remote access mechanism. However, there are a number of differing remote access scenarios, each having some shared and some unique requirements. A thorough understanding of these requirements is necessary in order to effectively evaluate the suitability of a specific set of mechanisms for any particular remote access scenario. This document enumerates the requirements for a number of common remote access scenarios. This memo provides information for the Internet community.

Document record

Document ID

RFC3457

Published

January 2003

Authors

S. Kelly; S. Ramamoorthi

Status

INFORMATIONAL

Stream

IETF

Area

sec

Pages

31

Also known as

—

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

Topics

• ipsra
• common remote access scenarios

Related documents

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

• RFC 3456Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel ModeCurrent

  January 2003

• RFC 3394Advanced Encryption Standard (AES) Key Wrap AlgorithmCurrent

  October 2002

• RFC 3526More Modular Exponential (MODP) Diffie-Hellman groups for Internet Key Exchange (IKE)Current

  May 2003

• RFC 3379Delegated Path Validation and Delegated Path Discovery Protocol RequirementsCurrent

  September 2002

• RFC 3537Wrapping a Hashed Message Authentication Code (HMAC) key with a Triple-Data Encryption Standard (DES) Key or an Advanced Encryption Standard (AES) KeyCurrent

  May 2003

• RFC 3370Cryptographic Message Syntax (CMS) AlgorithmsUpdated

  September 2002

• RFC 3369Cryptographic Message Syntax (CMS)Obsoleted

  September 2002

• RFC 3546Transport Layer Security (TLS) ExtensionsObsoleted

  June 2003

Also filed under

• INFORMATIONAL
• 2003
• IETF stream
• sec area