1 / 6

IPv6 RA Options for Multiple Interface Next Hop Routes

IPv6 RA Options for Multiple Interface Next Hop Routes. Behcet Sarikaya ( sarikaya@ieee.org ) IETF 84. d raft-sarikaya-mif-6man-ra-route-01. RA Route Option Motivation. RFC 4191 defines Route Information Option Prf field is to prefer the router associated with this IPv6 destination prefix

afya
Download Presentation

IPv6 RA Options for Multiple Interface Next Hop Routes

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. IPv6 RA Options for Multiple Interface Next Hop Routes BehcetSarikaya(sarikaya@ieee.org) IETF 84 draft-sarikaya-mif-6man-ra-route-01

  2. RA Route OptionMotivation • RFC 4191 defines Route Information Option • Prf field is to prefer the router associated with this IPv6 destination prefix • Next hop address is missing • Next hop address metric is missing • Metric field • is added (preference for Next Hop Address) to the Route Information Option and the new option is called Route Prefix Option • Next Hop Address option • Next hop address represents the IPv6 destination prefixes reachable via the given next hop • Next hop address metric to prefer the next hop associated with this IPv6 destination prefix over others, when multiple identical prefixes (for different next hops) have been received

  3. RA Route OptionMotivation - Continued • Next Hop Address with Route Prefix option • Includes next hop with RPO in one option to designate that specific routes are available via routers • If there is more than one route available via specific next hop, one next hop which contains multiple route prefix options • RA based solution • Assume clients that know what to do with the info • Those that don’t simply ignore

  4. Proposed RA Options • RPO • Defines the destination prefix • Borrows from RFC4191 in using the Reserved and Prf values • Adds metric in place of resvd • Prf is for preferring the router and metric is for preferring the next hop • Next Hop Address • Defines IPv6 next hop address.

  5. Proposed RA Options • Next Hop Address and RPO • Defines the two options together in one option

  6. Mailing List Discussions • Feedback from WG: • Brian commented that a central site-wide configuration mechanism is needed • Zhen asked how to relate the prefix option with nexthop option if they are used combined • To clearly indicate the next hop address associated with the right RPO, to avoid any inconsistency arising from sending the two in two different options • Hui asked what is the problem with RFC 4191? • No problem with 4191 however multiple interfaced smart phones and multi-homed hosts bring the need to add a few new RA options • Ok to progress into WG draft?

More Related