RFC 4942: IPv6 Transition/Co-existence Security Considerations
In plain English — editorial summary, not part of the RFC
The transition from a pure IPv4 network to a network where IPv4 and IPv6 coexist brings a number of extra security considerations that need to be taken into account when deploying IPv6 and operating the dual-protocol network and the associated transition mechanisms. This document attempts to give an overview of the various issues grouped into three categories: o issues due to the IPv6 protocol itself, o issues due to transition mechanisms, and o issues due to IPv6 deployment. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4942
- Published
- September 2007
- Authors
- E. Davies; S. Krishnan; P. Savola
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4943IPv6 Neighbor Discovery On-Link Assumption Considered HarmfulCurrent
September 2007
- RFC 4852IPv6 Enterprise Network Analysis - IP Layer 3 FocusCurrent
April 2007
- RFC 5375IPv6 Unicast Address Assignment ConsiderationsCurrent
December 2008
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 4219Things Multihoming in IPv6 (MULTI6) Developers Should Think AboutCurrent
October 2005
- RFC 4218Threats Relating to IPv6 Multihoming SolutionsCurrent
October 2005
- RFC 4213Basic Transition Mechanisms for IPv6 Hosts and RoutersCurrent
October 2005
- RFC 4057IPv6 Enterprise Network ScenariosCurrent
June 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?