RFC 4116: IPv4 Multihoming Practices and Limitations
In plain English — editorial summary, not part of the RFC
Multihoming is an essential component of service for many Internet sites. This document describes some implementation strategies for multihoming with IPv4 and enumerates features for comparison with other multihoming proposals (particularly those related to IPv6). This memo provides information for the Internet community.
Document record
- Document ID
- RFC4116
- Published
- July 2005
- Authors
- J. Abley; K. Lindqvist; E. Davies; B. Black; V. Gill
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 13
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4148IP Performance Metrics (IPPM) Metrics RegistryObsoleted
August 2005
- RFC 4177Architectural Approaches to Multi-homing for IPv6Current
September 2005
- RFC 4192Procedures for Renumbering an IPv6 Network without a Flag DayCurrent
September 2005
- RFC 4029Scenarios and Analysis for Introducing IPv6 into ISP NetworksCurrent
March 2005
- RFC 4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksCurrent
October 2005
- RFC 3956Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast AddressUpdated
November 2004
- RFC 3904Evaluation of IPv6 Transition Mechanisms for Unmanaged NetworksCurrent
September 2004
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
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?