RFC 4177: Architectural Approaches to Multi-homing for IPv6
In plain English — editorial summary, not part of the RFC
This memo provides an analysis of the architectural aspects of multi-homing support for the IPv6 protocol suite. The purpose of this analysis is to provide a taxonomy for classification of various proposed approaches to multi-homing. It is also an objective of this exercise to identify common aspects of this domain of study, and also to provide a framework that can allow exploration of some of the further implications of various architectural extensions that are intended to support multi-homing. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4177
- Published
- September 2005
- Authors
- G. Huston
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4192Procedures for Renumbering an IPv6 Network without a Flag DayCurrent
September 2005
- RFC 4148IP Performance Metrics (IPPM) Metrics RegistryObsoleted
August 2005
- RFC 4215Analysis on IPv6 Transition in Third Generation Partnership Project (3GPP) NetworksCurrent
October 2005
- RFC 4116IPv4 Multihoming Practices and LimitationsCurrent
July 2005
- RFC 4029Scenarios and Analysis for Introducing IPv6 into ISP NetworksCurrent
March 2005
- RFC 4339IPv6 Host Configuration of DNS Server Information ApproachesCurrent
February 2006
- 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
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?