RFC 4219: Things Multihoming in IPv6 (MULTI6) Developers Should Think About
In plain English — editorial summary, not part of the RFC
This document specifies a set of questions that authors should be prepared to answer as part of a solution to multihoming with IPv6. The questions do not assume that multihoming is the only problem of interest, nor do they demand a more general solution. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4219
- Published
- October 2005
- Authors
- E. Lear
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4218Threats Relating to IPv6 Multihoming SolutionsCurrent
October 2005
- RFC 4057IPv6 Enterprise Network ScenariosCurrent
June 2005
- RFC 4472Operational Considerations and Issues with IPv6 DNSCurrent
April 2006
- RFC 4609Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and EnhancementsCurrent
October 2006
- RFC 4852IPv6 Enterprise Network Analysis - IP Layer 3 FocusCurrent
April 2007
- RFC 4942IPv6 Transition/Co-existence Security ConsiderationsCurrent
September 2007
- RFC 4943IPv6 Neighbor Discovery On-Link Assumption Considered HarmfulCurrent
September 2007
- RFC 5375IPv6 Unicast Address Assignment ConsiderationsCurrent
December 2008
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?