1 / 10

Default Address Selection for IPv6

Default Address Selection for IPv6. draft-ietf-ipngwg-default-addr-select-04. Richard Draves May 31, 2001 Redmond Interim IPv6 WG Meeting. Source Address Selection and Destination Address Ordering. Minimal requirement for all implementations

juliamassey
Download Presentation

Default Address Selection for IPv6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Default Address Selection for IPv6 draft-ietf-ipngwg-default-addr-select-04 Richard DravesMay 31, 2001 Redmond Interim IPv6 WG Meeting

  2. Source Address Selection and Destination Address Ordering • Minimal requirement for all implementations • Automatically pick “reasonable”source and destination addresses • Configuration/policy is possible • NOT just for multi-homing • Complement other multi-homing approaches

  3. What’s Changed? • Reversed treatment of temporary addresses. • Implementations should avoid use unless application directs otherwise. • Clarify expectation that applications will loop over list of destination addresses. • Removed references to getipnodebyname.

  4. Last-Call Comments • Discussion – standard vs informational? • Clarify candidate set formation for routers. • Source address selection for multicast dests. • Privacy: temporary vs public preference. • No route to destination? • ISATAP? • Various minor editorial comments.

  5. Open Issues • Changes to Base API spec to allow applications to influence address selection? • Temporary addresses • Care-of vs home addresses

  6. Not Just for Multi-Homing • Consider a singly-homed IPv6 host… • Loopback, link-local, site-local addresses • Global address, temporary address • v4-compatible address, 6to4 address • Home address • IPv4 addresses • 90% of the complexity due to considerations other than multi-homing.

  7. Default Policy Table Implementations SHOULD be configurable, via mechanisms at least as powerful as these policy tables. If not configured, then they SHOULD operate according to the default policy table: … IPv4 destinations are represented as v4-mapped addresses.

  8. Source Address Selection Rules Selecting IPv6 source for IPv6 destination: • Prefer same address (for loopback). • Prefer appropriate scope. • Avoid deprecated addresses. • Prefer home addresses over care-of addresses. • Prefer source assigned to originating interface. • Prefer matching label from policy table. • Avoid temporary addresses. • Use longest-matching-prefix.

  9. Destination Address Ordering First, select best source for each destination,IPv6 and IPv4: • Avoid unusable destinations. • Prefer matching scope. • Avoid deprecated source addresses. • Prefer home source addresses. • Prefer matching label from policy table. • Prefer destinations with higher precedence. • Prefer smaller scope destinations. • Use longest-matching-prefix. • Otherwise, leave order from DNS unchanged

  10. Controversial Issues • Configuration mechanisms and default treatment for mobility & privacy preferences: • Home vs care-of addresses • Temporary vs public addresses • Current draft says • Prefer home address over care-of address • Prefer temporary address over public address • Configure via socket option (but does not preclude other approaches)

More Related