Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 17
- 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.
- Publication Date
- 2008-07-01
- Status Note
- Informational
- DOI
10.17487/RFC5220- Link
- https://doi.org/10.17487/RFC5220
- Author(s)
- Arifumi MatsumotoTomohiro FujisakiRuri HiromiKen-ichi Kanayama
- Keyword(s)
- Multiple Prefixes
Latest version of IETF RFC 5220
Document Versions — IETF RFC 5220
-
▶ IETF RFC 5220 (2008-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 3041 [Superseded*]
- IETF RFC 3484 [Superseded*]
- IETF RFC 3775 [Superseded*]
- IETF RFC 4192 [Active*]
- IETF RFC 4193 [Active*]
- IETF RFC 4291 [Active*]
- IETF RFC 4862 [Active*]
- IETF RFC 4864 [Active*]
- IETF RFC 5014 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5220.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5220, Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules. Available at https://doi.org/10.17487/RFC5220
Snippet:
IETF RFC 5220, Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules. Available at https://doi.org/10.17487/RFC5220
HTML (ISO 690 compliant)
Preview:
IETF RFC 5220, Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules. Available at https://doi.org/10.17487/RFC5220
Snippet:
<span class="citation"><cite>IETF RFC 5220</cite>, Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules. Available at <a href="https://doi.org/10.17487/RFC5220" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5220</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5220, Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules
doi: 10.17487/RFC5220
url: https://doi.org/10.17487/RFC5220
doi: 10.17487/RFC5220
url: https://doi.org/10.17487/RFC5220
Snippet:
<li> <cite id="bib-rfc5220">IETF RFC 5220</cite>, Problem Statement for Default Address Selection in Multi-Prefix Environments: Operational Issues of RFC 3484 Default Rules <span class="doi">10.17487/RFC5220</span> </li>
Referenced By
- IETF RFC 5221 [Active*]
- IETF RFC 6418 [Active*]
- IETF RFC 6724 [Active*]
- IETF RFC 7157 [Active*]