RFC 5221: Requirements for Address Selection Mechanisms
In plain English — editorial summary, not part of the RFC
There are some problematic cases when using the default address selection mechanism that RFC 3484 defines. This document describes additional requirements that operate with RFC 3484 to solve the problems. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5221
- Published
- July 2008
- Authors
- A. Matsumoto; T. Fujisaki; R. Hiromi; K. Kanayama
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5220Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default RulesCurrent
July 2008
- RFC 5181IPv6 Deployment Scenarios in 802.16 NetworksCurrent
May 2008
- RFC 5180IPv6 Benchmarking Methodology for Network Interconnect DevicesCurrent
May 2008
- RFC 5277NETCONF Event NotificationsCurrent
July 2008
- RFC 5157IPv6 Implications for Network ScanningObsoleted
March 2008
- RFC 5156Special-Use IPv6 AddressesObsoleted
April 2008
- RFC 5153IP Flow Information Export (IPFIX) Implementation GuidelinesCurrent
April 2008
- RFC 5136Defining Network CapacityCurrent
February 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?