Problem Statement of Default Address Selection in Multi-prefix Environment: Operational Issues of RFC3484 Default Rules
draft-arifumi-v6ops-addr-select-ps-01

Document Type Replaced Internet-Draft (individual)
Last updated 2006-12-05 (latest revision 2006-10-23)
Replaced by draft-ietf-v6ops-addr-select-ps
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-v6ops-addr-select-ps
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-arifumi-v6ops-addr-select-ps-01.txt

Abstract

One physical network can carry multiple logical networks. Moreover, we can use multiple physical networks at the same time in a host. In that environment, end-hosts might have multiple IP addresses and be required to use them selectively. Without an appropriate source/ destination address selection mechanism, the host will experience some trouble in the communication. RFC 3484 defines both the source and destination address selection algorithms, but the multi-prefix environment considered here needs additional rules beyond the default operation. This document describes the possible problems that end- hosts could encounter in an environment with multiple logical networks.

Authors

Arifumi Matsumoto (matsumoto.arifumi@lab.ntt.co.jp)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)