RFC 3456: Dynamic Host Configuration Protocol (DHCPv4) Configuration of IPsec Tunnel Mode
In plain English — editorial summary, not part of the RFC
This memo explores the requirements for host configuration in IPsec tunnel mode, and describes how the Dynamic Host Configuration Protocol (DHCPv4) may be leveraged for configuration. In many remote access scenarios, a mechanism for making the remote host appear to be present on the local corporate network is quite useful. This may be accomplished by assigning the host a "virtual" address from the corporate network, and then tunneling traffic via IPsec from the host's ISP-assigned address to the corporate security gateway. In IPv4, DHCP provides for such remote host configuration. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3456
- Published
- January 2003
- Authors
- B. Patel; B. Aboba; S. Kelly; V. Gupta
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 18
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3396Encoding Long Options in the Dynamic Host Configuration Protocol (DHCPv4)Current
November 2002
- RFC 3527Link Selection sub-option for the Relay Agent Information Option for DHCPv4Current
April 2003
- RFC 3776Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home AgentsUpdated
June 2004
- RFC 3011The IPv4 Subnet Selection Option for DHCPCurrent
November 2000
- RFC 4339IPv6 Host Configuration of DNS Server Information ApproachesCurrent
February 2006
- RFC 3394Advanced Encryption Standard (AES) Key Wrap AlgorithmCurrent
October 2002
- RFC 3547The Group Domain of InterpretationObsoleted
July 2003
- RFC 3554On the Use of Stream Control Transmission Protocol (SCTP) with IPsecCurrent
July 2003
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?