RFC 4891: Using IPsec to Secure IPv6-in-IPv4 Tunnels
In plain English — editorial summary, not part of the RFC
This document gives guidance on securing manually configured IPv6-in- IPv4 tunnels using IPsec in transport mode. No additional protocol extensions are described beyond those available with the IPsec framework. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4891
- Published
- May 2007
- Authors
- R. Graveman; M. Parthasarathy; P. Savola; H. Tschofenig
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4710Real-time Application Quality-of-Service Monitoring (RAQMON) FrameworkCurrent
October 2006
- RFC 4339IPv6 Host Configuration of DNS Server Information ApproachesCurrent
February 2006
- RFC 4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksCurrent
October 2005
- RFC 4192Procedures for Renumbering an IPv6 Network without a Flag DayCurrent
September 2005
- RFC 4177Architectural Approaches to Multi-homing for IPv6Current
September 2005
- RFC 4148IP Performance Metrics (IPPM) Metrics RegistryObsoleted
August 2005
- RFC 4116IPv4 Multihoming Practices and LimitationsCurrent
July 2005
- RFC 4029Scenarios and Analysis for Introducing IPv6 into ISP NetworksCurrent
March 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?