RFC 3582: Goals for IPv6 Site-Multihoming Architectures
In plain English — editorial summary, not part of the RFC
This document outlines a set of goals for proposed new IPv6 site- multihoming architectures. It is recognised that this set of goals is ambitious and that some goals may conflict with others. The solution or solutions adopted may only be able to satisfy some of the goals presented here. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3582
- Published
- August 2003
- Authors
- J. Abley; B. Black; V. Gill
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3498Definitions of Managed Objects for Synchronous Optical Network (SONET) Linear Automatic Protection Switching (APS) ArchitecturesCurrent
March 2003
- RFC 3393IP Packet Delay Variation Metric for IP Performance Metrics (IPPM)Current
November 2002
- RFC 3831Transmission of IPv6 Packets over Fibre ChannelObsoleted
July 2004
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
- RFC 3904Evaluation of IPv6 Transition Mechanisms for Unmanaged NetworksCurrent
September 2004
- RFC 3956Embedding the Rendezvous Point (RP) Address in an IPv6 Multicast AddressUpdated
November 2004
- RFC 4029Scenarios and Analysis for Introducing IPv6 into ISP NetworksCurrent
March 2005
- RFC 3056Connection of IPv6 Domains via IPv4 CloudsCurrent
February 2001
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?