Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules
RFC 5220, “Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules”, is an Informational document published in July 2008 by A. Matsumoto, T. Fujisaki, R. Hiromi, K. Kanayama. The canonical text is published by the RFC Editor.
Abstract
A single physical link can have multiple prefixes assigned to it. In that environment, end hosts might have multiple IP addresses and be required to use them selectively. RFC 3484 defines default source and destination address selection rules and is implemented in a variety of OSs. But, it has been too difficult to use operationally for several reasons. In some environments where multiple prefixes are assigned on a single physical link, the host using the default address selection rules will experience some trouble in communication. This document describes the possible problems that end hosts could encounter in an environment with multiple prefixes. This memo provides information for the Internet community.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 5220 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5219 A More Loss-Tolerant RTP Payload Format for MP3 Audio
- RFC 5221 Requirements for Address Selection Mechanisms
- RFC 5218 What Makes for a Successful Protocol?
- RFC 5222 LoST: A Location-to-Service Translation Protocol
- RFC 5217 Memorandum for Multi-Domain Public Key Infrastructure Interoperability
- RFC 5223 Discovering Location-to-Service Translation Servers Using the Dynamic Host Configuration Protocol
- RFC 5216 The EAP-TLS Authentication Protocol
- RFC 5224 Diameter Policy Processing Application