RFC 4891: Using IPsec to Secure IPv6-in-IPv4 Tunnels

This document gives guidance on securing manually configured IPv6-in- IPv4 tunnels using IPsec in transport mode. No additional protocol extensions are…

Read RFC 4891 on the RFC Editor

Outgoing relationships (15 related RFCs)

Normative reference — RFC 4303: IP Encapsulating Security Payload (ESP)
Normative reference — RFC 2401: Security Architecture for the Internet Protocol
Normative reference — RFC 2409: The Internet Key Exchange (IKE)
Normative reference — RFC 4306: Internet Key Exchange (IKEv2) Protocol
Normative reference — RFC 4213: Basic Transition Mechanisms for IPv6 Hosts and Routers
Normative reference — RFC 3704: Ingress Filtering for Multihomed Networks
Informative reference — RFC 4302: IP Authentication Header
Informative reference — RFC 3056: Connection of IPv6 Domains via IPv4 Clouds
Informative reference — RFC 4023: Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)
Informative reference — RFC 4555: IKEv2 Mobility and Multihoming Protocol (MOBIKE)
Informative reference — RFC 3715: IPsec-Network Address Translation (NAT) Compatibility Requirements
Informative reference — RFC 2893: Transition Mechanisms for IPv6 Hosts and Routers
Informative reference — RFC 3884: Use of IPsec Transport Mode for Dynamic Routing
Informative reference — RFC 4718: IKEv2 Clarifications and Implementation Guidelines
Informative reference — RFC 3193: Securing L2TP using IPsec

Incoming relationships (3 related RFCs)

Informatively referenced by — RFC 4925: Softwire Problem Statement
Informatively referenced by — RFC 5739: IPv6 Configuration in Internet Key Exchange Protocol Version 2 (IKEv2)
Informatively referenced by — RFC 6071: IP Security (IPsec) and Internet Key Exchange (IKE) Document Roadmap